Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
x/build: missing test output in case of timeouts #34576
The test log at https://build.golang.org/log/5f3ee279eff750a1e1fbb46a5866d993c36ca7a0 ends with the following output:
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
Probably we should start the investigation with the builders.
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: https://build.golang.org/log/9ec791ff66e9d9d62b6f45049c0934552a176110
Fixes golang/go#34576 Change-Id: I77d85c311612bdbdcff665051659c2609a0af760 Reviewed-on: https://go-review.googlesource.com/c/build/+/202477 Reviewed-by: Dmitri Shuralyov <firstname.lastname@example.org> Reviewed-by: Bryan C. Mills <email@example.com> Run-TryBot: Brad Fitzpatrick <firstname.lastname@example.org> TryBot-Result: Gobot Gobot <email@example.com>