daily CVS update output

2020-09-27 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/man/mi P src/distrib/sets/lists/tests/mi P src/doc/CHANGES P src/external/lgpl3/gmp/lib/libgmp/arch/arm/config.h P src/external/lgpl3/gmp/lib/libgmp/arch/arm/config.m4 P src/external/lgpl3/gmp/lib/libgmp/arch/arm/gmp-mparam.h P

Automated report: NetBSD-current/i386 test failure

2020-09-27 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/if_tap/t_tap:tap_bridged The above test failed in each of the last 4 test runs, and passed in at least 26 consecutive runs before that. The following commits were made

Re: Finding errors in build logs

2020-09-27 Thread Simon J. Gerraty
Andreas Gustafsson wrote: > On June 21, Simon J. Gerraty wrote: > > > It would be helpful for both human and robotic users if error messages > > > consistently included the word "error", or if there was some other easy > > > way of identifying them in the build log. > > > > The regex

Automated report: NetBSD-current/i386 build success

2020-09-27 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: 2020.09.27.19.06.47 rillig src/usr.bin/make/job.c,v 1.244 2020.09.27.19.08.11 roy src/sys/conf/files,v 1.1276 2020.09.27.19.13.46 rillig

Re: Finding errors in build logs

2020-09-27 Thread Christos Zoulas
In article <24432.50312.48649.508...@guava.gson.org>, Andreas Gustafsson wrote: >On June 21, Simon J. Gerraty wrote: >> > It would be helpful for both human and robotic users if error messages >> > consistently included the word "error", or if there was some other easy >> > way of identifying

Finding errors in build logs

2020-09-27 Thread Andreas Gustafsson
On June 21, Simon J. Gerraty wrote: > > It would be helpful for both human and robotic users if error messages > > consistently included the word "error", or if there was some other easy > > way of identifying them in the build log. > > The regex 'make.*stopped' is the best clue to look for since

Automated report: NetBSD-current/i386 build failure

2020-09-27 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 2020.09.27.13.59.24. The following commits were made between the last successful build and the failed build: