Pierrick Bouvier

After investigation, I can confirm it is flaky tests, randomly failing because of wrong order in output expected. Those tests are concerned: * sequential/test-watch-mode-inspect.mjs * sequential/test-watch-mode.mjs

I'm trying to contact author of those commits to see if that is normal, and what we can do with it.

PR: * https://github.com/nodejs/node/pull/44551 * https://github.com/nodejs/node/pull/44621 @MoLow (author). Do you know if something could create trouble with this? On my machine, I can make some failure appear by increasing the charge...

@sxa I suppose win-x64 CI did not fail with this, else those tests should already been marked as flaky. On our WoA machines, we reproduced that with x64 binaries (instead...

Thanks @richardlau, I missed that one, but that's exactly the issue.

@aduh95 It is not built on an arm64 machine, but on this agent: `test-rackspace-win2012r2_vs2019-x64-1` you can probably open another issue, or simply ask on nodejs slack build channel, if you...

That would be very nice to start running them. We can try for 24 hours, and see if jobs queue gets larger and larger. For flaky tests reported here, I...

@joaocgreis To clarify things a bit more, neither @nsait-linaro nor me have access to what you describe, so that would be nice if you could change that value to enable...

Thanks to https://github.com/nodejs/node/pull/45049 merged, the windows-arm-simple is now [green](https://ci.nodejs.org/job/windows-arm-simple/nodes=win10-vs2019-arm64/) again! 👍 Can we start enabling official job for this platform (despite current limitation with only two machines available)? Thanks

Yes sure, we don't want to block anything for contributors! The windows-arm-simple job has been green since we fixed it, so it should be fine.