Add a job that runs master + v10.x with `python tools/test.py --worker`

[addaleax]

Now that nodejs/node#20876 has landed, it would be great to have something in CI that runs the test suite under workers. It’s probably not feasible to make it part of a regular make test run, or add it to all CI nodes because the test suite is going to run twice as long that way.

Instead, I’d imagine we want a CI job for this. What do we need? Something in the Makefile + a job that runs that particular make target?

[maclover7]

@addaleax In theory we should be able to get this working with https://ci.nodejs.org/job/node-test-commit-custom-suites, using --worker as the input for TEST_ARGS, taking a look now

[addaleax]

@maclover7 Does that mean it would run only if requested? Because you’re right, that sounds doable, but I’d love to have it be part of node-test-commit

[maclover7]

@addaleax Yep, it technically runs on an "as requested" basis. But we can add a run of this job to node-test-commit like all of the other subjobs (node-test-commit-plinux, node-test-commit-arm, etc), or just node-daily-master if that's what's wanted

Giving this another run: https://ci.nodejs.org/job/node-test-commit-custom-suites/10/

[addaleax]

@maclover7 https://ci.nodejs.org/job/node-test-commit-custom-suites/10/nodes=rhel72-s390x/console looks like there’s some kind of encoding trouble?

[maclover7]

@addaleax Sorry this fell off my radar. Was able to get through ~2000 tests before getting two timeouts. Would you be be able to look into these failures? I believe you should have access to trigger builds of the node-test-commit-custom-suites job, where you can customize the arguments for python tools/test.py, and also pick the specific Jenkins node(s) that will run the job.

[addaleax]

@maclover Thanks! I have fixes for the timeouts in nodejs/node#21791. :)

(This is why I want to get this into node-test-commit, btw … 😄)