test: investigate crash in `parallel/test-timers-uncaught-exception`

[refack]

• Version: master
• Platform: freeBSD11-x64
• Subsystem: test,timers

1191	parallel/test-timers-uncaught-exception	
duration_ms	0.282
severity	crashed
stack	|-
oh no!
exit code: CRASHED (Signal: 11)

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

[refack]

/cc @nodejs/platform-freebsd

[misterdjules]

Are there core files generated on these FreeBSD test machines? If so it would be helpful to get a stack trace from that. Otherwise we'll need to reproduce the crash.

If not, would it be helpful to setup core file generation and cleanup as was done for SmartOS test machines?

[Trott]

@nodejs/build Can we accommodate @misterdjules's request above about core files on FreeBSD machines?

[refack]

Should this be a new issue?

1531	sequential/test-net-listen-shared-ports	
duration_ms	1.72
severity	crashed
stack	oh no!
exit code: CRASHED (Signal: 11)

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

[Trott]

Should this be a new issue?

Since it appears to be the same issue, I suspect we should change the name of this issue and consider it a "oh no, FreeBSD is crashing on tests sometimes!" thing. I'd guess they're probably related if not exactly the same thing.

[BridgeAR]

Ping @nodejs/platform-freebsd @nodejs/testing please have a look. It would be great to have a green CI before the next Code & Learn and this might be related to other flaky tests on freebsd as well.

[maclover7]

Did a stress test, and it looks like this test is working better now. Since no reports for several months, going to close this. Please open if I'm mistaken, or if test starts flaking again :)