Multiarch builds (lxd) always time out on failure instead of exit

[native-api]

Don’t set errexit in the main shell. This shell also runs the build’s internal logic and the sudden exit terminates it abnormally.

If a failing command should terminate the build, put it into a section other than script: – i.e. install. The script: section is designed to run tests – i.e. stuff that you want to run to completion even if something fails.

Multiline `script:` is running without errexit?

This is by design. User commands run without errexit – because, by necessity, they are run with eval in the same shell as other build logic (so that environment changes they make are seen by further commands), so errexit would break the enveloping internal logic. You have a few options here: Put the commands into a separate script and run it (with -e or whatever), as a subprocess. Invoke consecutive commands as cmd1 && \ cmd2 && \ etc so that the status of the first failed command prop…

Travis CI Documentation

Builds are failing with truncated logs when errexit is used

You are setting errexit option, and your build is dying at the first sign of trouble. I would guess that the logs are not flushed when the script dies, giving you an impression that the build is failing at different points. I would suggest removing set -eto figure out how exactly things are failing for you.