Re: Go on NetBSD needs love

2017-07-03 Thread Christos Zoulas 
In article <20170702202656.gc29...@netbsd.org>,
David Holland   wrote:
>On Fri, Jun 30, 2017 at 07:36:41PM +0200, Joerg Sonnenberger wrote:
> > From the follow-up, it is far from clear that it is fixed completely.
>
>Yes, I was wondering about that but people have been saying it works
>on -8...
>
> > I'm running current with https://www.netbsd.org/~joerg/kern_event.c.diff
> > with the go 1.8.3 test suite in an infinite loop. Modulo the Perl 5.26.0
> > issue in vet_test and some occassional time outs from individual tests,
> > I don't see any issues.
>
>any reason not to commit?

Go needs two commits to work which are already in current:

For 8: https://releng.netbsd.org/cgi-bin/req-8.cgi?show=91
For 7: https://releng.netbsd.org/cgi-bin/req-7.cgi?show=1442

christos

Re: Go on NetBSD needs love

2017-07-02 Thread David Holland 
On Fri, Jun 30, 2017 at 07:36:41PM +0200, Joerg Sonnenberger wrote:
 > From the follow-up, it is far from clear that it is fixed completely.

Yes, I was wondering about that but people have been saying it works
on -8...

 > I'm running current with https://www.netbsd.org/~joerg/kern_event.c.diff
 > with the go 1.8.3 test suite in an infinite loop. Modulo the Perl 5.26.0
 > issue in vet_test and some occassional time outs from individual tests,
 > I don't see any issues.

any reason not to commit?

-- 
David A. Holland
dholl...@netbsd.org

Re: Go on NetBSD needs love

2017-07-02 Thread David Holland 
On Fri, Jun 30, 2017 at 09:49:21AM -0700, Brad Fitzpatrick wrote:
 > > which leads to
 > >http://gnats.netbsd.org/50730
 > > which is fixed but the fix is apparently not in 7.1.
 > 
 > Where do you see that it's fixed?

That part requires some inside knowledge :-)  Christos committed a fix,
and the bug report state wasn't updated because Christos never does
that himself and occasionally nobody else gets to it.

Also since your original post there's been some discussion in chat.

 > I'm fumbling my way around these tools. Is there a link to the fix
 > somewhere?

Our tools suck I'm afraid :(

The commit referenced in the PR can be gotten here:

http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/kern/kern_event.c.diff?r1=1.84=1.85=h
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/sys/event.h.diff?r1=1.25=1.26=h

and also here:

https://mail-index.netbsd.org/source-changes/2016/01/31/msg072323.html

-- 
David A. Holland
dholl...@netbsd.org

Re: Go on NetBSD needs love

2017-06-30 Thread Joerg Sonnenberger 
On Fri, Jun 30, 2017 at 04:31:17PM +, David Holland wrote:
> On Thu, Jun 29, 2017 at 09:41:27AM -0700, Brad Fitzpatrick wrote:
>  > 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
> 
> Those are all completely different bugs; the only thing they have in
> common is the kernel-level equivalent of SIGSEGV.
> 
>  > > https://github.com/golang/go/issues/20836
> 
> leads to
>https://github.com/golang/go/issues/14127
> which leads to
>http://gnats.netbsd.org/50730
> which is fixed but the fix is apparently not in 7.1.

>From the follow-up, it is far from clear that it is fixed completely.

I'm running current with https://www.netbsd.org/~joerg/kern_event.c.diff
with the go 1.8.3 test suite in an infinite loop. Modulo the Perl 5.26.0
issue in vet_test and some occassional time outs from individual tests,
I don't see any issues.

Joerg

Re: Go on NetBSD needs love

2017-06-30 Thread Brad Fitzpatrick 
On Fri, Jun 30, 2017 at 9:31 AM, David Holland 
wrote:

> On Thu, Jun 29, 2017 at 09:41:27AM -0700, Brad Fitzpatrick wrote:
>  > 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
>
> Those are all completely different bugs; the only thing they have in
> common is the kernel-level equivalent of SIGSEGV.
>
>  > > https://github.com/golang/go/issues/20836
>
> leads to
>https://github.com/golang/go/issues/14127
> which leads to
>http://gnats.netbsd.org/50730
> which is fixed but the fix is apparently not in 7.1.
>

Where do you see that it's fixed?

I'm fumbling my way around these tools. Is there a link to the fix
somewhere?


>
> Also, tech-kern is the list for kernel issues. Adjusting accordingly.

Re: Go on NetBSD needs love

2017-06-30 Thread David Holland 
On Thu, Jun 29, 2017 at 09:41:27AM -0700, Brad Fitzpatrick wrote:
 > 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

Those are all completely different bugs; the only thing they have in
common is the kernel-level equivalent of SIGSEGV.

 > > https://github.com/golang/go/issues/20836

leads to
   https://github.com/golang/go/issues/14127
which leads to
   http://gnats.netbsd.org/50730
which is fixed but the fix is apparently not in 7.1.

Also, tech-kern is the list for kernel issues. Adjusting accordingly.

-- 
David A. Holland
dholl...@netbsd.org