Build Farm Output is Difficult to Read
Why do I need to look through over 1000 lines of output to figure out what went wrong with the build?
ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A answers.ros.org |
Why do I need to look through over 1000 lines of output to figure out what went wrong with the build?
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.
Please start posting anonymously - your entry will be published after you log in or create a new account.
Asked: 2013-12-26 09:24:27 -0600
Seen: 121 times
Last updated: Dec 26 '13
Build failed in Jenkins with KeyError
What is the update policy on Jenkins plugins for the buildfarm?
Build failing because of dependency issue
How to setup continous integration for private ros repository?
[buildfarm] dpkg-shlibdeps: error: cannot find library
Jenkins buildfarm fails to download file from bitbucket.org [closed]
Problem installing uvc_cam on ARM/Hydro
My package added to shadow-fixed repository with bloom is installed into a wrong path