Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Automated report: NetBSD-current/i386 build failure

On Sun, Jun 23, 2013 at 02:38:00PM +0100, David Laight wrote:
> All of the makes should be using the same job token queue, so should stop
> as soon as the 'failed' token is inserted.
> So you should only see one non-make fail for each possible parralel task.
> (Of course, it could be buggy!)

And a "local make" one for each directory recursion, I presume?

The builds run with -j11 currently and (just for example)

 fgrep "A failure has been detected in another" | wc -l

says 10, but then each of the make instances unwinds recursion and logs
a failure for each level.

In the example I used here the first "stopped in" message is printed in line
54428 of the log, and the last log line is number 54695. So a lot of noise,
but basically it looks all correct.

Should we suppress the errror messages on recursion pops? They do not provide
a lot of value (besides naming the make target causing the recursion).


Home | Main Index | Thread Index | Old Index