-
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: failures with fatal error: traceback did not unwind completely
on openbsd/arm64
#62182
Comments
Found new dashboard test flakes for:
2023-08-07 19:31 linux-arm64-longtest go@d367ec6a runtime.TestVDSO (log)
2023-08-07 19:31 linux-arm64-longtest go@aca65771 runtime.TestCgoCCodeSIGPROF (log)
2023-08-15 03:40 plan9-arm go@60506f4d (log)
2023-08-20 05:56 openbsd-arm64-jsing go@a2ec545e os/signal.test [build] (log)
2023-08-20 05:56 openbsd-arm64-jsing go@a2ec545e strings (log)
|
Hrm. The failure on If so, that may indicate that the |
Yes, the two linux-arm64-longtest failures were fixed by https://go.dev/cl/516856. |
fatal error: traceback did not unwind completely
fatal error: traceback did not unwind completely
on openbsd/arm64
Found new dashboard test flakes for:
2023-08-21 18:00 openbsd-arm64-jsing go@c7383441 os/signal.test [build] (log)
2023-08-21 18:00 openbsd-arm64-jsing go@c7383441 strings (log)
|
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I get this error with go1.21.1 as well, is it fixed already somewhere? |
It's fixed here #62326 |
@Giulio2002 , are you getting this error on OpenBSD or a different platform? The fix for #62326 will appear in Go 1.21.2, but it appears there's still some separate issue on OpenBSD, which is what the current issue is still tracking. |
Found new dashboard test flakes for:
2023-11-22 15:50 openbsd-arm64-jsing go@37971b31 os/signal.test [build] (log)
2023-11-22 15:50 openbsd-arm64-jsing go@37971b31 strings (log)
|
Found new dashboard test flakes for:
2023-11-29 19:13 openbsd-arm64-jsing go@636c6e35 os/signal.test [build] (log)
2023-11-29 19:13 openbsd-arm64-jsing go@636c6e35 strings (log)
|
Found new dashboard test flakes for:
2023-11-29 15:49 openbsd-arm64-jsing go@1908d435 os/signal.test [build] (log)
2023-11-29 15:49 openbsd-arm64-jsing go@1908d435 strings (log)
|
Found new dashboard test flakes for:
2023-12-18 19:42 openbsd-arm64-jsing go@08bec0db os/signal.test [build] (log)
2023-12-18 19:42 openbsd-arm64-jsing go@08bec0db strings (log)
|
Found new dashboard test flakes for:
2023-12-06 17:29 openbsd-arm64-jsing go@c80bd631 os/signal.test [build] (log)
2023-12-06 17:29 openbsd-arm64-jsing go@c80bd631 strings (log)
|
Found new dashboard test flakes for:
2024-02-19 15:44 openbsd-arm64-jsing go@cf52e709 os/signal.test [build] (log)
2024-02-19 15:44 openbsd-arm64-jsing go@cf52e709 strings (log)
|
Found new dashboard test flakes for:
2024-02-28 05:32 openbsd-arm64-jsing go@b8c76eff os/signal.test [build] (log)
2024-02-28 05:32 openbsd-arm64-jsing go@b8c76eff strings (log)
|
Found new dashboard test flakes for:
2024-03-29 21:55 openbsd-arm64-jsing go@7979c8f5 strings (log)
|
Found new dashboard test flakes for:
2024-03-29 21:53 openbsd-arm64-jsing go@29fcd156 strings (log)
|
Found new dashboard test flakes for:
2024-04-02 21:51 openbsd-arm64-jsing go@d08a9572 strings (log)
|
Found new dashboard test flakes for:
2024-04-19 17:16 openbsd-arm64-jsing go@4324d5a8 strings (log)
|
(Pulled out from #55167 (comment), #62105 (comment), and #62101 (comment).)
The text was updated successfully, but these errors were encountered: