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?
to your account
post <- pkg == "runtime" && test == "TestNeedmDeadlock"
Issue created automatically to collect these failures.
--- 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
The text was updated successfully, but these errors were encountered:
Found new dashboard test flakes for:
Sorry, something went wrong.
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.
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.
No branches or pull requests