-
Notifications
You must be signed in to change notification settings - Fork 146
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
build: Adding option to show full stdout if a stage fails #362
base: main
Are you sure you want to change the base?
Conversation
This fixes #361 |
As I mentioned in the other issue, my personal opinion is that this should be the default behavior and there could be a option or setting that switches it to the current behavior. (This underscores the need for a workspace agnostic catkin tools settings, something like ~/.catkin_tools.conf) |
Strongly in support of this. Any chance it can target 0.4.3? |
I was going to open a new pr that inverts the logic, so that printing stdout was the default behavior and you could configure catkin_tools through a user level config to do the current behavior. However, I haven't had time to do this. Hopefully I'll have a week to catch up on this repository and the others like |
Would this address issue #419? |
@Levi-Armstrong I believe so. |
@rhaschke I think you may be right. I am getting the "how much to print out" versus "where to print what out" confused. |
No description provided.