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

[Trott]

I'm not finding this error with ncu-ci walk commit and no one has reported it here since April (but that may just be because it's been marked flaky so people ignore it failing).

I'll run a stress test. If that passes, I'll open a PR to optimistically remove the flaky designation.

[Trott]

Stress test CI: https://ci.nodejs.org/job/node-stress-single-test/164/

[Trott]

Stress test was green. PR to remove this from flaky tests; #34684

[vweevers]

no one has reported it here since April

The exit code 1073741819 has been seen on AppVeyor builds too (of sharp, sqlite3, prebuild-install, native-hdr-histogram) with 32-bit node when running npm run * or even just npm -v. This bug disappears and reappears with new node releases. 14.0.0 had it, 14.1.0 and 14.2.0 did not, 14.3.0 did, 14.7.0 did.

I'm not sure it's the same issue, so I wanted to investigate before reporting but I haven't had the time to do so.

See appveyor/ci#3407 (comment)