runtime: test frequently times out after 10 minutes on linux-amd64-longtest builder

[mvdan]

For example: https://build.golang.org/log/9b5c6ae2c5be87e49c9893e9ea6dcc2aa6198200

The builder has been consistently broken for this and other reasons since mid-May, so it's hard to pinpoint when this failure started happening. I tried looking for an existing issue about this, but couldn't find any.

If I run go test -v runtime on my laptop, I get the result:

ok      runtime 171.977s

Perhaps the three-minute timeout per package is too low for the runtime package, seeing as how my run barely fit under 180s. Or perhaps some of the long or expensive tests should be made faster.

/cc @aclements @ianlancetaylor @bradfitz

Tangential question - should this be labelled Testing or Builders? Perhaps the label descriptions could be clarified.

[ALTree]

I bumped the timeout to 6 minutes in CL 115016.

Either I did it wrong or it's not deployed yet.

[ALTree]

p.s. I thinks this should be labeled "builders".

[mvdan]

Ah, I forgot to remove the is:open filter from my issue search. It didn't occur to me that the issue was already closed. I naively assumed that it couldn't have been, since the problem is still present :)

Then yes, this seems like it should be labelled Builders. Do you want to keep this issue open to track the deployment/debugging of your fix?

[ALTree]

Do you want to keep this issue open to track the deployment/debugging of your fix?

I guess we could do this to avoid someone else opening another one : ) Once the version with the new time limit is deployed we can close.