-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile: random failure after upgrade to v1.16 #45537
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
This looks like memory corruption. This can only happen if the capacity of that slice is trashed somehow. |
@randall77 |
@fanqiehc Not sure. It's possible that some memory corruption introduced by the host is to blame. It could also be a bug in the Go runtime. I don't think there's any easy way to distinguish the two. Certainly if you have some memory stress tests you can run, that might point to an obvious cause. |
If you can catch a failure while setting the environment variable |
@gopherbot add WaitingForInfo |
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.) |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
v1.16.3 / v1.16.2 / v1.16.0
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Compiling a server app inside a Kubernetes Pod. The pod is created by Jenkins.
What did you expect to see?
Build without errors.
What did you see instead?
About 1/10 percent random failures with different stacktrace.
The text was updated successfully, but these errors were encountered: