Build Farm Output is Difficult to Read

answered 2013-12-26 16:01:39 -0500

58457 ●128 ●550 ●526 http://www.ros.org/

If you don't provide the full output, you may miss important things that happen during the build. If the information is not logged it is gone because you don't have access to the build environment for introspection afterwards.

When viewing a failed build I usually start by searching for "error" caps insensitively and find what the error is and work back from there. Using this technique, especially searching from the bottom it usually takes only a couple of seconds to find the failure in a log.

edit flag offensive delete link

Comments

Great tip that I should've asked long ago. I also search `not found`.

130s ( 2013-12-26 16:06:59 -0500 )edit

That is a good tip, but that doesn't alleviate the essential usability problem. I don't argue having access to the log. It's that it doesn't provide any high level information to give a hint other than reading the log. This answer seems to just be RTFM.

David Lu ( 2013-12-27 05:00:41 -0500 )edit

At the highest level you get pass or fail. If you have any suggestions for libraries or algorithms we can apply to them to give a good summary of failures we'd be happy to add them.

tfoote ( 2013-12-27 06:21:12 -0500 )edit

Sounds more like a good enhancement for jenkins (or there might already exist plugins) ?

130s ( 2013-12-27 14:50:47 -0500 )edit

add a comment

1 Answer

Comments

Question Tools

Stats

Related questions

Build Farm Output is Difficult to Read edit

1 Answer

Comments

Question Tools

Stats

Related questions

Build Farm Output is Difficult to Read