-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: test timeout on netbsd/arm #24774
Comments
There's also #24591 for the recent spike of timeout issues on multiple builders and tests. I imagine that the issues are different, since that one involves |
You might need to crank up that TIMEOUT_SCALE environment variable that's often needed with the slower machines. |
The They do still seem to time out: https://build.golang.org/log/f397d8329c98f733558168f03017f9e0589f927a is a recent example. |
Wait, that's amd64, not arm! |
The |
@bsiegert, are these tests still timing out? Is there some way for us to reproduce these failures? |
The builder is on my desk at work, I'll reboot it on Monday. I assume NetBSD/arm runs in qemu, though I haven't tested. Unfortunately, Scaleway VMs do not run 32-bit code so they cannot be used to test this. |
Rebooted and cleaned up the state of its git repo, which is what had been causing these I'll need to take the machine offline for a bit later today but I'll let it run some builds in the meantime. I also remounted its filesystem with |
And it looks like it's just slowness:
https://build.golang.org/log/2f7edd8edfffbb73680af3f141ac3497c9cc1181 |
The tests for cmd/go keep timing out (after 6 minutes) on the netbsd-arm builder. Not sure if they are just slow, or indicating a synchronization problem of some sort.
Here is a typical log from a recent build:
/cc @tklauser @bradfitz
The text was updated successfully, but these errors were encountered: