A user build in our distributed build system failed in CDS archive creation. When this happens, the output contains a lot of data, where the most interesting is usually found last. The output of this command is set to $(LOG_INFO) which means it's not printed by default. The command is wrapped with SetupExecute, which means the output of failed commands is printed at the end of the build, but this output is truncated to the first 15 lines.

The user suggested that we run the build remotely with LOG_REPORT=all, which would remove the truncation in the end of log output, but I don't think that's actually what we want. For most commands, the end of log is just a repeat of the failed command output further up the log. The problem here is rather that we hid the output of the failing command in the first place. I think we need to have a way to configure a default log level for the command output in SetupExecute, but that this level is then ignored when the command fails. Failed commands should always print output to the build log.