runtime: TestCgoCallbackGC failures
#!watchflakes
post <- pkg == "runtime" && test == "TestCgoCallbackGC"
Issue created automatically to collect these failures.
Example (log):
--- FAIL: TestCgoCallbackGC (0.00s)
crash_test.go:58: /var/gobuilder/buildlet/tmp/go-build2870843524/testprogcgo.exe CgoCallbackGC failed to start: context deadline exceeded
panic: finalizer started 14.186166497s ago (38.476234ms after registration) and ran 210 iterations, but did not return
goroutine 141876 [running]:
panic({0x35bfe0, 0x400005a010})
/var/gobuilder/buildlet/go/src/runtime/panic.go:987 +0x3ac fp=0x4000772f20 sp=0x4000772e60 pc=0x492ac
runtime_test.TestStackGrowth.func4()
/var/gobuilder/buildlet/go/src/runtime/stack_test.go:134 +0x11c fp=0x4000772fd0 sp=0x4000772f20 pc=0x304abc
runtime.goexit()
/var/gobuilder/buildlet/go/src/runtime/asm_arm64.s:1172 +0x4 fp=0x4000772fd0 sp=0x4000772fd0 pc=0x83574
created by time.goFunc
/var/gobuilder/buildlet/go/src/time/sleep.go:176 +0x38
goroutine 19 [running]:
goroutine running on other thread; stack unavailable
created by runtime.gcBgMarkStartWorkers
/var/gobuilder/buildlet/go/src/runtime/mgc.go:1199 +0x28
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "runtime" && test == "TestCgoCallbackGC"
2022-12-16 03:40 netbsd-arm64-bsiegert go@24ac659a runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (0.00s)
crash_test.go:58: /var/gobuilder/buildlet/tmp/go-build2870843524/testprogcgo.exe CgoCallbackGC failed to start: context deadline exceeded
panic: finalizer started 14.186166497s ago (38.476234ms after registration) and ran 210 iterations, but did not return
goroutine 141876 [running]:
panic({0x35bfe0, 0x400005a010})
/var/gobuilder/buildlet/go/src/runtime/panic.go:987 +0x3ac fp=0x4000772f20 sp=0x4000772e60 pc=0x492ac
runtime_test.TestStackGrowth.func4()
/var/gobuilder/buildlet/go/src/runtime/stack_test.go:134 +0x11c fp=0x4000772fd0 sp=0x4000772f20 pc=0x304abc
runtime.goexit()
/var/gobuilder/buildlet/go/src/runtime/asm_arm64.s:1172 +0x4 fp=0x4000772fd0 sp=0x4000772fd0 pc=0x83574
created by time.goFunc
/var/gobuilder/buildlet/go/src/time/sleep.go:176 +0x38
goroutine 19 [running]:
goroutine running on other thread; stack unavailable
created by runtime.gcBgMarkStartWorkers
/var/gobuilder/buildlet/go/src/runtime/mgc.go:1199 +0x28
#32023 may be related. Are they same?
#57381, #57380, #57377, #56584, #56580 were all on the same builder. CC @golang/netbsd
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "runtime" && test == "TestCgoCallbackGC"
2022-11-18 23:57 openbsd-386-71 go@04d6aa65 runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (0.00s)
crash_test.go:58: /tmp/workdir/tmp/go-build3123997662/testprogcgo.exe CgoCallbackGC failed to start: context deadline exceeded
2022-11-21 17:16 openbsd-amd64-71 go@998949c0 runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (0.00s)
crash_test.go:58: /tmp/workdir/tmp/go-build1527382388/testprogcgo.exe CgoCallbackGC failed to start: context deadline exceeded
2022-12-06 19:52 openbsd-386-71 go@03bf6f49 runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (0.00s)
crash_test.go:58: /tmp/workdir/tmp/go-build719402250/testprogcgo.exe CgoCallbackGC failed to start: context deadline exceeded
2022-12-16 17:12 openbsd-amd64-71 go@f4b42f5c runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (0.00s)
crash_test.go:58: /tmp/workdir/tmp/go-build3915581810/testprogcgo.exe CgoCallbackGC failed to start: context deadline exceeded
#57585 / #57847
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "runtime" && test == "TestCgoCallbackGC"
2023-01-26 07:17 darwin-amd64-10_15 go@cea70301 runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (0.06s)
crash_test.go:58: /tmp/buildlet/tmp/go-build4119296738/testprogcgo.exe CgoCallbackGC: signal: segmentation fault
crash_cgo_test.go:74: expected "OK\n", but got:
2023-01-26 07:17 darwin-amd64-11_0 go@cea70301 runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (0.20s)
crash_test.go:58: /tmp/buildlet/tmp/go-build2556092564/testprogcgo.exe CgoCallbackGC: signal: segmentation fault
crash_cgo_test.go:74: expected "OK\n", but got:
2023-01-26 10:15 darwin-amd64-10_15 go@4df10fba runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (0.02s)
crash_test.go:58: /tmp/buildlet/tmp/go-build1310876794/testprogcgo.exe CgoCallbackGC: signal: segmentation fault
crash_cgo_test.go:74: expected "OK\n", but got:
2023-01-26 10:15 darwin-amd64-11_0 go@4df10fba runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (0.09s)
crash_test.go:58: /tmp/buildlet/tmp/go-build4292740019/testprogcgo.exe CgoCallbackGC: signal: segmentation fault
crash_cgo_test.go:74: expected "OK\n", but got:
#58068
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "runtime" && test == "TestCgoCallbackGC"
2023-04-19 14:36 linux-s390x-ibm go@9cad0cc6 runtime.TestCgoCallbackGC (log)
--- FAIL: TestCgoCallbackGC (2.82s)
exec.go:146: test timed out while running command: /data/golang/workdir/tmp/go-build1486251316/testprogcgo.exe CgoCallbackGC
crash_cgo_test.go:71: /data/golang/workdir/tmp/go-build1486251316/testprogcgo.exe CgoCallbackGC failed to start: context deadline exceeded
panic: test timed out after 3m0s
running tests:
TestCgoExternalThreadSignal (3s)
TestFakeTime (13s)
TestMemmoveOverlapLarge0x120000 (13s)
TestStackGrowth (13s)
goroutine 182435 [running]:
panic({0x46eaa0, 0xc000a9a1c0})
/data/golang/workdir/go/src/runtime/panic.go:1016 +0x4c6 fp=0xc000278ef8 sp=0xc000278e50 pc=0x584e6
testing.(*M).startAlarm.func1()
/data/golang/workdir/go/src/testing/testing.go:2260 +0x47a fp=0xc000278fd8 sp=0xc000278ef8 pc=0x14de3a
runtime.goexit()
/data/golang/workdir/go/src/runtime/asm_s390x.s:749 +0x2 fp=0xc000278fd8 sp=0xc000278fd8 pc=0xa26f2
created by time.goFunc
/data/golang/workdir/go/src/time/sleep.go:176 +0x42
goroutine 9 [running]:
goroutine running on other thread; stack unavailable
created by runtime.gcBgMarkStartWorkers in goroutine 6
/data/golang/workdir/go/src/runtime/mgc.go:1221 +0x34
@cherrymui points out that there are existing s390x timeout issues related to TestStackGrowth.
The failure in https://github.com/golang/go/issues/57379#issuecomment-1515264122 doesn't look particularly specific to TestCgoCallbackGC or TestStackGrowth — nothing seems to be wedged, it looks like the builder just took a little too long to run the runtime tests overall.
(That failure probably belongs in #58901, but went to this issue because both match and this one is older.)
(I suggest that this issue be closed and removed from the Test Flakes project so that new failures will go to the other open issues.)
Agreed. Done.