From a4a17c28364f10fdb1420e1f71afda8a7524b7d1 Mon Sep 17 00:00:00 2001 From: Jeff Squyres Date: Tue, 15 Dec 2015 17:07:01 -0500 Subject: [PATCH] travis: use "make -k" to see all failures One of the criticisms of Travis on the call earlier today was that when there's a compile failure, you really only see the *first* compile failure. Then you fix that, resubmit, and 15-60 minutes later, you see the *next* compile failure. Per some discussion with @bosilca and @rhc54 this afternoon, use "make -k", which will have "make" try to continue the build even after compile failures. Hence, you'll be able to see many more compile errors that just one at a time. In some cases (e.g., if there's a typo in a top-level header file), it will cause a bazillion lines of compile error output, but hopefully that should be easy to spot / ignore. --- .travis.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 508d0e1f47..cd6ff119f3 100644 --- a/.travis.yml +++ b/.travis.yml @@ -46,7 +46,7 @@ install: - if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then libtool --version; else glibtool --version; fi - ./autogen.pl - if [[ "$TRAVIS_OS_NAME" == "linux" && "$CC" == "gcc" ]]; then ./configure $CONFIGURE_ARGS --with-libfabric=$HOME/bogus --with-usnic --with-verbs; else ./configure $CONFIGURE_ARGS; fi - - make + - make -k script: - if [[ "$TRAVIS_OS_NAME" == "linux" && "$CC" == "gcc" ]]; then make distcheck; else make check; fi