-
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
flaky: test-worker-uncaught-exception #23873
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
test
Issues and PRs related to the tests.
windows
Issues and PRs related to the Windows platform.
worker
Issues and PRs related to Worker support.
Comments
refack
added
windows
Issues and PRs related to the Windows platform.
test
Issues and PRs related to the tests.
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
worker
Issues and PRs related to Worker support.
labels
Oct 25, 2018
3 tasks
Since Rackspace vs. Azure is often a relevant thing on our Windows failures: The above test failure is on test-rackspace-win2012r2-x64-3. |
CI stress test: https://ci.nodejs.org/job/node-stress-single-test/2086/ (Stress test is on test-rackspace-win2012r2-x64-12.) ✔️ |
Stress did not repro. |
Re-opening because it's shown up again. test-rackspace-win2012r2-x64-7 14:05:51 not ok 536 parallel/test-worker-uncaught-exception
14:05:51 ---
14:05:51 duration_ms: 120.186
14:05:51 severity: fail
14:05:51 exitcode: 1
14:05:51 stack: |-
14:05:51 timeout
14:05:51 foo
14:05:51 ... |
addaleax
added a commit
to addaleax/node
that referenced
this issue
Feb 3, 2019
The Windows ETW code is not written to be compatible with multi-threading, and in particular it relies on global state like a single static `uv_async_t`. Adding that to multiple threads would corrupt the corresponding loops' handle queues. This addresses the flakiness of at least `test-worker-exit-code` and very likely other flaky tests that relate to Worker threads on Windows as well. Fixes: nodejs#25847 Fixes: nodejs#25702 Fixes: nodejs#24005 Fixes: nodejs#23873
2 tasks
addaleax
added a commit
that referenced
this issue
Feb 6, 2019
The Windows ETW code is not written to be compatible with multi threading, and in particular it relies on global state like a single static `uv_async_t`. Adding that to multiple threads would corrupt the corresponding loops' handle queues. This addresses the flakiness of at least `test-worker-exit-code` and very likely other flaky tests that relate to Worker threads on Windows as well. Fixes: #25847 Fixes: #25702 Fixes: #24005 Fixes: #23873 PR-URL: #25907 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: James M Snell <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
test
Issues and PRs related to the tests.
windows
Issues and PRs related to the Windows platform.
worker
Issues and PRs related to Worker support.
https://ci.nodejs.org/job/node-test-binary-windows/21029/COMPILED_BY=vs2017-x86,RUNNER=win2012r2,RUN_SUBSET=2/console
Windows
The text was updated successfully, but these errors were encountered: