Clearly crashes, and possibly hangs, are NetBSD bugs, not Go bugs, so they should be filed through the NetBSD bug tracker. If you have them only in the Go tracker, that might account for them not being worked on.
paul
On Jun 29, 2017, at 11:58 AM, Brad Fitzpatrick <bradfitz%golang.org@localhost> wrote:
Hi,
I work on Go (https://golang.org) and run our build farm (https://build.golang.org/).
Go's main toolchain supports 38 different OS/arch pairs (`go tool dist list`), not including gccgo.
Three of those 38 are:
netbsd/386netbsd/amd64netbsd/arm
And those three are currently in need of love.
We've had problems with both hangs during builds as well as kernel crashes, so we've had to stop running our NetBSD builders during the last dev cycle, as sadly added to our upcoming Go 1.9 release notes:
If any NetBSD developers have time and/or interest, these bugs need attention:
Most concerning is our builders kernel panicing:
Until that's fixed, it's hard to make forward progress on other issues.
Thanks!
Brad