Skip to content
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

x/build: missing test output in case of timeouts #34576

bcmills opened this issue Sep 27, 2019 · 2 comments

x/build: missing test output in case of timeouts #34576

bcmills opened this issue Sep 27, 2019 · 2 comments


Copy link

@bcmills bcmills commented Sep 27, 2019

The test log at ends with the following output:

Test "go_test:net" ran over 20m0s limit (20m0.036448368s)

That seems to imply that the test has deadlocked, but in order to diagnose the deadlock we need the goroutine dump, which is not present.

It is not obvious to me whether the lack of goroutine dump is a bug in the builder/buildlet sharding and logging path, in cmd/dist, or in the runtime.

Probably we should start the investigation with the builders.

CC @bradfitz @toothrot @dmitshur

Copy link
Member Author

@bcmills bcmills commented Sep 30, 2019

The examples of this sort of output seem to be numerous. I'm not sure when they started appearing.

Here's another one from over the weekend:

Copy link

@gopherbot gopherbot commented Oct 21, 2019

Change mentions this issue: cmd/coordinator: include command output in timeout failures

codebien added a commit to codebien/build that referenced this issue Nov 13, 2019
Fixes golang/go#34576

Change-Id: I77d85c311612bdbdcff665051659c2609a0af760
Reviewed-by: Dmitri Shuralyov <>
Reviewed-by: Bryan C. Mills <>
Run-TryBot: Brad Fitzpatrick <>
TryBot-Result: Gobot Gobot <>
@golang golang locked and limited conversation to collaborators Oct 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants