-
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
Investigate flaky test test-child-process-emfile #2666
Comments
Both happened in the new |
Another one, again in |
Why don't these tests show error output? |
rebooted pi2-7, just in case it's something related to just being set up yesterday and not having a reboot since |
@Fishrock123 because they timed out - pr #2647 would make that visible |
Can't say I've seen this around either. |
Different platform: |
Seems to mostly/only fail on FreeBSD lately. #3335 isn't a fix but may at least help point someone in the right direction. |
The test treats |
Proposed fix in #3430 |
Require the test setup to obtain an EMFILE error and not ENFILE as ENFILE means there is a race condition with other processes that may close files before `spawn()` is called by the test. Fixes: nodejs#2666
Require the test setup to obtain an EMFILE error and not ENFILE as ENFILE means there is a race condition with other processes that may close files before `spawn()` is called by the test. Fixes: #2666 PR-URL: #3430 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
Require the test setup to obtain an EMFILE error and not ENFILE as ENFILE means there is a race condition with other processes that may close files before `spawn()` is called by the test. Fixes: #2666 PR-URL: #3430 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
Require the test setup to obtain an EMFILE error and not ENFILE as ENFILE means there is a race condition with other processes that may close files before `spawn()` is called by the test. Fixes: #2666 PR-URL: #3430 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
Examples of failures:
pi2-raspbian-wheezy
pi2-raspbian-wheezy
(while testing v3.3.0)Ref: #2636 (comment)
The text was updated successfully, but these errors were encountered: