trybots not running tests after 1 failure?

[Russ Cox]

https://go-review.googlesource.com/c/go/+/87155/3 produced a failure on linux-amd64: https://storage.googleapis.com/go-build-log/91a88879/linux-amd64_d0111c6d.log.

Why does the test log stop at cmd/go? "go test std cmd" would have continued on running the remaining directories from "go list std cmd", namely cmd/gofmt, link, nm, and so on. But they were not run. Can we fix that?

I know that if the std+cmd tests fail then we don't run things like the race tests or misc/cgo/foo, and that's fine. But we should finish the std+cmd tests even when one fails.

Thanks.

Russ

[Brad Fitzpatrick]

The builders don't run "go test std cmd".

To shard tests over different machines, they first run "go tool dist test --list", and then shard those tests over all builders.

I suppose it could do something different, but right now it prioritizes telling you something failed as soon as possible.

--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.