go: cmd/compile,runtime: frequent test timeouts on solaris-amd64-oraclerel
#!watchflakes
default <- builder == "solaris-amd64-oraclerel" && (pkg == "runtime" || pkg == "cmd/compile") && (`^panic: test timed out` || `failed to start: context deadline exceeded`)
greplogs --dashboard -md -l -e '(?ms)\Asolaris-amd64-oraclerel.*^panic: test timed out.*FAIL\s+runtime' --since=2022-01-01
2022-03-01T21:27:42-b0db2f0/solaris-amd64-oraclerel 2022-02-28T19:00:23-b33592d/solaris-amd64-oraclerel 2022-01-08T00:24:25-90860e0/solaris-amd64-oraclerel 2022-01-06T23:39:43-042548b/solaris-amd64-oraclerel
@golang/runtime: the builder appears to only run the -short tests. Is there something we can feasibly do to make -short mode shorter?
@golang/release, @rorth: would it make sense to set GO_TEST_TIMEOUT_SCALE on this builder to make the timeouts more generous?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (12 by maintainers)
Commits related to this issue
- dashboard: add known issue for solaris-amd64-oraclerel For golang/go#52653. Updates golang/go#51443. Change-Id: Iaea8fab13ed979e54c827f0f3c4d705bdaff4ee4 Reviewed-on: https://go-review.googlesource.... — committed to golang/build by bcmills 2 years ago
- dashboard: unmark known-issues with low failure rates I had initially added known issues fairly aggressively in order to use them to reduce noise in 'greplogs -triage'. Now that we are using 'watchfl... — committed to golang/build by bcmills a year ago
It makes sense to increase
GO_TEST_TIMEOUT_SCALEto me, but @rorth as the builder owner is in a better position to decide the optimal configuration for this builder. This builder is not configured as a TryBot, so if it needs more time, it’s fine and won’t affect pre-submit testing times (#17104).