daily CVS update output

2019-09-29 Thread NetBSD source update
Updating src tree: P src/bin/ksh/Makefile P src/crypto/external/bsd/netpgp/bin/netpgpverify/Makefile P src/crypto/external/bsd/netpgp/lib/verify/Makefile P src/crypto/external/bsd/openssh/bin/sftp/Makefile P src/distrib/utils/zcat/Makefile P src/external/bsd/atf/lib/tools/Makefile P

Re: 9.0-BETA panic

2019-09-29 Thread Mike Pumford
On 29/09/2019 21:54, Mike Pumford wrote: Was doing a pkgsrc build under jenkins and got the following panic: [ 14305.111922] panic: kernel diagnostic assertion "semcnt >= 0" failed: file "/ work/netbsd/9-stable/src/sys/kern/kern_uidinfo.c", line 241 [ 14305.111922] cpu5: Begin traceback...

Automated report: NetBSD-current/i386 build success

2019-09-29 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2019.09.29.18.51.08 rmind src/usr.sbin/npf/npfctl/npf_build.c,v 1.52 Log files can be found at:

9.0-BETA panic

2019-09-29 Thread Mike Pumford
Was doing a pkgsrc build under jenkins and got the following panic: [ 14305.111922] panic: kernel diagnostic assertion "semcnt >= 0" failed: file "/ work/netbsd/9-stable/src/sys/kern/kern_uidinfo.c", line 241 [ 14305.111922] cpu5: Begin traceback... [ 14305.111922] vpanic() at

Automated report: NetBSD-current/i386 build failure

2019-09-29 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2019.09.29.17.00.29. An extract from the build.sh output follows:

Re: time(1) reporting corrupted system time

2019-09-29 Thread Andreas Gustafsson
Michael van Elst wrote: > First there was a change to precent that user/system time are decreasing > in kern-resource.c 1.180. But it shouldn't be related to negative numbers. > > Additionally a possible underflow of user/system time was fixed in > kern_resource.c 1.182. This prevents negative

Re: Build failed on fresh sources

2019-09-29 Thread Paul Goyette
On Sun, 29 Sep 2019, Christos Zoulas wrote: Sure, but the question is why are you getting errors in the first place. They should have been downgraded to warnings by -Wno-error-foo. Something in /etc/mk.conf perhaps? christos On Sep 29, 2019, at 3:18 AM, Greywolf wrote: On Sat, Sep 28,

Re: Build failed on fresh sources

2019-09-29 Thread Christos Zoulas
Sure, but the question is why are you getting errors in the first place. They should have been downgraded to warnings by -Wno-error-foo. christos > On Sep 29, 2019, at 3:18 AM, Greywolf wrote: > > On Sat, Sep 28, 2019 at 3:48 AM Christos Zoulas wrote: > >> We've chosen not to fix the

time(1) reporting corrupted system time

2019-09-29 Thread Andreas Gustafsson
Hi all, I'm trying to run a bisection to determine why builds hosted on recent versions of NetBSD seem to be taking significantly more system time than they used to, building the same thing. My efforts are hampered by time(1) reporting corrupted system times on certain past versions of -current:

re: Build failed on fresh sources

2019-09-29 Thread matthew green
> ../../../../external/bsd/drm2/dist/drm/i915/intel_ddi.c -o intel_ddi.o makeoptions i915drmkms "CWARNFLAGS.intel_ddi.c"+="${${ACTIVE_CC} == gcc && ${HAVE_GCC:U0} == 7:? -Wno-error=implicit-fallthrough :}" this is missing from your build some how. do you have HAVE_GCC set to something

Re: Build failed on fresh sources

2019-09-29 Thread Greywolf
On Sat, Sep 28, 2019 at 3:48 AM Christos Zoulas wrote: > We've chosen not to fix the fallthrough warnings in 3rd party code, but > we instead have changed the default setting to not produce errors. Have > you made any changes to the compilation environment that caused those to > become errors