all: builders seeing test timeouts in various packages

[mvdan]

Some recent ones:

• cmd/link/internal/ld: https://build.golang.org/log/605bbee54f3f3bfa763b4185583b0cc550dee6e8
• runtime: https://build.golang.org/log/63f6888c9a4ac251a0f1dbca2369679afc2c5835
• cmd/fix: https://build.golang.org/log/d11055331cfdb560e1ef22854c786d5a146b80b6

This seems to have started sometime around the 28th of March: https://build.golang.org/

Since it's not a single package, and they don't seem to be related, this seems like a runtime or compiler issue. /cc @aclements @josharian @mdempsky

[mvdan]

Josh filed an issue about flaky network tests that time out, but I doubt the two related: #24580

[mvdan]

I've looked through all the recent failures, and I only see these three packages plus net. I wonder what's special about them.

[josharian]

Are all the hangs while exec'ing external tools? The first two I looked at were.

Maybe there are underlying resource conflicts causing the exec to get significantly delayed.

[mvdan]

The three I linked above seem to be while running an external tool, yes. I haven't gone through all of them, as most seem to be duplicates.

[bradfitz]

Let's close this in favor of concrete bugs for certain packages.

It's likely that certain packages are now running up against the default 3 minute timeout.

Another reason to close this: this predates the move away from Kubernetes pods to dedicated VMs for Linux builders, so we have better isolation now.