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
The TL;DR is that Travis doesn't always bail immediately on failures. This causes build errors to get buried in output logs as other build steps attempt to continue on. The best course of action thus far is to move the build steps out of the travis YAML format and into build scripts. Similar in concept for the KVM travis run. set -e -x would provide the desired exit on error and tracing the community desires.
The text was updated successfully, but these errors were encountered:
See this thread:
The TL;DR is that Travis doesn't always bail immediately on failures. This causes build errors to get buried in output logs as other build steps attempt to continue on. The best course of action thus far is to move the build steps out of the travis YAML format and into build scripts. Similar in concept for the KVM travis run. set -e -x would provide the desired exit on error and tracing the community desires.
The text was updated successfully, but these errors were encountered: