-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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 flaky parallel/test-child-process-exec-kill-throws #12053
Comments
PR-URL: nodejs#12054 Ref: nodejs#12053 Ref: nodejs#11038 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
PR to fix coming in a few minutes. The child process isn't failing because of exceeding Fixed by moving the I'm running a stress test now to make sure these changes actually get rid of the flakiness. (UPDATE: Looks good. https://ci.nodejs.org/job/node-stress-single-test/1146/nodes=win-vs2015/console) As for how this bug triggers flakiness on Windows (assuming the flakiness on Windows is related to it), I'm not 100% sure, but I do see this: On Windows, it's getting UV_ESRCH a lot, indicating the process is already exited by the time |
Here it is: #12111 |
Cross-posting from #12111 (comment)
|
Possibly, but the thing we're seeing there isn't Windows-specific. The bug in the test that that PR fixes seemed Windows specific. The new issue it exposes now that bug is fixed.. that's on all sorts of platforms. Check the CI results. |
This is a fix for test-child-process-exec-kill-throws which is currently flaky on Windows. A bug in the test was causing the child process to fail for reasons other than those intended by the test. Instead of failing for exceeding the `maxBuffer` setting, the test was failing because it was trying to load `internal/child_process` without being passed the `expose-internals` flag. Move that module to where only the parent process (which gets the flag) loads it. Additionally, improve an assertion message to help debug problems like this. Fixes: nodejs#12053
This is a fix for test-child-process-exec-kill-throws which is currently flaky on Windows. A bug in the test was causing the child process to fail for reasons other than those intended by the test. Instead of failing for exceeding the `maxBuffer` setting, the test was failing because it was trying to load `internal/child_process` without being passed the `expose-internals` flag. Move that module to where only the parent process (which gets the flag) loads it. Additionally, improve an assertion message to help debug problems like this. PR-URL: nodejs#12111 Fixes: nodejs#12053 Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Creating this issue to document that we need to work out and fix the issue. Will mark as flaky in a separate PR. EDIT: #12054
See discussion in #11038.
cc/ @nodejs/platform-windows
The text was updated successfully, but these errors were encountered: