Re: Finding errors in build logs

[christos%astron.com@localhost (Christos Zoulas)]

In article <24432.50312.48649.508059%guava.gson.org@localhost>,
Andreas Gustafsson  <gson%gson.org@localhost> 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 'make.*stopped' is the best clue to look for since it will
>> always be present.
>
>It is not present in this recent log extract:
>
> 
>http://releng.netbsd.org/b5reports/i386/2020/2020.09.27.13.59.24/build.log.tail
>
>I also checked the full log, and it's not there, either.

Yes, I have a log that does not contain it either.

http://www.zoulas.com/~christos/NetBSD/make.amd64-x86_64.release.out

It finishes with:

--- obj-crypto/external ---

ERROR: Failed to make release
*** BUILD ABORTED ***

I suggest that we revert the change that minimize the error messages in
the parallel make until this is undestood. This is not the first time this
happened to me.

christos