Repository navigation
Flaky parallel/test-child-process-fork-args on Windows #32863
Description
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 ...
Activity
[-]Flaky test/parallel/test-child-process-fork-args on Windows[/-][+]Flaky parallel/test-child-process-fork-args on Windows[/+]addaleax commentedon Apr 15, 2020
Fwiw, I tried to reproduce this locally, but failed both on Linux and Windows. :/
puzpuzpuz commentedon Apr 15, 2020
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 commentedon Apr 18, 2020
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 commentedon Apr 20, 2020
Happened here too: https://ci.nodejs.org/job/node-test-binary-windows-js-suites/3321/
sam-github commentedon Apr 20, 2020
Can we mark it as flaky to get CI stable? (This issue would remain open).
puzpuzpuz commentedon Apr 20, 2020
Created #32950 to mark it as flaky
test: mark test-child-process-fork-args as flaky on Windows
test: mark test-child-process-fork-args as flaky on Windows
test: mark test-child-process-fork-args as flaky on Windows
test: mark test-child-process-fork-args as flaky on Windows
test: mark test-child-process-fork-args as flaky on Windows
Trott commentedon Aug 8, 2020
I'm not finding this error with
ncu-ci walk commitand 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 commentedon Aug 8, 2020
Stress test CI: https://ci.nodejs.org/job/node-stress-single-test/164/
Trott commentedon Aug 8, 2020
Stress test was green. PR to remove this from flaky tests; #34684
vweevers commentedon Aug 9, 2020
The exit code 1073741819 has been seen on AppVeyor builds too (of
sharp,sqlite3,prebuild-install,native-hdr-histogram) with 32-bit node when runningnpm run *or even justnpm -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)
test: remove test-child-process-fork-args flaky designation
test: remove test-child-process-fork-args flaky designation
test: remove test-child-process-fork-args flaky designation
test: remove test-child-process-fork-args flaky designation
test: remove test-child-process-fork-args flaky designation