On Mon, Jul 19, 2021 at 08:13:19AM +0300, Andreas Gustafsson wrote: > David Holland wrote: > > On Mon, Jul 19, 2021 at 10:32:20AM +0900, Rin Okuyama wrote: > > > Logs below are usually more helpful. > > > > Right... I wonder what happened to bracket's error-matching script; it > > usually does better than that. > > There are multiple causes, but a major one is that since babylon5 was > upgraded to a new server with more cores, the builds have more > parallelism, which causes make(1) to print more output from the other > parallel jobs after the actual error message, and bracket isn't > looking far enough back in the log. I have a fix in testing on my own > testbed but still need to deploy it on babylon5.
I think I've expressed this idea before, but can't we enhance our make(1) to record all printouts for each make target? It could discard the logs of the targets that succeeded and print the one(s) that failed out on reporting the complation error? Then at least all the output of the failed targets are collected and readable. If this was already shot down once before, please ignore it. I'm not that familiar with the make(1) internals. Reinoud
signature.asc
Description: PGP signature
