Draft
Conversation
Contributor
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 33 files + 2 33 suites +2 11h 45m 15s ⏱️ + 17m 46s For more details on these failures, see this check. Results for commit e4f757e. ± Comparison against base commit 4fb4814. ♻️ This comment has been updated with latest results. |
13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Warning-related test failures:
These are due to a difference between 3.14 and 3.14t, which causes warnings to be contextvars-based. This causes
pytest.warnsandpytest.mark.filterwarningsnot to catch warnings emitted by a thread which was started before the filter was set - such as in workers started by thecfixture. So it should just be a matter of tweaking the tests.Other test failures, which I have not investigated yet: