Repository navigation
flaky test/parallel/test-trace-atomics-wait.js when run in parallel #33427
Description
Activity
Thanks, I’ll take alook.
Should we move it to sequential?
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
parallel/.)Reacted by Michaël Zasso- added a commit that references this issue
on May 16, 2020 - added a commit that references this issue
on May 23, 2020 - added 2 commits that reference this issue
on Jun 18, 2020 - added a commit that references this issue
on Jun 30, 2020
I discovered it with
make test -j12On my local machine:
Is it expected? Should we move it to sequential?