-
Notifications
You must be signed in to change notification settings - Fork 17.6k
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: SIGSEGV during gcenable on darwin-arm64-corellium #34908
Comments
It's not obvious to me what test or what build of a test is causing the failure (just must be some test after sync/atomic). But I tried reproducing the failure by running the following command (which executes a sequence of tests around the point where things failed) repeatedly via gomote to darwin-arm64-corellium:
I couldn't reproduce -- never got any failures in 50 runs. So, I think we'll probably just have to wait & see if there are any other failures from builders. |
Most likely fixed by the numerous runtime fixes. |
From the
darwin-arm64-corellium
builder (https://build.golang.org/log/591a1a4a3afb0d8d72864ae84e551bb82c40f0c9):May be related to #32026 and/or #32324: it looks like we may have a general memory-corruption issue on either the builder or the platform.
CC @aclements @randall77 @cherrymui @steeve
The text was updated successfully, but these errors were encountered: