-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests requiring internet access #1088
Comments
Bonus points if anyone can figure out how to jail our runners so that we can actually test this in CI and prevent it from slipping in again. We seem to fix bugs like this with every release. Note that many of our slow tests (run only on release branches) are actually designed to test these kinds of dataset and weight downloads. We should be able to get 100% coverage without internet access, but can add additional slow tests to ensure that the weights still download correctly. |
@calebrob6 I think the detection tests could use the same treatment from #344, that would greatly speed things up. |
|
It can be done at the same time, using a fake detection model and avoiding downloads. Both will speed up the test and make it more stable. |
FarSeg tests were failing on main because of this. Would love to get these fixed. |
Update: slowly whittling these down:
|
Useful discussion (Linux-only): |
Description
Several of our tests require internet access. This is problematic for a number of reasons:
We should apply the same magic we used in previous PRs to monkeypatch any downloads.
Steps to reproduce
rm -r $(python -c 'import torch; print(torch.hub.get_dir())')
pytest
Version
0.5.0.dev0 (ce4e7ef)
The text was updated successfully, but these errors were encountered: