-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
Comments
Found new dashboard test flakes for:
2022-10-20 22:16 linux-s390x-ibm go@4725c71b runtime.TestNeedmDeadlock (log)
|
In triage I think we want to see more failures. For context, 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. |
Seems no new failure for quite a while. Move to backlog. |
Found new dashboard test flakes for:
2023-01-09 20:25 openbsd-amd64-71 go@0bbd67e5 runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-01-26 07:17 darwin-amd64-10_15 go@cea70301 runtime.TestNeedmDeadlock (log)
2023-01-26 07:17 darwin-amd64-11_0 go@cea70301 runtime.TestNeedmDeadlock (log)
2023-01-26 10:15 darwin-amd64-10_15 go@4df10fba runtime.TestNeedmDeadlock (log)
2023-01-26 10:15 darwin-amd64-11_0 go@4df10fba runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-02-28 01:46 linux-s390x-ibm go@aaace6dd runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-03-24 16:00 netbsd-arm-bsiegert go@ef0dedce runtime.TestNeedmDeadlock (log)
|
The failure on 2023-03-24 is due to CL 392854 and is fixed with CL 479255. |
Found new dashboard test flakes for:
2023-03-24 18:14 netbsd-arm-bsiegert go@2716dfd9 runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-03-24 17:48 netbsd-arm-bsiegert go@59d7c693 runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-03-31 19:15 linux-arm-aws go@99276aeb runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-03-31 19:15 netbsd-arm-bsiegert go@99276aeb runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-05-31 19:15 linux-s390x-ibm go@3cea9e68 runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-08-22 19:18 linux-s390x-ibm-race go@3e73802c runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-09-12 17:08 netbsd-arm-bsiegert go@4f9fe6d5 runtime.TestNeedmDeadlock (log)
2023-09-12 18:14 netbsd-arm-bsiegert go@5cc1e99f runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2023-09-12 17:47 netbsd-arm-bsiegert go@9f5a2cf6 runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2024-01-10 17:35 netbsd-arm-bsiegert go@e9b3ff15 runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2024-02-17 06:03 netbsd-arm-bsiegert go@86a32d6d runtime.TestNeedmDeadlock (log)
|
Found new dashboard test flakes for:
2024-11-11 20:08 gotip-netbsd-arm go@6051da46 runtime.TestNeedmDeadlock (log)
|
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: