Control: retitle -1 golang-google-grpc: Tests sometimes time out on mips Control: severity -1 important
Sebastian Ramacher <[email protected]> writes: > > https://buildd.debian.org/status/fetch.php?pkg=golang-google-grpc&arch=mipsel&ver=1.33.3-2%2Bb1&stamp=1675949301&raw=0 This snippet misses the relevant part: tlogger.go:99: clientconn.go:428 [core] Channel Connectivity change to CONNECTING (t=+4.339825666s) panic: test timed out after 10m0s goroutine 49343 [running]: testing.(*M).startAlarm.func1() /usr/lib/go-1.19/src/testing/testing.go:2036 +0xfc created by time.goFunc /usr/lib/go-1.19/src/time/sleep.go:176 +0x58 goroutine 1 [chan receive, 9 minutes]: testing.(*T).Run(0x19043c0, {0xb443b5, 0x4}, 0xb79918) /usr/lib/go-1.19/src/testing/testing.go:1494 +0x460 testing.runTests.func1(0x19043c0) /usr/lib/go-1.19/src/testing/testing.go:1846 +0xa0 testing.tRunner(0x19043c0, 0x1965e44) /usr/lib/go-1.19/src/testing/testing.go:1446 +0x184 testing.runTests(0x1920630, {0xf30fa8, 0x1, 0x1}, {0xc0f15b18626e5c47, 0x8bb37fbc9d, 0xf7a0c0}) /usr/lib/go-1.19/src/testing/testing.go:1844 +0x4cc testing.(*M).Run(0x19328c0) /usr/lib/go-1.19/src/testing/testing.go:1726 +0x778 main.main() _testmain.go:47 +0x204 goroutine 35 [chan receive]: testing.(*T).Run(0x19044b0, {0xa8bfa3, 0x14}, 0x19582f0) /usr/lib/go-1.19/src/testing/testing.go:1494 +0x460 google.golang.org/grpc/internal/grpctest.RunSubTests(0x19044b0, {0xb42f80, 0xf8c708}) /<<PKGBUILDDIR>>/_build/src/google.golang.org/grpc/internal/grpctest/grpctest.go:99 +0x408 google.golang.org/grpc/test.Test(0x19044b0) /<<PKGBUILDDIR>>/_build/src/google.golang.org/grpc/test/end2end_test.go:86 +0x58 testing.tRunner(0x19044b0, 0xb79918) /usr/lib/go-1.19/src/testing/testing.go:1446 +0x184 created by testing.(*T).Run /usr/lib/go-1.19/src/testing/testing.go:1493 +0x440 > > created by google.golang.org/grpc/test.(*test).listenAndServe > > /<<PKGBUILDDIR>>/_build/src/google.golang.org/grpc/test/end2end_test.go:674 > +0x22c8 > FAIL google.golang.org/grpc/test 600.036s Looking at the source, the test that is failing is an end-to-end test that starts an grpc server and tests various functionality. The stack trace indicates crypt operations being processed. It looks to me that the machine is simply too slow to complete the test in a timely fashion. We can either skip the test or increase the timeout. I'm leaning towards extending the timeout. Best, -rt
