-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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-stream2-readable-empty-buffer-no-eof #4493
Comments
Trott
added
test
Issues and PRs related to the tests.
arm
Issues and PRs related to the ARM platform.
labels
Dec 30, 2015
Stress test to confirm flakiness: |
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jan 3, 2016
Use common.platformTimeout() to fix flaky test-stream2-readable-empty-buffer-no-eofi on Raspberry Pis. Fixes: nodejs#4493
Fishrock123
pushed a commit
to Fishrock123/node
that referenced
this issue
Jan 6, 2016
Use common.platformTimeout() to fix flaky test-stream2-readable-empty-buffer-no-eofi on Raspberry Pis. Fixes: nodejs#4493 PR-URL: nodejs#4516 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Evan Lucas <evanlucas@me.com> Reviewed-By: James M Snell<jasnell@gmail.com>
scovetta
pushed a commit
to scovetta/node
that referenced
this issue
Apr 2, 2016
Use common.platformTimeout() to fix flaky test-stream2-readable-empty-buffer-no-eofi on Raspberry Pis. Fixes: nodejs#4493 PR-URL: nodejs#4516 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Evan Lucas <evanlucas@me.com> Reviewed-By: James M Snell<jasnell@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failure:
The text was updated successfully, but these errors were encountered: