| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Replace a flaky immediates event loop test that hasn't truly made sense for a while, since it has gone through so many different iterations, with a new test that is verifying the same behavior but without so much potential for flakiness. Fixes: nodejs#24497
|
Stress test CI: https://ci.nodejs.org/job/node-stress-single-test/311/ Edit: Passed. Now let's try to get a bad run on master... heh. https://ci.nodejs.org/job/node-stress-single-test/313/ |
Sorry, something went wrong.
|
Trying stress tests again but this time with -J --repeat 10 -j 16 --repeat 128. Current (expected to fail): https://ci.nodejs.org/job/node-stress-single-test/314/ https://ci.nodejs.org/job/node-stress-single-test/315/ This PR (expected to pass): ...will run once we see failures above... |
Sorry, something went wrong.
|
Tbh I don't know that we've seen this fail on Win10 ever. Definitely older versions but I haven't been able to get those to run in node-stress-single-test. Trying some of the others https://ci.nodejs.org/job/node-stress-single-test/316/ Edit: Trying again... https://ci.nodejs.org/job/node-stress-single-test/317/ Edit2: I guess most recently this actually failed on CentOS so... https://ci.nodejs.org/job/node-stress-single-test/318/ |
Sorry, something went wrong.
|
I have no clue about our build systems but most of these node-stress-single-test instances aren't working :( |
Sorry, something went wrong.
We could approve the PR on principle, I suppose. |
Sorry, something went wrong.
Looks like the stress job didn’t have the -gcc8 variants for centos7 added to the selectable configurations (we wouldn’t expect earlier versions to be able to compile current master). Also centos7-64 isn’t currently covered by https://github.com/nodejs/build/blob/master/jenkins/scripts/select-compiler.sh so isn’t selecting the right compiler either. I can look at sorting this out but it’ll be after the security releases. |
Sorry, something went wrong.
|
This needs a rebase. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Replace a flaky immediates event loop test that hasn't truly made sense for a while, since it has gone through so many different iterations, with a new test that is verifying the same behavior but without so much potential for flakiness.
Fixes: #24497