runtime: TestSegv failures with `did not see "SIGSEGV" in output`

[gopherbot]

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/SegvInCgo (0.01s)
        crash_test.go:58: /scratch/gobuilder/buildlet/tmp/go-build3109463291/testprogcgo.exe SegvInCgo (11.518812ms): ok
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv"

2023-01-16 08:37 netbsd-arm64-bsiegert go@1c65b69b runtime.TestSegv (log)

--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/SegvInCgo (0.01s)
        crash_test.go:58: /scratch/gobuilder/buildlet/tmp/go-build3109463291/testprogcgo.exe SegvInCgo (11.518812ms): ok
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output

2023-01-19 20:45 netbsd-arm64-bsiegert go@fbf14ae1 runtime.TestSegv (log)

--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/SegvInCgo (0.03s)
        crash_test.go:58: /var/gobuilder/buildlet/tmp/go-build733110322/testprogcgo.exe SegvInCgo (25.795671ms): ok
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output

— watchflakes

[bcmills]

Both on netbsd-arm64-bsiegert so far. 🤔

(Attn @bsiegert @golang/netbsd; CC @golang/runtime.)

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`

2023-01-18 20:42 netbsd-arm64-bsiegert go@5adb0ca8 runtime.TestSegv (log)

--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/Segv (0.01s)
        crash_test.go:58: /scratch/gobuilder/buildlet/tmp/go-build2434025212/testprogcgo.exe Segv (11.701045ms): ok
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output

2023-01-26 07:17 darwin-amd64-10_15 go@cea70301 runtime.TestSegv (log)

--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/Segv (0.03s)
        crash_test.go:58: /tmp/buildlet/tmp/go-build4119296738/testprogcgo.exe Segv: signal: segmentation fault
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output
        crash_cgo_test.go:633: skipping known flaky test without the -flaky flag; see golang.org/issue/49182
    --- FAIL: TestSegv/SegvInCgo (0.03s)
        crash_test.go:58: /tmp/buildlet/tmp/go-build4119296738/testprogcgo.exe SegvInCgo: signal: segmentation fault
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output
        crash_cgo_test.go:633: skipping known flaky test without the -flaky flag; see golang.org/issue/49182

2023-01-26 07:17 darwin-amd64-11_0 go@cea70301 runtime.TestSegv (log)

--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/Segv (0.04s)
        crash_test.go:58: /tmp/buildlet/tmp/go-build2556092564/testprogcgo.exe Segv: signal: segmentation fault
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output
        crash_cgo_test.go:633: skipping known flaky test without the -flaky flag; see golang.org/issue/49182
    --- FAIL: TestSegv/SegvInCgo (0.03s)
        crash_test.go:58: /tmp/buildlet/tmp/go-build2556092564/testprogcgo.exe SegvInCgo: signal: segmentation fault
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output
        crash_cgo_test.go:633: skipping known flaky test without the -flaky flag; see golang.org/issue/49182

2023-01-26 10:15 darwin-amd64-10_15 go@4df10fba runtime.TestSegv (log)

--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/SegvInCgo (0.02s)
        crash_test.go:58: /tmp/buildlet/tmp/go-build1310876794/testprogcgo.exe SegvInCgo: signal: segmentation fault
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output
        crash_cgo_test.go:633: skipping known flaky test without the -flaky flag; see golang.org/issue/49182
    --- FAIL: TestSegv/Segv (0.02s)
        crash_test.go:58: /tmp/buildlet/tmp/go-build1310876794/testprogcgo.exe Segv: signal: segmentation fault
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output
        crash_cgo_test.go:633: skipping known flaky test without the -flaky flag; see golang.org/issue/49182

2023-01-26 10:15 darwin-amd64-11_0 go@4df10fba runtime.TestSegv (log)

--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/SegvInCgo (0.07s)
        crash_test.go:58: /tmp/buildlet/tmp/go-build4292740019/testprogcgo.exe SegvInCgo: signal: segmentation fault
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output
        crash_cgo_test.go:633: skipping known flaky test without the -flaky flag; see golang.org/issue/49182
    --- FAIL: TestSegv/Segv (0.07s)
        crash_test.go:58: /tmp/buildlet/tmp/go-build4292740019/testprogcgo.exe Segv: signal: segmentation fault
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output
        crash_cgo_test.go:633: skipping known flaky test without the -flaky flag; see golang.org/issue/49182

— watchflakes

[bsiegert]

Looks like it is now happening on other platforms as well.

[bcmills]

The darwin-amd64 logs above have a similar symptom, but they were caused by a separate regression (#58068).

As far as I can tell the unexplained failures are still all specific to netbsd-arm64-bsiegert.