Hi guys, As you can see, there are many warn and error log messages and exception messages in the log of Travis.[1] Although they do not cause Travis failure, it makes the log file very large and hard to read useful messages. So, I propose we need to try to fix and reduce these unuseful messages and make the log of build job cleaner.
Another suggestion: we can split the single build job of Hudi's Travis into multiple stages, e.g. Compile and Test and Clean. Please consider this example[2], there are two advantages to this suggestion: 1) It can fail the Travis as soon as possible, if the PR can not be compiled successfully; 2) Split test jobs based on modules will let the contributor location the failed module as soon as possible, instead of waiting and view the whole log file. What do you think? Best, Vino [1]: https://api.travis-ci.org/v3/job/570626673/log.txt [2]: https://travis-ci.org/apache/flink/builds/555743542
