go test times out on armhf

Bug #1893640 reported by Balint Reczey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Auto Package Testing
Fix Released
Undecided
Unassigned
golang (Ubuntu)
Fix Released
Undecided
Unassigned
golang-gopkg-square-go-jose.v2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

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
...
=== RUN TestOpaqueKeyRoundtripJWE
panic: test timed out after 10m0s

goroutine 22 [running]:
testing.(*M).startAlarm.func1()
 /usr/lib/go-1.14/src/testing/testing.go:1459 +0xbc
created by time.goFunc
 /usr/lib/go-1.14/src/time/sleep.go:168 +0x34

goroutine 1 [chan receive, 4 minutes]:
testing.(*T).Run(0xcb2b40, 0x3cc3f5, 0x19, 0x3f679c, 0x301)
 /usr/lib/go-1.14/src/testing/testing.go:1043 +0x2d0
testing.runTests.func1(0xcb2280)
 /usr/lib/go-1.14/src/testing/testing.go:1284 +0x68
testing.tRunner(0xcb2280, 0xcf9ef8)
 /usr/lib/go-1.14/src/testing/testing.go:991 +0xbc
testing.runTests(0x102ea00, 0x6cad78, 0x73, 0x73, 0x0)
dh_auto_test: error: cd obj-arm-linux-gnueabihf && go test -vet=off -v -p 4 gopkg.in/square/go-jose.v2 gopkg.in/square/go-jose.v2/cipher gopkg.in/square/go-jose.v2/cryptosigner gopkg.in/square/go-jose.v2/json gopkg.in/square/go-jose.v2/jwt returned exit code 1
 /usr/lib/go-1.14/src/testing/testing.go:1282 +0x238
testing.(*M).Run(0xc58440, 0x0)
 /usr/lib/go-1.14/src/testing/testing.go:1199 +0x134
main.main()
 _testmain.go:594 +0x120
...

Revision history for this message
Balint Reczey (rbalint) wrote :
Balint Reczey (rbalint)
Changed in golang-gopkg-square-go-jose.v2 (Ubuntu):
status: New → Invalid
Changed in golang (Ubuntu):
status: New → Fix Released
Revision history for this message
Balint Reczey (rbalint) wrote :
Revision history for this message
Balint Reczey (rbalint) wrote :

As an alternative to carrying a patch against Go GO_TEST_TIMEOUT_SCALE= should be set on the test runners which are known to be slower than expected by the Go upstream (armhf).

Revision history for this message
Balint Reczey (rbalint) wrote :

With the newly deployed faster ARM hardware this issue hopefully disappeared. At lease I don't observe it frequently.

Changed in auto-package-testing:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.