@BanzaiMan thanks for the info. But I’m afraid that this was probably recently changed.
Context: It was often requested to stop the build on the first failed command. It simply is not useful (and often even harmful) to execute subsequent commands when one fails (e.g. mkdir fails, but cmake runs afterwards). So the solution until now was to use
set -e at the start and
set +e at the end of the script to not interfere with the travis stuff running afterwards.
Until now this worked as expected: On any fail the build stops right after the failed command.
What has changed: The failing command and it’s output are no longer shown.
Is this expected? What is the official guideline on handling failing commands in build scripts? Moving the whole code out into a separate shell script would be a possible solution of course.