tech-misc archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Go on NetBSD needs love

I only identified it as a kernel crash the other day. We had assumed it was our bug prior to that.

But many similar looking bugs exist already:

I don't want to file duplicates.

I would like somebody from NetBSD who knows your process and bug tracker to take the lead on filing & nudging bugs as needed.

On Thu, Jun 29, 2017 at 9:36 AM, <> wrote:
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.


On Jun 29, 2017, at 11:58 AM, Brad Fitzpatrick <> wrote:


I work on Go ( and run our build farm (

Go's main toolchain supports 38 different OS/arch pairs (`go tool dist list`), not including gccgo.

Three of those 38 are:


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.


Home | Main Index | Thread Index | Old Index