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:

http://gnats.netbsd.org/44402
http://gnats.netbsd.org/42319
http://gnats.netbsd.org/52065
http://gnats.netbsd.org/46224

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, <[email protected]> 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.
>
> paul
>
> On Jun 29, 2017, at 11:58 AM, Brad Fitzpatrick <[email protected]>
> 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/386
> netbsd/amd64
> netbsd/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:
>
>     https://tip.golang.org/doc/go1.9#known_issues
>
> If any NetBSD developers have time and/or interest, these bugs need
> attention:
>
>     https://github.com/golang/go/labels/OS-NetBSD
>
> Most concerning is our builders kernel panicing:
>
>     https://github.com/golang/go/issues/20836
>
> Until that's fixed, it's hard to make forward progress on other issues.
>
> Thanks!
> Brad
>
>
>