/ go Public
x/build: increase timeouts or reduce parallelism on darwin-arm-mg912baios builder? #32024
x/build issues (builders, bots, dashboards)
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
An issue that has been verified to require only test changes, not just a test failure.
There is a strange effect visible in this log on the
The tests are running along fine for a while, and when they get to the (presumably CPU-intensive)
hash/*tests they suddenly dropm from ~150s per test to ~19m per test.
The first couple of
imagetests are similarly slow, but then the builder seems to recover:
I wonder if that implies some sort of resource contention (perhaps a thermal limit?) between the tests — should we reduce the parallelism of that builder to decrease the likelihood of spurious timeouts?
CC @eliasnaur @steeve @bradfitz @dmitshur
The text was updated successfully, but these errors were encountered: