Access to arm32 build machines for @ShogunPanda

[Trott]

From @ShogunPanda:

@nodejs/build

Some tests is failing on ARM but not on my machine. May I get access to the CI machine?

Originally posted by @ShogunPanda in https://github.com/nodejs/node/issues/41263#issuecomment-1060751903

[mhdawson]

+1 from me.

[sxa]

Bear in mind that from what I can see it's only the ARM 32-bit builds that are showing failing tests from what I can see, so this will need access to our arm32 infrastructure ... (Either a docker container or @rvagg's systems)

[sxa]

@ShogunPanda You should be able to connect with:

ssh -p 2888 [email protected]

There's a copy of your built branch in the node directory with the output from make test showing the failure in there too.

Let me know when you're finished with the system (Note that it's running an aarch64 kernel but I don't believe that affects the problem you're seeing)

[sxa]

@shogunpanda Is this access suitable for your debugging?

[ShogunPanda]

I haven't tried yet, I was too busy on work stuff. I'll let you know ASAP.

[ShogunPanda]

Ok, I just tried and was successfully able to debug the issue. There two tests still failing by they look unrelated to my changes.

I think you can dispose this access if you need it, otherwise I'll use it later to debug the other failings. Am I free to pull the latest version of my PR?

[sxa]

You're welcome to hold onto the machine just and yes - feel free to do whatever you want with the repository on there.

[ShogunPanda]

I think you can close this.

[Trott]

I guess I'll let someone who knows for a fact that the relevant key has been removed (thus disabling access) to close this rather than closing it myself. @nodejs/build

[github-actions[bot]]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

[sxa]

Confirmed - closing.