Windows CI failures

[BridgeAR]

From the last 100 CI runs only 14 succeeded on Windows. This is pretty bad and it's hard to actually get any CI run to become green.

I am not sure if this is already looked at or not but if not, we should definitely try to fix those ASAP. I just do not know much about Windows and won't be of much help.

// cc @nodejs/platform-windows @nodejs/testing

---

@mmarchini the percentage seems a bit off on your CI health indicator (101%):

EDIT(by @sam-github): issues labelled flaky on windows

[refack]

FWIW I know of two issues that were prevalent that were addressed in #28035 (one hopefully solved, and one marked as known flaky).
Currently the common flakes I see most often are (for example in the daily master test):

• flaky: parallel/test-http2-* on Windows #20750
• Investigate flaky async-hooks/test-statwatcher #21425
• Investigate flaky test-worker-prof #26401

Some more discussion at
nodejs/reliability#1
nodejs/build#1829 (comment)

Any assistance will be greatly appreciated.

[MichelLopez]

cc @joaocgreis @bzoz for tracking

[sam-github]

For prominence, I edited in a link to the list of issues for flaky windows tests, https://github.com/nodejs/node/issues?q=is%3Aopen+is%3Aissue+label%3A%22CI+%2F+flaky+test%22+label%3Awindows, there are 13 ATM.

[jasnell]

Not obvious that there's anything left here actionable. Closing but can reopen if necessary