daily CVS update output

2016-07-19 Thread NetBSD source update
Updating src tree: P src/libexec/ftpd/ftpd.c P src/libexec/httpd/content-bozo.c P src/libexec/mail.local/mail.local.c P src/share/man/man9/driver.9 P src/share/misc/acronyms P src/sys/arch/playstation2/dev/sbus.c P src/sys/arch/playstation2/dev/spd.c P

Re: strange failure to run

2016-07-19 Thread Paul Goyette
On Tue, 19 Jul 2016, bch wrote: Running cc(1) or cvs(1) fails with the following. My kernel/userland is very up-to-date, but my machine did just shutdown w/ a dead battery, too ( it usually catches the issue quickly enough and issues a shutdown, though I'm not sure that happened in time this

strange failure to run

2016-07-19 Thread bch
Running cc(1) or cvs(1) fails with the following. My kernel/userland is very up-to-date, but my machine did just shutdown w/ a dead battery, too ( it usually catches the issue quickly enough and issues a shutdown, though I'm not sure that happened in time this instance). Anybody else

Re: Crash in xhci driver

2016-07-19 Thread Paul Goyette
Well, I've been running a 7.99.33 kernel (sources dated 2016-07-04 at 08:34:20 UTC) for two weeks now without any further crashes. Maybe the problem is fixed? Or maybe is has just gone into hiding, lurking, waiting to reappear? :) On Thu, 30 Jun 2016, Takahiro Hayashi wrote: On

Re: current build failure automated messages

2016-07-19 Thread Paul Goyette
On Tue, 19 Jul 2016, Greg Troxel wrote: Andreas Gustafsson writes: I can appreciate that - different people have different preferences and workflows. I'd like to hear the opinions of other developers - if there is a consensus that "build has been fixed" email notifications

Re: current build failure automated messages

2016-07-19 Thread Greg Troxel
Andreas Gustafsson writes: > I can appreciate that - different people have different preferences > and workflows. I'd like to hear the opinions of other developers - > if there is a consensus that "build has been fixed" email notifications > would be useful, I can certainly add

Re: current build failure automated messages

2016-07-19 Thread Robert Elz
Date:Tue, 19 Jul 2016 12:40:34 +0300 From:Andreas Gustafsson Message-ID: <22413.62866.53313.424...@guava.gson.org> | You don't have to screen scrape the HTML reports - you can get the | underlying data by anonymous rsync, as described in | |

Re: current build failure automated messages

2016-07-19 Thread Andreas Gustafsson
Robert Elz wrote: > | If the page says "Build: OK" at the end, the issue has > | been fixed. At least for me, this is less work overall than it would > | be to handle twice the number of emails. > > I actually cannot imagine that being possible for me, one more e-mail to > delete every few

Re: current build failure automated messages

2016-07-19 Thread Robert Elz
Date:Sat, 16 Jul 2016 12:15:41 +0300 From:Andreas Gustafsson Message-ID: <22409.64317.493648.115...@guava.gson.org> | It would not be hard to implement, but I'm not sure it would be useful | enough to justify doubling the number of messages to the