-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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-fs-readfile-tostring-fail #4046
Comments
It looks like the issue is that the test can take 20 or 30 seconds on ubuntu1404-32 under ordinary conditions and so a hiccup of some kind can make it exceed the 60 second timeout implemented by the test runner. |
Stress test came up clean (with the 20-30 second caveat mentioned above). This never came up as flaky before so I'm going to close it. It looks like maybe all that happened was the host was bogged down for some reason and tests that normally take a long time took a Very Long Time and timed out. If this comes up again, we can re-open this or open a new ticket and explore it some more. |
Happened again on a Raspberry: https://ci.nodejs.org/job/node-test-binary-arm/2650/RUN_SUBSET=6,label=pi2-raspbian-wheezy/console Not reopening this issue since it failed by timeout and could be a hiccup, but reporting this just in case we see more of it soon and need to start investigating. |
Example failure:
The text was updated successfully, but these errors were encountered: