-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
TST BUG: Tests fail in sandboxed environment #155
Comments
I guess we can start using However here is an immediate patch for your use case for now, where I simply wget-ed the most up-to-date objects.inv file to /tmp. But if you have site-packages/sphinx_astropy/local/python3_local_links.inv
|
@pllim - I'm kind of inclined towards decorating the tests as online tests and call it a day (and having CI run all but on job with online enabled) rather than adding a local intersphinx file here. After all, the feature of adding alternative locations is not a sphinx-automodapi feature and should have been tested upstream already. |
Personally, I would be more than satisfied if it checked for a You both know what's best for your project, naturally :) With your suggestion, I've already been able to get the tests running for |
yeah, I wonder why it never came up as a problem for e.g. debian packaging testing, anyway, we have the machinery to enforce tests not to run when there is no online connection, that will probably be the solution for here. |
👍 to marking as remote and (optionally) open follow-up issue to see if it can run offline in the future. |
@lovesegfault , do you have a list of the failed tests in sandboxed env? I can mark them or a PR is also very welcome. Thanks! |
If you show me how to mark them, I can roll back the patch where I fixed this in |
You would need to add Line 26 in c4aa837
Then you can use it like this: import pytest
@pytest.mark.remote_data
def some_test_that_needs_internet():
# Much internet, so remote |
Almost all the tests fail inside a sandboxed build environment because they require network access for some reason. The error is always the same:
I would appreciate it if there was a way to manually provide this
objects.inv
file, so that tests could still run without network access.The text was updated successfully, but these errors were encountered: