From Jonathan Gibbons on build-dev:

Re: JDK builds,

The new parallel make is wonderfully fast (thank you) but less great when it comes to figuring out why a build failed, especially when you don't have full access to the build machine, as is the case with "build servers", where you get the build log, and the product bits if the build is successful.

I finally figured out a tip and wonder if it would be worth adding this to the end of the build.

If the build fails, grep through the log looking for lines containing the text "recipe for .* failed".

Would it be possible to have the build report any such lines in the summary at the end of the log?

-- Jon


I have been experimenting a bit with this and found a basic solution that will likely work quite well. I simply put the summary creation in the logger.sh script that is already wrapping the main make calls for creating build.log. The challenge will be in constructing good grep expressions that catch the relevant parts of the log while filtering out the noise. This will need to be maintained and improved over time.