#!watchflakes
post <- builder ~ `(gotip|go1\.\d\d)-windows-amd64-longtest` && (`test timed out` || `SIGQUIT` || `context deadline exceeded` || status == "ABORT")
Go version
5647578230cab57e3befb9a736b045063e0156b5
What operating system and processor architecture are you using (go env)?
What did you do?
Add a gotip-windows-amd64-longtest LUCI Trybot on https://go.dev/cl/550237.
What did you expect to see?
Test results in 15 minutes or less, per #37439 (comment).
What did you see instead?
Testing on gotip-windows-amd64-longtest took 26½ minutes (http://ci.chromium.org/b/8761608988288421329).
Perhaps the builder sharding needs to be adjusted? (Maybe there are differences in machine speed or load that cause the LUCI builders to be slower than the legacy TryBots?)
Go version
5647578230cab57e3befb9a736b045063e0156b5
What operating system and processor architecture are you using (
go env)?What did you do?
Add a
gotip-windows-amd64-longtestLUCI Trybot on https://go.dev/cl/550237.What did you expect to see?
Test results in 15 minutes or less, per #37439 (comment).
What did you see instead?
Testing on
gotip-windows-amd64-longtesttook 26½ minutes (http://ci.chromium.org/b/8761608988288421329).Perhaps the builder sharding needs to be adjusted? (Maybe there are differences in machine speed or load that cause the LUCI builders to be slower than the legacy TryBots?)