Stewart X Addison

[EDIT: User error - after I got past the authentication/connection issues I had switched back to a different user which didn't have access to the database file I was accessing,...

Changed the title

> (Is it too optimistic to hope the https://github.com/nodejs/build/issues/2948 makes a difference? slightly_smiling_face) I suspect so ;-) I brought it back online earlier today and will contact WorksOnArm regarding the...

It looks like one of them may not have been started after the previous maintenance window. For the other one (which has been unreliable for us) Equinix have provided me...

Looks to be down again. Let's not bring it back. I've got the playbook running at the moment which will bring up the `-3` machine with direct replacements (same names)...

Confirmed via email

Most recent jobs before the crash seem to have been `centos7-arm64-gcc6` ones -although they were listed as `SUCCESS` (This is from the jenkins server log): ``` 2022-07-16 06:08:53:620 - AuditLog...

Have taken [the second centos7 container](https://ci.nodejs.org/computer/test-equinix-centos7_container-arm64-2/) offline and currently repeatedly running the centos7 gcc6 job repeatedly on the "failing" altra. I will also add in the ubuntu2004-armv7l combination in future...

I've brought https://ci.nodejs.org/computer/test-equinix-ubuntu2004_container-armv7l-2/ back online to clear the backlog. test-equinix-ubuntu2004-arm64-1 - 145.40.81.219 - had gone offline for the first time in a while so we'll need to re-evaluate what's going...

FYI the builds really are using about 14GB while in flight: During build (while running tests): ``` /dev/disk1s1 53710936 39596968 1474908 97% 284892 536824468 0% /System/Volumes/Data ``` After build (Workspace...