Flaky parallel/test-child-process-fork-args on Windows

[puzpuzpuz]

Saw this test crashing in node-test-binary-windows-js-suites on https://ci.nodejs.org/job/node-test-pull-request/30753/:

12:59:01 not ok 70 parallel/test-child-process-fork-args
12:59:01   ---
12:59:01   duration_ms: 0.305
12:59:01   severity: crashed
12:59:01   exitcode: -1073741819
12:59:01   stack: |-
12:59:01   ...

[addaleax]

Fwiw, I tried to reproduce this locally, but failed both on Linux and Windows. :/

[puzpuzpuz]

Fwiw, I tried to reproduce this locally, but failed both on Linux and Windows. :/

From what I can find on the internet, -1073741819 application exit code on Windows means Access Violation exception, which is a generic error. So, it may be related with something specific in CI machine environment.

If I encounter this failure once again, I'll post an update here.

[puzpuzpuz]

Saw this one once again today here:
https://ci.nodejs.org/job/node-test-binary-windows-js-suites/3285/RUN_SUBSET=1,nodes=win10-COMPILED_BY-vs2019/testReport/(root)/test/parallel_test_child_process_fork_args/

[targos]

Happened here too: https://ci.nodejs.org/job/node-test-binary-windows-js-suites/3321/

[sam-github]

Can we mark it as flaky to get CI stable? (This issue would remain open).

[puzpuzpuz]

Can we mark it as flaky to get CI stable? (This issue would remain open).

Created #32950 to mark it as flaky