Need shell access to `test-ibm-rhel8-s390x` machine

Context

I've this PR => https://github.com/nodejs/node/pull/54857 which consistently fails at https://ci.nodejs.org/computer/test-ibm-rhel8-s390x-1/. All other machines do pass but for some reason /test-ibm-rhel8-s390x fails with a timeout. Here's a link to the latest CI run => https://ci.nodejs.org/job/node-test-pull-request/68149/

Local reproduction Efforts

I've tried to reproduce the issue locally by emulating both a general linux on top of s390x and rhel8 specifically on s390x like below

docker run -it --platform linux/s390x --mount type=bind,src=.,dst=/usr/node -w /usr/node ubuntu:22.04 /bin/bash

and

docker run -it --platform linux/s390x --mount type=bind,src=.,dst=/usr/node -w /usr/node registry.access.redhat.com/ubi8:latest /bin/bash

Both of the scenarios took 5-6 hours to build and did not reproduce the issue I faced.

Note: My machine

MacBook M1 Pro

Solution

I think what's left for me is to shell into the actual testing machine and try to debug over there. Upon @joyeecheung 's suggestion, I'm opening this issue to debug the issue.

Start with PR 54857, the test-ibm-rhel8-s390x machine page, and CI job 68149 to review the timeout context. The work is done when shell access to the actual testing machine is available and the failure can be investigated there.