-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: fatal errors on dragonfly #13947
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
It seems that dragonfly was still happy until @ianlancetaylor's recent a7cad52 (runtime: preserve signal stack when calling Go on C thread). Ian, can you take a look? |
I'm not sure I would single out that particular change. After that change, the builder consistently timed out and looked flaky. The first time I see an error other than a timeout or a SIGTRAP signal was in http://build.golang.org/log/d8be87e27545cca84e8d0721c7b663ddb15ac7e4 for the change d75acd6 (which was clearly not the cause). So I think the error could have been introduced anywhere between those two changes, which is unfortunately a fair amount of ground. |
I've been trying to figure out this by deduction and by looking at the source code, but no luck. gomote doesn't support DragonFly. @mikioh is there a way I can ssh on to your Dragonfly system and run tests? |
Sorry I cannot provide you with easy access to my netbsd/dragonfly VMs. I'm happy to try your patch for investigation if you can send it me off-list. |
@mikioh I don't have a patch. I don't understand how these errors are possible. I need to have a system that I can use to investigate the problem interactively. |
62c280a - builds ok |
Thanks. I think I've found out the root cause of this issue: https://go-review.googlesource.com/#/c/18715. |
@mikioh All tests passed with your patch applied. Thanks.
|
CL https://golang.org/cl/18716 mentions this issue. |
CL https://golang.org/cl/18776 mentions this issue. |
CL https://golang.org/cl/18814 mentions this issue. |
CL https://golang.org/cl/29971 mentions this issue. |
… thread on dragonfly This change reverts CL 18814 which is a workaroud for older DragonFly BSD kernels, and fixes #13945 and #13947 in a more general way the same as other platforms except NetBSD. This is a followup to CL 29491. Updates #16329. Change-Id: I771670bc672c827f2b3dbc7fd7417c49897cb991 Reviewed-on: https://go-review.googlesource.com/29971 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
The recent logs display the following:
http://build.golang.org/log/ae9f24a66a50d66cf8ca2de2a0864d26e3a16daa
[signal 0xb code=0x1 addr=0xffffffffc8200011 pc=0xc820547baf]
http://build.golang.org/log/b207aed2f1628f1ad8828de714b33e2ebdfa25a9
fatal error: unexpected signal during runtime execution
panic during panic
[signal 0xb code=0x1 addr=0x0 pc=0xc8203fe510]
http://build.golang.org/log/fe324eb68c4836072136d30f41cb5d791ae27b6e
The text was updated successfully, but these errors were encountered: