-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
gh-107851: Fix spurious failures in fcntl eintr tests #121556
Conversation
On heavily loaded machines, the subprocess may finish its sleep before the parent process manages to synchronize with it via a failed lock. This leads to errors like: Exception: failed to sync child in 300.3 sec Use pipes instead to mutually synchronize between parent and child.
I tested this with the following command to heavily load 2 CPUs with 20 tests. This seems to fairly reliably reproduce the issue before this PR. I no longer see failures after this PR is applied.
|
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.
LGTM. It looks like real working synchronization code, whereas before, it was more an optimistic heuristic :-)
Thanks @colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
…-121556) On heavily loaded machines, the subprocess may finish its sleep before the parent process manages to synchronize with it via a failed lock. This leads to errors like: Exception: failed to sync child in 300.3 sec Use pipes instead to mutually synchronize between parent and child. (cherry picked from commit af9f6de) Co-authored-by: Sam Gross <[email protected]>
…-121556) On heavily loaded machines, the subprocess may finish its sleep before the parent process manages to synchronize with it via a failed lock. This leads to errors like: Exception: failed to sync child in 300.3 sec Use pipes instead to mutually synchronize between parent and child. (cherry picked from commit af9f6de) Co-authored-by: Sam Gross <[email protected]>
GH-121585 is a backport of this pull request to the 3.13 branch. |
GH-121586 is a backport of this pull request to the 3.12 branch. |
…) (#121586) On heavily loaded machines, the subprocess may finish its sleep before the parent process manages to synchronize with it via a failed lock. This leads to errors like: Exception: failed to sync child in 300.3 sec Use pipes instead to mutually synchronize between parent and child. (cherry picked from commit af9f6de) Co-authored-by: Sam Gross <[email protected]>
…) (#121585) On heavily loaded machines, the subprocess may finish its sleep before the parent process manages to synchronize with it via a failed lock. This leads to errors like: Exception: failed to sync child in 300.3 sec Use pipes instead to mutually synchronize between parent and child. (cherry picked from commit af9f6de) Co-authored-by: Sam Gross <[email protected]>
…21556) On heavily loaded machines, the subprocess may finish its sleep before the parent process manages to synchronize with it via a failed lock. This leads to errors like: Exception: failed to sync child in 300.3 sec Use pipes instead to mutually synchronize between parent and child.
…21556) On heavily loaded machines, the subprocess may finish its sleep before the parent process manages to synchronize with it via a failed lock. This leads to errors like: Exception: failed to sync child in 300.3 sec Use pipes instead to mutually synchronize between parent and child.
On heavily loaded machines, the subprocess may finish its sleep before the parent process manages to synchronize with it via a failed lock.
This leads to errors like:
Use pipes instead to mutually synchronize between parent and child.