incident: z/OS hosts down

[refack]

https://ci.nodejs.org/label/zos-s390x/

@jBarz @mhdawson @nodejs/platform-s390

P.S. I see we only test libuv and not node, is that intentional?

[refack]

Any news? Should we remove these workers?

[mhdawson]

@refack we only test libuv as we don't have all of the contributions required for Node.js yet. Still working on that.

Just back from vacation. See nobody else chimed in, thats because @jBarz left IBM and we still need to get somebody else into zos-s390x

[mhdawson]

@gdams can you chase what's going on here and add yourself to platform-s390.

[gdams]

okay so here's the steps to bring the machines back online:

ssh unix1@<zos_host>
sh /u/iojs/start.sh

[gdams]

test build looking good: https://ci.nodejs.org/job/libuv-test-commit-zos/nodes=zos-s390x/938/console

[refack]

FTR: the default shell does not recognize su - -s iojs, but bash does.

[joaocgreis]

@mhdawson @sam-github All z/OS hosts were down, with a few libuv jobs queued up. I brought them back using the instructions above, but all of the builds that were queued turned red. Possibly because of some missing configuration.

• https://ci.nodejs.org/computer/test-marist-zos13-s390x-1/builds
• https://ci.nodejs.org/computer/test-marist-zos13-s390x-2/builds

[sam-github]

Hm, kicked off another build: https://ci.nodejs.org/job/libuv-test-commit-zos/1693/

[sam-github]

I'd prefer we close this issue and open another, since it doesn't seem related - I'd rather not have a floating issue per host type that gets reopened whenever that host is down.

@nodejs/platform-s390 would you agree? Shall I open another to track this latest issue, which seems it may be caused by the python updates (though that's still being looked into)?

[mhdawson]

@joaocgreis thanks for pointing this out. I had noticed earlier today when I got emails saying all those jobs failed. I had wondered why I just got them today, but makes sense if they were queued. @sam-github is following up on this issue.

@sam-github I agree a new issue makes sense to me.

[sam-github]

new issue, for new problem: #1855