Skip to content

runtime: "scan missed a g" #13140

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

Closed
mdempsky opened this issue Nov 4, 2015 · 3 comments
Closed

runtime: "scan missed a g" #13140

mdempsky opened this issue Nov 4, 2015 · 3 comments
Milestone

Comments

@mdempsky
Copy link
Contributor

mdempsky commented Nov 4, 2015

I've seen this failure on the OpenBSD trybot and builders a bunch. E.g.:

http://build.golang.org/log/9a7a7718cfe2eea41f9d63f236cbca4eb59bc0b8

I believe I've also seen it on a nacl trybot, and I saw it on my work desktop (linux/amd64) earlier today too.

@mdempsky
Copy link
Contributor Author

mdempsky commented Nov 4, 2015

@aclements
Copy link
Member

I'm hoping this will go away once I merge my series at https://go-review.googlesource.com/#/c/16391/. My goal is to do that this week. I'll ping this bug once that's happened and if we still see failures with that in the tree, I'll investigate.

@aclements aclements added this to the Go1.6 milestone Nov 4, 2015
@aclements
Copy link
Member

I pushed my decentralized GC series last Thursday, November 5th and, in fact, the last time we saw this was in the middle of me pushing that series. Given the failure rate, it's highly likely that this has been fixed, but please reopen if you see it again.

First observed 82d14d7 30 Oct 22:46 2015 (93 commits ago)
Last observed d986bf2 05 Nov 21:23 2015 (41 commits ago)
0.11% chance failure is still happening
15% failure probability (9 of 53 commits)

@golang golang locked and limited conversation to collaborators Nov 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants