-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: unexpected return pc on windows-386-2016 #58569
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
Comments
Found new dashboard test flakes for:
2023-02-09 21:13 windows-386-2016 go@da47cd61 os.TestFTruncate (log)
|
Panic happens on line 61 Lines 59 to 64 in da47cd6
I don't see how the panic is possible unless the problem is in runtime or GC. Alex |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Got one of these on a |
In triage, both of the failures look like a failure during a panic to process open-coded defers. Possibly the stack got corrupted, it tried to panic, but then the panic broke because, well, the stack is corrupted. |
@prattmic notes the test is intentionally panicking, and then it fails. Unfortunately there's not a lot to go off of here. The two failures we've seen happened in totally different places. We could try to reproduce I suppose? |
We haven't seen this fail in quite a long time, and @mdempsky simplified defer processing this cycle. I wonder if that fixed it? Optimistically closing. |
2023-02-09T21:13:56-da47cd6/windows-386-2016
Notes:
windows-386-2016
builder.prefixAndSuffix
is unexpected; none of the os tests expect panics.cc @mknyszek @aclements @golang/runtime @golang/windows
The text was updated successfully, but these errors were encountered: