cmd/dist: request to increase user higher test timeout scale for ARM #43002
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Most likely (see #42798), but we carry carry the fix in Ubuntu so I'm not absolutely sure.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Ran a test on armhf:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/g/golang-gopkg-square-go-jose.v2/20200706_025803_f6666@/log.gz
What did you expect to see?
Test passing, like on all other architectures.
What did you see instead?
Internal test timeout:
Also reported as https://bugs.launchpad.net/ubuntu/+source/golang-gopkg-square-go-jose.v2/+bug/1893640 and fixed in Ubuntu by bumping arm's timeout scale to 3 from 2.
I had hard time resulting only a failure to get cross-company CLA signed, thus I'm not filing a PR, but the change is trivial. Please consider applying it.
The reasoning is that most developers use (faster) amd64 machines setting the test timeouts, but test may run on slower arm ones and also different tests may suffer different relative slowdown on the arm CPUs.
Due to those two varying factors it is safer to allow a higher timeout scale on arm to avoid tests timing out.
The text was updated successfully, but these errors were encountered: