shardulm94 opened a new issue #1198: URL: https://github.com/apache/iceberg/issues/1198
Travis kills a build when there is no output received from the build for 10 mins. As we grow our test cases (especially Spark), we will hit this timeout limit as Gradle by default does not produce an output if tests are working as intended. I hit this issue in #1189 when I updated read tests to also test the vectorized codepaths. https://travis-ci.org/github/apache/iceberg/jobs/707083672#L1408. The spark2 module tests seem to run for > 10 mins now on Travis nodes. There are a few ways I think we can tackle this issue. 1. Reduce the tests we have (Not ideal in the long term) 2. Use `travis_wait` as recommended by Travis for long running tasks. https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received The issue I have with `travis_wait` is that it suppresses the log from the child command till it is complete. Also timeout supplied to `travis_wait` is for the whole child command (in our case `./gradlew check` which already takes about 20 minutes today. 3. Run a background process to output a line to the log every minute. This similar to what I have done in the past at https://github.com/linkedin/transport/blob/6fc9a9274c147e999b8b52ee286973a57bbbd7f2/.travis.yml#L21-L25. We can also use the `travis_jigger` command which does a similar thing (and can have a timeout too) 4. Make Gradle print out the name of every test it ran so that it produces some output as it progresses through the tests ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
