travis_wait on ./cooker -c

When a long running command or compile step regularly takes longer than 10 minutes without producing any output, you can adjust your build configuration to take that into consideration.

The shell environment in our build system provides a function that helps to work around that, at least for longer than 10 minutes.

If you have a command that doesn’t produce output for more than 10 minutes, you can prefix it with travis_wait, a function that’s exported by our build environment.

https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

.travis.yml

@@ -29,9 +29,9 @@ script:
 - cd $TRAVIS_BUILD_DIR/sdk
 - export J=$(($(nproc)+1))
 - ./cooker -b x86/generic
-- ./cooker --flavor=lime_default -c x86/generic --profile=Generic
-- ./cooker --flavor=lime_mini -c x86/generic --profile=Generic
-- ./cooker --flavor=lime_zero -c x86/generic --profile=Generic
+- travis_wait ./cooker --flavor=lime_default -c x86/generic --profile=Generic
+- travis_wait ./cooker --flavor=lime_mini -c x86/generic --profile=Generic
+- travis_wait ./cooker --flavor=lime_zero -c x86/generic --profile=Generic
 after_success:
 - chmod +x $TRAVIS_BUILD_DIR/.ci/after_success.sh
 - $TRAVIS_BUILD_DIR/.ci/after_success.sh