-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
test: remove flaky designation for fixed test #35961
Conversation
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I should have done that in my PR.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
maybe we should wait a little with this. I have just seen another fail: https://ci.nodejs.org/job/node-test-commit-osx/37136/ Hmm, stress test was green so maybe a single event |
This comment has been minimized.
This comment has been minimized.
The test is not nearly as unreliable as it used to be but we're still seeing failures around the timing checks that will definitely be affected by other tests running in other processes. So move it to sequential. Refs: nodejs#35961 (comment)
Oh, yeah, that timing sensitivity with those millisecond magic numbers is definitely going to be affected by being in the parallel directory. The test needs to be re-written to not be dependent on "must happen within 10 milliseconds" type logic or else (the more likely result) moved to sequential. Pull request to do just that: #35996 |
Remove flaky designation for test-worker-eventlooputil fixed in 9dbde1d. PR-URL: nodejs#35961 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Landed in 55b1718 |
The test is not nearly as unreliable as it used to be but we're still seeing failures around the timing checks that will definitely be affected by other tests running in other processes. So move it to sequential. Refs: #35961 (comment) PR-URL: #35996 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]>
Remove flaky designation for test-worker-eventlooputil fixed in 9dbde1d. PR-URL: #35961 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Remove flaky designation for test-worker-eventlooputil fixed in 9dbde1d. PR-URL: #35961 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Remove flaky designation for test-worker-eventlooputil fixed in 9dbde1d. PR-URL: #35961 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
The test is not nearly as unreliable as it used to be but we're still seeing failures around the timing checks that will definitely be affected by other tests running in other processes. So move it to sequential. Refs: #35961 (comment) PR-URL: #35996 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]>
Remove flaky designation for test-worker-eventlooputil fixed in 9dbde1d.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes