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.
This commit is contained in:
Field G. Van Zee
2017-11-20 15:57:06 -06:00
parent a1caeba0ea
commit 13e5d9107b

View File

@@ -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