Skip to content

[3.6] bpo-35601: Alleviate race condition when waiting for SIGALRM in test_asyncio (GH-11337) #11348

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

Merged
merged 1 commit into from
Jan 18, 2019

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Dec 29, 2018

There is a race condition regarding signal delivery in test_signal_handling_args for
test_asyncio.test_events.KqueueEventLoopTests. The signal can be received at any moment outside the time window provided in the test. The fix is to wait for the signal to be received instead with a bigger timeout.
(cherry picked from commit 5471420)

Co-authored-by: Pablo Galindo Pablogsal@gmail.com

https://bugs.python.org/issue35601

…asyncio (pythonGH-11337)

There is a race condition regarding signal delivery in test_signal_handling_args for
test_asyncio.test_events.KqueueEventLoopTests. The signal can be received at any moment outside the time window provided in the test. The fix is to wait for the signal to be received instead with a bigger timeout.
(cherry picked from commit 5471420)

Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
@miss-islington
Copy link
Contributor Author

@pablogsal: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

Sorry, I can't merge this PR. Reason: You're not authorized to push to this branch. Visit https://help.github.com/articles/about-protected-branches/ for more information..

@pablogsal
Copy link
Member

@ned-deily What are we supposed to do with PRs eliminating races in the testing suite in the 3.6 branch? Should we close this PR as only security fixes are allowed in 3.6 now?

@ned-deily
Copy link
Member

The dev guide discusses fixes for hard-failing tests in security-fix-only branches. Since we are still at the beginning of that phase for 3.6, I’m inclined to accept this PR After it’s had some exposure elsewhere. So just leave it open for now, thanks.
https://devguide.python.org/devcycle/#security-branches

@pablogsal
Copy link
Member

Thanks for the rapid response! There are a couple of PRs appart from this one eliminating races that happened recently. If we are going to retire soon the 3.6 buildbots I am on with not merging them :)

@ned-deily ned-deily merged commit 7eef540 into python:3.6 Jan 18, 2019
@miss-islington miss-islington deleted the backport-5471420-3.6 branch January 18, 2019 01:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip news tests Tests in the Lib/test dir
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants