-
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
flaky test/parallel/test-trace-atomics-wait.js when run in parallel #33427
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
Comments
Thanks, I’ll take alook.
We should definitely not move a test to sequential just because it’s flaky. I think it’s okay when we really can’t come up with a better solution. (This test is not resource-intensive or conflicts with other tests running in parallel, so it does belong in |
addaleax
added
the
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
label
May 16, 2020
addaleax
added a commit
to addaleax/node
that referenced
this issue
May 16, 2020
This adds a possible ordering of the trace events that was missing from the list previously. Fixes: nodejs#33427
3 tasks
codebytere
pushed a commit
that referenced
this issue
Jun 18, 2020
This adds a possible ordering of the trace events that was missing from the list previously. Fixes: #33427 PR-URL: #33428 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
codebytere
pushed a commit
that referenced
this issue
Jun 18, 2020
This adds a possible ordering of the trace events that was missing from the list previously. Fixes: #33427 PR-URL: #33428 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
codebytere
pushed a commit
that referenced
this issue
Jun 30, 2020
This adds a possible ordering of the trace events that was missing from the list previously. Fixes: #33427 PR-URL: #33428 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Colin Ihrig <[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
I discovered it with
make test -j12
On my local machine:
Is it expected? Should we move it to sequential?
The text was updated successfully, but these errors were encountered: