Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
gopherbot opened this issue Jan 25, 2023 · 14 comments
Open

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

gopherbot opened this issue Jan 25, 2023 · 14 comments
Assignees
@prattmic
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Backlog

Comments

@gopherbot
Copy link
Contributor

gopherbot commented Jan 25, 2023 •
edited by bcmills
Loading 

#!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 gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jan 25, 2023
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jan 25, 2023
@gopherbot
Copy link
Contributor Author

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
Copy link
Contributor

bcmills commented Jan 25, 2023

Both on netbsd-arm64-bsiegert so far. 🤔

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

@bcmills bcmills changed the title runtime: TestSegv failures runtime: TestSegv failures with did not see "SIGSEGV" in output Jan 25, 2023
@bcmills bcmills added this to the Backlog milestone Jan 25, 2023
@dr2chase dr2chase assigned dr2chase and prattmic and unassigned dr2chase Feb 1, 2023
@gopherbot
Copy link
Contributor Author

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
Copy link
Contributor

bsiegert commented Feb 3, 2023

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

@bcmills
Copy link
Contributor

bcmills commented Feb 3, 2023

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.

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`
2023-02-08 02:44 netbsd-arm-bsiegert go@abd55d84 runtime.TestSegv (log) 
--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/Segv (0.02s)
        crash_cgo_test.go:619: /var/gobuilder/buildlet/tmp/go-build395569536/testprogcgo.exe Segv (20.666187ms): ok
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`
2023-02-28 23:42 linux-amd64-goamd64v3 go@0384235a runtime.TestSegv (log) 
--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/SegvInCgo (0.00s)
        crash_cgo_test.go:619: /workdir/tmp/go-build730233276/testprogcgo.exe SegvInCgo (3.425654ms): ok
        crash_cgo_test.go:620: 
        crash_cgo_test.go:626: did not see "SIGSEGV" in output

— watchflakes

@bcmills
Copy link
Contributor

bcmills commented Mar 1, 2023

Well, that one isn't on netbsd. 😅

@golang/runtime, that last failure is on a first-class port (linux/amd64) — does that affect prioritization on this issue?

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`
2023-03-31 03:39 netbsd-arm-bsiegert go@e29dd78f runtime.TestSegv (log) 
--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/Segv (0.22s)
        crash_cgo_test.go:628: /var/gobuilder/buildlet/tmp/go-build503233079/testprogcgo.exe Segv (219.034999ms): ok
        crash_cgo_test.go:629: 
        crash_cgo_test.go:635: did not see "SIGSEGV" in output

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`
2023-04-04 17:04 netbsd-arm64-bsiegert go@ecc5ba46 runtime.TestSegv (log) 
--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/Segv (0.03s)
        crash_cgo_test.go:628: /var/gobuilder/buildlet/tmp/go-build634491355/testprogcgo.exe Segv (24.638017ms): ok
        crash_cgo_test.go:629: 
        crash_cgo_test.go:635: did not see "SIGSEGV" in output

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`
2023-05-24 03:14 netbsd-arm-bsiegert go@626d478d runtime.TestSegv (log) 
--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/Segv (0.08s)
        crash_cgo_test.go:651: /var/gobuilder/buildlet/tmp/go-build2001216304/testprogcgo.exe Segv (77.00665ms): ok
        crash_cgo_test.go:652: 
        crash_cgo_test.go:658: did not see "SIGSEGV" in output

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`
2023-08-25 21:04 netbsd-arm-bsiegert go@789b3f84 runtime.TestSegv (log) 
--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/SegvInCgo (0.03s)
        crash_cgo_test.go:655: /var/gobuilder/buildlet/tmp/go-build1238234895/testprogcgo.exe SegvInCgo (28.856047ms): ok
        crash_cgo_test.go:656: 
        crash_cgo_test.go:662: did not see "SIGSEGV" in output

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`
2023-09-06 14:20 netbsd-amd64-9_3 go@b0e1d3ea runtime.TestSegv (log) 
--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/SegvInCgo (0.00s)
        crash_cgo_test.go:655: /tmp/workdir/tmp/go-build2292806128/testprogcgo.exe SegvInCgo (4.798403ms): ok
        crash_cgo_test.go:656: 
        crash_cgo_test.go:662: did not see "SIGSEGV" in output

— watchflakes

@bcmills bcmills mentioned this issue Jan 11, 2024
Closed
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && `did not see "SIGSEGV" in output`
2024-01-22 16:54 netbsd-386-9_3 go@29cea658 runtime.TestSegv (log) 
--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/SegvInCgo (0.00s)
        crash_cgo_test.go:656: /tmp/workdir/tmp/go-build787461731/testprogcgo.exe SegvInCgo (3.695741ms): ok
        crash_cgo_test.go:657: 
        crash_cgo_test.go:663: did not see "SIGSEGV" in output

— watchflakes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prattmic prattmic

Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Go Compiler / Runtime
Status: Todo
Test Flakes
Status: No status
Milestone
Backlog
Development

No branches or pull requests
5 participants
@bsiegert @prattmic @dr2chase @bcmills @gopherbot