x/build: arm5 builders are gone again, remove port?

[bradfitz]

@zeebo, what's the status with the ARM5 Spacemonkey builders?

We haven't seen them in quite some time.

/cc @bcmills @dmitshur

[zeebo]

I don’t think they’re maintained anymore. I’m 👍 on removing.

I’ll link this issue around to some former coworkers to see if they want to own it.

[bradfitz]

@zeebo, you're still listed as the owner at https://farmer.golang.org/builders

Should I remove you? Looks like you're at Storj now? Do you know anybody at Space Monkey that wants to run them?

[esnolte]

We didn't realize they were offline. Where are the directions for how the builders need to be configured? I'll work on bringing them back online.

[bradfitz]

@esnolte, you at Space Monkey? Should I list you as the new owner?

Do you have physical access to the old machines? They should already be configured.

[esnolte]

Yes, I'm at Space Monkey (now part of Vivint). List me as the new owner until we figure out something better. The old machines were moved across the office and either weren't plugged in or have some sort of network connectivity issue. I'll ping people in the office to see what their status is and fix them Tuesday if we can't get them working today.

[gopherbot]

Change https://golang.org/cl/202019 mentions this issue: dashboard: update linux-arm-arm5 owner

[esnolte]

2 of our 3 Go builders are online and appear to be handling builds according to the pool display:
linux-arm-arm5spacemonkey rev 5375c71; failed, 3m16s ago

I'm not sure if/when the status shows up on the dashboard.

[ghost]

I vote for removal of armv5. Now even Cortex-R supports v7 instructions.

[esnolte]

We have 200,000+ devices running this architecture that we regularly update the software on. We'd prefer to run the latest Go rather than be stuck at an old release.

[bradfitz]

@esnolte, then it's on you to keep builders up & running. We can only support what we can test.

[bcmills]

The builder is back, but it's still persistently broken (#32407 again).

[cagedmantis]

I'm going to close this issue since it seems like we found a new maintainer at this point in time.