Fix flaky test_steal_twice and test_steal_when_more_tasks#9288
Merged
Conversation
crusaderky
added
flaky test
Contributor
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 40 files ±0 40 suites ±0 14h 39m 31s ⏱️ + 13m 43s For more details on these failures, see this check. Results for commit 597f6b2. ± Comparison against base commit daff1c6. This pull request removes 1 and adds 1 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
crusaderky
changed the title
test_steal_twicetest_steal_twice and steal_when_more_tasks
crusaderky
changed the title
test_steal_twice and steal_when_more_taskstest_steal_twice and test_steal_when_more_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
1 participant
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.
test_steal_twiceflaky #4957test_steal_twicewas almost always failing on high-CPU-count desktops due to unbound number of threads-per-worker