-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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-read-buffer-tostring-fail on Raspberry Pi #7042
Comments
@Trott any other instances of this failure? It's possibly related to the Pi's all running their |
Not that I've noticed, but I haven't been paying attention to specific failures on Raspberry Pi the last few days. I'll run a stress test and if it doesn't show any problems, then let's close this issue. Stress test: https://ci.nodejs.org/job/node-stress-single-test/752/nodes=pi1-raspbian-wheezy/console (Aside: These aren't really "stress tests" but I can't think of a better term that is sufficiently succinct. Suggestions welcome.) |
Oof, that job went offline after 10 hours and it was still compiling. Let's try again and hope some of that compilation is cached... https://ci.nodejs.org/job/node-stress-single-test/753/nodes=pi1-raspbian-wheezy/console |
The test takes more than a minute to run on these devices, so I'm content with stopping it after 500 successful consecutive runs rather than waiting another 10 hours to get another 500 runs. Closing! |
Argh. It came back. https://ci.nodejs.org/job/node-test-binary-arm/2674/RUN_SUBSET=5,label=pi2-raspbian-wheezy/console
|
Might the thing to do here be to check |
It takes ~90s to run normally and the test runner times out at 120s. That seems like not a lot of headroom to me. I'm inclined to do the skip-based-on-memory thing as I imagine this is a memory-intensive test. |
Proposed fix: #7575 |
The test is memory intensive and times out occasionally on Raspberry Pi devices in CI. Successful test runs take about 90 seconds, but the devices time out after 120 seconds. That's not a lot of headroom. So let's skip the test on devices that have only modest amounts of memory. Fixes: nodejs#7042
The test is memory intensive and times out occasionally on Raspberry Pi devices in CI. Successful test runs take about 90 seconds, but the devices time out after 120 seconds. That's not a lot of headroom. So let's skip the test on devices that have only modest amounts of memory. Fixes: #7042 PR-URL: #7575 Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]>
https://ci.nodejs.org/job/node-test-binary-arm/2326/RUN_SUBSET=2,label=pi1-raspbian-wheezy/console
The text was updated successfully, but these errors were encountered: