chore: Fix two types of warnings in unit tests #2183
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit reduces the number of times two warnings appear when running unit tests:
PytestRemovedIn9Warning
intests/unit/test_opentelemetry_tracing.py
: Removed a@pytest.mark.skipif
decorator from a fixture. The skip condition is already present on the test methods that use the fixture.Example warning:
FutureWarning
intests/unit/test_client.py
: Updated calls toclient.query()
to includejob_retry=None
whenjob_id
is also specified. This is to avoid ambiguity as BigQuery cannot retry a failed job with the exact same ID.Example warning: