-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make step failures more specific than "bash failed" #143
Comments
If you click on "Invoking bash...", you can see the tool output. You can also download the raw logs. |
I know how to dig into the data. I was calling out that the top-level error is pretty unuseful. This seems to be a negative consequence of wrapping everything in a new bash script as opposed to using ToolRunner directly. |
It would be useful to try and parse error output to get more useful data. |
I don't think even parsing output is needed - simply not wrapping all executables in a bash shell would suffice. |
Description
When a step fails, CI should report the step which failed.
Completion Criteria
Make failures report that colcon (or whatever tool) failed instead of bash.
See https://github.com/RoverRobotics-forks/rmw_cyclonedds/runs/565373542?check_suite_focus=true
The text was updated successfully, but these errors were encountered: