[Libclc-dev] [PATCH 1/1] .travis: Make sure we report failure even if only earlier checked files fail
Jeroen Ketema via Libclc-dev
libclc-dev at lists.llvm.org
Sun Oct 8 12:07:43 PDT 2017
Any specific reason for using the value 2?
Otherwise, LGTM
-- Jeroen
> On 8 Oct 2017, at 12:01, Jan Vesely via Libclc-dev <libclc-dev at lists.llvm.org> wrote:
>
> for loop would only report status of the last command
>
> Signed-off-by: Jan Vesely <jan.vesely at rutgers.edu>
> ---
> .travis.yml | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index 2f058a7..5f5de72 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -55,6 +55,8 @@ matrix:
>
> script:
> - $PYTHON ./configure.py --with-llvm-config=$LLVM_CONFIG --with-cxx-compiler=$CXX && make -j4
> - - for f in $CHECK_FILES; do
> - ./check_external_calls.sh built_libs/$f;
> - done
> + - ret=0;
> + for f in $CHECK_FILES; do
> + ./check_external_calls.sh built_libs/$f || ret=2;
> + done;
> + [ $ret -eq 0 ]
> --
> 2.13.6
>
> _______________________________________________
> Libclc-dev mailing list
> Libclc-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/libclc-dev
More information about the Libclc-dev
mailing list