You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Do not print build commands for every element being built #2142
For one, just 20 lines is not enough to fit most build instructions in my experience. For two, I do not think it adds any value, am I missing a use case? This information is logged per element already. There is already machinery to print logs when an element fails to build, which is actually useful.
I'm not sure I fully understand what you're referring to. Are you referring to the "Running commands" detail output which include the command that is being run? What's the information that "is logged per element already"? Can you please be more explicit and provide examples?
Are you referring to the "Running commands" detail output which include the command that is being run?
This is indeed what I am referring to. I do not think it is particularly useful to do it pre-emptively for every element that is being built in the interactive output and probably not in the main CI output either when element logs exist. Currently what gets printed is:
[--:--:--] START core/gnome-characters.bst: Running commands
meson setup [...]
[20 or so lines of output]
Message contains 47 additional lines
This output is truncated and passes by really fast, so I do not really see the use of it if you need to troubleshoot something.
What's the information that "is logged per element already"?
If you run bst artifact log core/gnome-characters.bst you get the full untruncated output of which commands were run for that element's build, which can be useful for troubleshooting
On build failure you also get a print of the last few commands where the build failed, which can be useful, but this issue is about doing it for every build pre-emptively when no failure has occurred.
I'm not sure I fully understand what you're referring to.
I rushed writing this issue, apologies for that. I will change the title to something more descriptive.
Activity
abderrahim commentedon Jul 9, 2026
I'm not sure I fully understand what you're referring to. Are you referring to the "Running commands" detail output which include the command that is being run? What's the information that "is logged per element already"? Can you please be more explicit and provide examples?
ada-magicat commentedon Jul 9, 2026
This is indeed what I am referring to. I do not think it is particularly useful to do it pre-emptively for every element that is being built in the interactive output and probably not in the main CI output either when element logs exist. Currently what gets printed is:
This output is truncated and passes by really fast, so I do not really see the use of it if you need to troubleshoot something.
If you run
bst artifact log core/gnome-characters.bstyou get the full untruncated output of which commands were run for that element's build, which can be useful for troubleshootingOn build failure you also get a print of the last few commands where the build failed, which can be useful, but this issue is about doing it for every build pre-emptively when no failure has occurred.
I rushed writing this issue, apologies for that. I will change the title to something more descriptive.
[-]Do not print build instructions every time[/-][+]Do not print build commands for every element being built[/+]