You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the plan9/arm builder, the cmd/go tests are passing successfully because the timeout has been set to 18m. On this machine (Raspberry Pi 3), cmd/go tests takes approximately 14m to complete.
Maybe we should try to set GO_TEST_TIMEOUT_SCALE=2 on the plan9/386 builder.
The text was updated successfully, but these errors were encountered:
On the plan9-386 builder, the cmd/go tests sometimes
take a little more than 3 minutes to complete.
We set GO_TEST_TIMEOUT_SCALE=2, so the cmd/go tests
doesn't time out anymore.
Updates golang/go#18047
Change-Id: I16ce26917ee785ebed8ad16e0370d575a0fdd638
Reviewed-on: https://go-review.googlesource.com/33774
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
The cmd/go tests are regularly timing out after 3m on the plan9/386 builder. The issue happened the first time on 2016-11-18.
See https://build.golang.org/log/d0b1a47cba400dd5f3693a0702fe19385a73372c
On the plan9/arm builder, the cmd/go tests are passing successfully because the timeout has been set to 18m. On this machine (Raspberry Pi 3), cmd/go tests takes approximately 14m to complete.
Maybe we should try to set
GO_TEST_TIMEOUT_SCALE=2
on the plan9/386 builder.The text was updated successfully, but these errors were encountered: