commit 0c5145fc29cf2377fa364aaf848eaf89b886cc28
author Stephen Warren <swarren@nvidia.com> Wed Oct 26 11:05:32 2016 -0600
committer Tom Rini <trini@konsulko.com> Fri Oct 28 22:10:43 2016 -0400
tree e580f0d0e06aea0c0c9d8405961c5373b2d4de4a
parent 43a68e49e13e94416a971a0e65499f1e87d3006d

travis-ci: use correct exit code on errors

The phrase "if [ $? -ne 0 ]; then exit $?; fi" doesn't work correctly;
by the time the "exit" statement runs, $? has already been over-written
by the result of the [ command. Fix this by explicitly storing $? and
then using that stored value in both the test and the error-case exit
statement.

This change also converts from textual comparison to integer comparison,
since the exit code is an integer and there's no need to convert it to
a string for comparison.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Heiko Schocher <hs@denx.de>

.travis.yml

diff --git a/.travis.yml b/.travis.yml
index f91e1bc..33685ce 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -70,11 +70,12 @@
  - if [[ "${BUILDMAN}" != "" ]]; then
      set +e;
      tools/buildman/buildman ${BUILDMAN};
-     if [[ "$?" == "0" || "$?" == "129" ]]; then
+     ret=$?;
+     if [[ $ret -eq 0 || $ret -eq 129 ]]; then
        exit 0;
      else
-       exit $?;
-     fi
+       exit $ret;
+     fi;
    fi
 
 matrix: