-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
tests: mark additional WMS/WMTS test as network-dependent #13812
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
base: master
Are you sure you want to change the base?
Conversation
autotest/gdrivers/wms.py
Outdated
|
|
||
|
|
||
| @pytest.mark.network | ||
| @pytest.mark.require_curl |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
require_curl is not needed here since pytestmark = pytest.mark.require_driver("WMS") at line 28 implies it (the WMS driver is only enabled if CURL is enabled)
That pull request would only be worth it if generalized to marking (temptively) all tests that perform an external network access (tests doing localhost networking shouldn't be tagged with it)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarification.
You’re right , require_curl is redundant here given require_driver("WMS"). I’ll drop it.
Regarding scope,I agree that the marker is only really useful if applied more broadly. I kept this PR minimal as a follow-up example, but I’m happy to extend it to other tests that clearly perform external (non-localhost) network access if that’s preferred.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All non-fuzzing CI checks are now green.
The remaining CIFuzz failure appears unrelated to the changes in this PR, which only affect pytest markers and do not touch any fuzzed code paths.
Happy to re-run or adjust if you think it’s related.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The remaining CIFuzz failure appears unrelated to the changes in this PR,
yes that is unrelated. you can ignore that and concentrate on adding more markers where relevant
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All relevant tests performing external (non-localhost) network access have now been tagged, and CI is green.
I’ll leave it at this unless you’d like me to extend the marker coverage further.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are tests in the following files that would also benefit from the marker:
- autotest/gdrivers/gdalhttp.py
- autotest/gcore/vsis3.py
- autotest/gcore/vsigs.py
- autotest/gcore/vsicurl.py
- autotest/gcore/vsicurl_streaming.py
- autotest/ogr/ogr_sqlite.py
- autotest/ogr/ogr_shape.py
- autotest/ogr/ogr_shape_sbn.py
- autotest/ogr/ogr_parquet.py
This PR is a small follow-up to the introduction of pytest.mark.network.
It applies the marker to an additional test that clearly depends on external
network access, following the same conservative, case-by-case approach
discussed in #10886.