-
-
Notifications
You must be signed in to change notification settings - Fork 718
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
Fix test nanny timeout #8847
Fix test nanny timeout #8847
Conversation
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 25 files ± 0 25 suites ±0 10h 9m 45s ⏱️ - 7m 53s For more details on these failures, see this check. Results for commit a325253. ± Comparison against base commit ac7a24e. This pull request removes 1 and adds 4 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
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, @fjetter!
distributed/tests/test_nanny.py
Outdated
async def try_to_kill_nanny(): | ||
while not nanny.process or nanny.process.status not in ( | ||
Status.starting, # this is what we want | ||
# Status.failed # we might've missed it already |
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.
# Status.failed # we might've missed it already |
This still has a problem... |
Alright, just let me know once it's ready for a final review. CI looked good though 🙈 |
@hendrikmakait should be good to go now |
This should be fixing
distributed.tests.test_nanny.test_nanny_timeout
which appears to be caused by a race condition between startup and kill.That condition is now tested in a dedicated test
test_worker_start_exception_while_killing