When the cross compile build step fails, the raised exception contains all output lines concatenated by \n. It makes it very hard to read the compiler error!
Expected Behavior
The colcon output is well-formatted on failure.
Actual Behavior
A docker.exceptions.ContainerError is raised with a single string, which is printed out as a single line.
To Reproduce
Add a syntax error to dummy_pkg_ros2 and build
System (please complete the following information)
OS: Ubuntu Bionic
ROS 2 Distro: Dashing
Additional context
This should be fairly simple to solve, I think we just need to catch the exception and process the output properly, perhaps via output.split('\n')
Description
When the cross compile build step fails, the raised exception contains all output lines concatenated by
\n. It makes it very hard to read the compiler error!Expected Behavior
The colcon output is well-formatted on failure.
Actual Behavior
A
docker.exceptions.ContainerErroris raised with a single string, which is printed out as a single line.To Reproduce
Add a syntax error to
dummy_pkg_ros2and buildSystem (please complete the following information)
Additional context
This should be fairly simple to solve, I think we just need to catch the exception and process the output properly, perhaps via
output.split('\n')