From 13e5d9107b3763cba46fb1bae87476852601b47c Mon Sep 17 00:00:00 2001 From: "Field G. Van Zee" Date: Mon, 20 Nov 2017 15:57:06 -0600 Subject: [PATCH] Added travis_wait prefix to testsuite via Travis. Details: - It appears that Travis CL has implemented a new policy that results in a test failing if it does not produce any output for more than 10 minutes. (Two test instances are now failing in Travis despite the most recent commit not affecting the library or testsuite.) This issue can be worked around by executing the test run via travis_wait, which takes an optional time parameter. This commit attempts to use 'travis_wait 30' in the .travis.yml file to prevent the early failure at 10 minutes. --- .travis.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 24c426396..472983725 100644 --- a/.travis.yml +++ b/.travis.yml @@ -72,5 +72,5 @@ script: - export BLIS_IR_NT=1 - export BLIS_JR_NT=1 - if [ $RUN_TEST -eq 1 ]; then make BLIS_ENABLE_TEST_OUTPUT=yes test; fi - - if [ $RUN_TEST -eq 1 ]; then ./build/check-test.sh ./output.testsuite; fi + - if [ $RUN_TEST -eq 1 ]; then travis_wait 30 ./build/check-test.sh ./output.testsuite; fi