investigate flaky test-domain-abort-on-uncaught #11814

This test is flaky under load. This can be seen by running it with a command like this:

tools/test.py -j 32 --repeat=32 test/parallel/test-domain-abort-on-uncaught.js

(If 32 isn't enough to cause problems on your setup, try 64 or higher.)

There are at least three solutions possible here:

• move the test to sequential
• break the test up into as many as 13 separate test files so that each one is launching one additional node process rather than one test launching 13 of them in parallel
• rewrite the test to run the 13 processes sequentially rather than in parallel

I'll open a PR to move to sequential. The second or third option above can be a good first contribution for someone.

Fix in #11817

• break the test up into as many as 13 separate test files so that each one is launching one additional node process rather than one test launching 13 of them in parallel
• rewrite the test to run the 13 processes sequentially rather than in parallel

I'll open a PR to move to sequential. The second or third option above can be a good first contribution for someone.

I'll open a new issue for this (as I assume this one will be closed by #11817).

EDIT: Issue raised: #11826