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.

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

runtime: TestCgoTraceParserWithOneProc failures #59235

Closed
gopherbot opened this issue Mar 24, 2023 · 4 comments
Closed

runtime: TestCgoTraceParserWithOneProc failures #59235

gopherbot opened this issue Mar 24, 2023 · 4 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

Comments

@gopherbot
Copy link

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

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestCgoTraceParserWithOneProc (0.10s)
    crash_cgo_test.go:753: /var/gobuilder/buildlet/tmp/go-build3741504798/testprogcgo.exe CgoTraceParser: exit status 2
    crash_cgo_test.go:759: GOMAXPROCS=1, want OK
        , got panic: runtime error: invalid memory address or nil pointer dereference
        [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]

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 Mar 24, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestCgoTraceParserWithOneProc"
2023-03-24 16:00 netbsd-arm-bsiegert go@ef0dedce runtime.TestCgoTraceParserWithOneProc (log)
--- FAIL: TestCgoTraceParserWithOneProc (0.10s)
    crash_cgo_test.go:753: /var/gobuilder/buildlet/tmp/go-build3741504798/testprogcgo.exe CgoTraceParser: exit status 2
    crash_cgo_test.go:759: GOMAXPROCS=1, want OK
        , got panic: runtime error: invalid memory address or nil pointer dereference
        [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]

watchflakes

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Mar 24, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestCgoTraceParserWithOneProc"
2023-03-24 18:14 netbsd-arm-bsiegert go@2716dfd9 runtime.TestCgoTraceParserWithOneProc (log)
--- FAIL: TestCgoTraceParserWithOneProc (0.11s)
    crash_cgo_test.go:753: /var/gobuilder/buildlet/tmp/go-build1118342320/testprogcgo.exe CgoTraceParser: exit status 2
    crash_cgo_test.go:759: GOMAXPROCS=1, want OK
        , got panic: runtime error: invalid memory address or nil pointer dereference
        [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]

watchflakes

@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestCgoTraceParserWithOneProc"
2023-03-24 17:48 netbsd-arm-bsiegert go@59d7c693 runtime.TestCgoTraceParserWithOneProc (log)
--- FAIL: TestCgoTraceParserWithOneProc (0.12s)
    crash_cgo_test.go:753: /var/gobuilder/buildlet/tmp/go-build632147128/testprogcgo.exe CgoTraceParser: exit status 2
    crash_cgo_test.go:759: GOMAXPROCS=1, want OK
        , got panic: runtime error: invalid memory address or nil pointer dereference
        [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]

watchflakes

@mknyszek
Copy link
Contributor

This seems like the same issue as #59233. I updated the watchflakes expression there. Closing this as duplicate.

@mknyszek mknyszek closed this as not planned Won't fix, can't repro, duplicate, stale Mar 29, 2023
@golang golang locked and limited conversation to collaborators Mar 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: Done
Development

No branches or pull requests

2 participants