Flaky `node-test-commit-v8-linux` suite on Jenkins

[bcoe]

It appears as thought the node-test-commit-v8-linux test suite has not passed for any environment except ppcle-ubuntu1404 for quite some time:

I propose that we either remove these other three tests, if they're not needed, or we should prioritize getting them passing again.

@nodejs/testing, @nodejs/build

[richardlau]

This is a known issue (#30152). V8's build scripts are not compatible with Python 3.

[richardlau]

cc @AshCripps @sam-github We did have the V8 CI passing on rhel7-s390x (nodejs/build#2080 (comment)) so something seems to have regressed.

[AshCripps]

cc @AshCripps @sam-github We did have the V8 CI passing on rhel7-s390x (nodejs/build#2080 (comment)) so something seems to have regressed.

The socket time out issues are back it seems

[AshCripps]

I added the v8test label to test-ibm-rhel7-s390x-3 and ran a job on it which passed: https://ci.nodejs.org/job/node-test-commit-v8-linux/2789/nodes=rhel7-s390x,v8test=v8test/

I also ran a job on the failing test-ibm-rhel7-s390x-2 which is still ongoing: https://ci.nodejs.org/job/node-test-commit-v8-linux/2787/nodes=rhel7-s390x,v8test=v8test/console. The job took a long time (around 8 minutes) to perform the git clone.

The two console outputs are wildly different as well

[bcoe]

closing in favor of #30152