-
Notifications
You must be signed in to change notification settings - Fork 30k
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
aix, test: prolong debugged child process #15774
Conversation
Needs a stress test |
Still looking a bit flaky: Is there a way for the child process to pause until the debugger is attached? |
Maybe replace |
Can we do the stress test again? |
@jBarz not till nodejs/build#775 (comment) is resolved. |
@jBarz if you rebase I'll stress test. |
Thanks @gibfahn , done! |
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 the change but I think we also need to revert the AIX part of 7027191 so that it is no longer marked as flaky for AIX.
Pause child on startup using inspect-brk=0 until the parent debugger is ready.
I made another change which no longer marks this test as flaky for aix and windows. |
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.
Should stress test, but code LGTM
I think earlier stress test showed it was good. New CI since it has been 2 weeks: https://ci.nodejs.org/job/node-test-pull-request/11152/ |
arm failures were infra issues not related to this PR. |
Windows failure was #16688 so net is that CI is good with respect to this change. |
Pause child on startup using inspect-brk=0 until the parent debugger is ready. PR-URL: #15774 Fixes: #14897 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Landed as f1f0eb2 |
Pause child on startup using inspect-brk=0 until the parent debugger is ready. PR-URL: nodejs#15774 Fixes: nodejs#14897 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Pause child on startup using inspect-brk=0 until the parent debugger is ready. PR-URL: #15774 Fixes: #14897 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
On AIX, there is a possibility that the child process is done before the parent debugger can connect to it. So prolong the child process by factor of 2.
Fixes: #14897
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)