-
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
Windows intermittent ? - parallel/test-timers-throw-reschedule #21188
Comments
That test probably shouldn't be in parallel tbh. If someone wants to open a PR to move it to sequential on v8.x then that would be great. |
This is failing now on linuxone on v8.x:
|
Attempted to move to sequential and still feeing failures on linuxon
https://ci.nodejs.org/job/node-test-commit-linuxone/4061/nodes=rhel72-s390x/console /cc @nodejs/timers can someone please help out with this? Potentially blocking release Edit: I've got a PR moving the test to sequential and marking it flaky... #22379 we should not close this issue until we figure out how to unflake the test |
This also sets the test as flaky Refs: nodejs#21188
this is showing up again in #23774 have no clue why it is not showing up as flaky |
Node.js v8.x has reached the end-of-life and won't receive any fixes anymore. I am closing this since this issue seems to only apply to Node.js v8.x. |
https://ci.nodejs.org/job/node-test-binary-windows/17851/COMPILED_BY=vs2015-x86,RUNNER=win2012r2,RUN_SUBSET=2/console
The text was updated successfully, but these errors were encountered: