Description
As of CL 231223, the dragonfly-amd64-5_8 builder (and only that builder) is consistently timing out on the cmd/go tests, during one of the script tests:
https://build.golang.org/log/fb00e74ea4d50113498d60db4d6b30c09ee0a4ea
The builder goes unresponsive enough that the test's usual timeout behavior doesn't halt the test in time, so all we get is a goroutine dump from the test process (which does not reveal the source of the hang).
I tried to use gomote ssh to investigate, but it failed due to a configuration error (#38796):
~/go/src$ mote ssh
$ ssh -p 2222 [email protected] # auth using https://github.com/bcmills.keys
Enter passphrase for key '/usr/local/google/home/bcmills/.ssh/id_rsa':
instance "user-bcmills-dragonfly-amd64-5_8-0" host type "host-dragonfly-amd64-5_8" does not have SSH configured
Connection to farmer.golang.org closed.
I don't see how CL 231223 could be causing deadlocks, since it is mostly a straight refactor, but I tried a revert (in CL 231557) and it passed as a SlowBot. So I'm not sure what to do about that: I hate to roll back based on a seemingly-unrelated failure on a builder I can't even access, especially given that the mainline dragonfly-amd64 builder is still passing.
If I could at least figure out which test is deadlocking, I could add a skip for that test on the theory that it's likely a bad interaction with a kernel bug...