runtime: "unexpected signal during runtime execution" during bgscavenge on plan9-386-0intro #35456
Comments
This is very odd. It's failing very, very early in the runtime (right when the background scavenger is spinning up) trying to allocate a timer. And the problem seems to be that |
The type parameter passed to But that said I have no idea why the binary would get a trap signal. I don't know enough about Plan 9 to know what might cause that. If this happened only once I'm inclined to ignore it. CC @0intro |
Not sure if this is related, but
|
Change https://golang.org/cl/233797 mentions this issue: |
The plan9-arm builder is currently passing fairly reliably on the dashboard, whereas the plan9-386-0intro builder is frequently failing with an "unexpected fault address". Until the plan9-386-0intro build is fixed, the plan9-arm builder seems more useful as a SlowBot to check architecture-agnostic changes that affect plan9. Updates golang/go#35456 Updates golang/go#22227 Change-Id: Ib5ecddafec91ca9274f9f0e15cb98621b41dda85 Reviewed-on: https://go-review.googlesource.com/c/build/+/233797 Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
From
plan9-386-0intro
(https://build.golang.org/log/a94f5d80b1a5d38ecdf8b02bed7bfb305f569118), acmd/vet
test failure that appears to have nothing to do withcmd/vet
:CC @aclements @mknyszek @0intro @fhs
The text was updated successfully, but these errors were encountered: