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: TestNeedmDeadlock failures #56420

Open
gopherbot opened this issue Oct 25, 2022 · 3 comments
Open

runtime: TestNeedmDeadlock failures #56420

gopherbot opened this issue Oct 25, 2022 · 3 comments
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

Comments

@gopherbot
Copy link

gopherbot commented Oct 25, 2022

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

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestNeedmDeadlock (5.11s)
    testenv.go:459: [/data/golang/workdir/tmp/go-build4218498514/testprogcgo.exe NeedmDeadlock] exit status: exit status 1
    crash_cgo_test.go:714: want OK
        , got Hung for 5 seconds

watchflakes

@gopherbot gopherbot added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. compiler/runtime Issues related to the Go compiler and/or runtime. labels Oct 25, 2022
@gopherbot
Copy link
Author

gopherbot commented Oct 25, 2022

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestNeedmDeadlock"
2022-10-20 22:16 linux-s390x-ibm go@4725c71b runtime.TestNeedmDeadlock (log)
--- FAIL: TestNeedmDeadlock (5.11s)
    testenv.go:459: [/data/golang/workdir/tmp/go-build4218498514/testprogcgo.exe NeedmDeadlock] exit status: exit status 1
    crash_cgo_test.go:714: want OK
        , got Hung for 5 seconds

watchflakes

@mknyszek
Copy link
Contributor

mknyszek commented Oct 26, 2022

In triage I think we want to see more failures. For context, needm is used on the C -> Go call path to get an m for the C thread. Seems like it might be similar to #43625?

If it happens again on s390x I'll loop in the s390x folks.

@mknyszek mknyszek added this to the Go1.20 milestone Oct 26, 2022
@mknyszek
Copy link
Contributor

mknyszek commented Nov 23, 2022

This continues to be the only failure in recent memory. At the end of the cycle we should put this into the backlog if we don't see any more issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Status: Todo
Status: No status
Development

No branches or pull requests

2 participants