Investigate flaky test-stdout-close-catch on FreeBSD in CI

[Trott]

https://ci.nodejs.org/job/node-test-commit-freebsd/27488/nodes=freebsd11-x64/console on test-digitalocean-freebsd11-x64-1

00:20:42 not ok 1923 parallel/test-stdout-close-catch
00:20:42   ---
00:20:42   duration_ms: 120.101
00:20:42   severity: fail
00:20:42   exitcode: -15
00:20:42   stack: |-
00:20:42     timeout
00:20:42   ...

It seems to be timing out along with parallel/test-worker-message-port-message-before-close a fair amount. In addition to the one above, there's:

• https://ci.nodejs.org/job/node-test-commit-freebsd/27482/
• https://ci.nodejs.org/job/node-test-commit-freebsd/27468/

In all three cases, those two tests timed out.

@nodejs/testing @nodejs/platform-freebsd

[anandsuresh]

Seems like all 3 links in this ticket have expired. I'm unsure of how to gain access to test machines to be able to re-run/re-test this. @Trott any pointers?

[Trott]

Seems like all 3 links in this ticket have expired. I'm unsure of how to gain access to test machines to be able to re-run/re-test this. @Trott any pointers?

You can try to emulate locally of course. The entire relevant part of the log is reproduced above. Here's one that hasn't expired yet as of this writing:

https://ci.nodejs.org/job/node-test-commit-freebsd/nodes=freebsd11-x64/28495/console

And for posterity:

11:50:58 not ok 1969 parallel/test-stdout-close-catch
11:50:58   ---
11:50:58   duration_ms: 120.50
11:50:58   severity: fail
11:50:58   exitcode: -15
11:50:58   stack: |-
11:50:58     timeout
11:50:58   ...

If you want login access to the actual test machines, that can be requested with an issue in the nodejs/build repository, but you'll need one or two people on the Build team to vouch for you.

[saper]

Is this reproducible with a simple

ktrace -idf p1 node test/fixtures/catch-stdout-error.js | ktrace -idf p2 node -e "process.stdin.on('data' , () => process.exit(1))"

Also, do we need to use -p to print process.stdin to the stdout in the second process?

node/test/parallel/test-stdout-close-catch.js

Line 13 in 111e59b

'-pe "process.stdin.on(\'data\' , () => process.exit(1))"';

[sam-github]

Still happening: https://ci.nodejs.org/job/node-test-commit-freebsd/30771/

Should it be marked skip?

[sam-github]

https://ci.nodejs.org/job/node-test-commit-freebsd/32763/ still flaky

[targos]

Closing as there was no recent activity