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 | ros @ Robotics Stack Exchange |
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.
Asked: 2013-12-26 09:24:27 -0500
Seen: 152 times
Last updated: Dec 26 '13
Build failed in Jenkins for cuda cmake error
Build failing because of dependency issue
Build failed in Jenkins with KeyError
Buildfarm issues with shared libraries [closed]
Jenkins: Couldn't find any revision to build
Jenkins error: dpkg-shlibdeps can't find libs building non-catkin pkg
unable to build package now [closed]
New release while ignoring EOL Ubuntu distro