apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vlad Rozov <v.ro...@datatorrent.com>
Subject Re: APEX integration with travis-ci and 4MB log limit
Date Mon, 28 Sep 2015 19:40:34 GMT

Thank you,


On 9/28/15 11:44, Chetan Narsude wrote:
> Verbosity can be reduced to INFO level. It always bugged me that there was
> so much garbage printed as part of debug log, that I was forced to ignore
> even the occasional unexpected exceptions that the tests would spew out.
> The tests should look clean when run, ideally, and print helping messages
> when they fail. While debugging the failing applications/test, one always
> has an option of changing the verbosity to DEBUG so having to do that in
> debug environment is not a problem.
> The only problem would be the tests which fail only during the PR trigger.
> These are time/environment dependent tests and more frequently than not the
> debug log is useless (inconclusive) from the PR test run.
> --
> Chetan
> On Sat, Sep 26, 2015 at 12:32 PM, Vlad Rozov <v.rozov@datatorrent.com>
> wrote:
>> Travis-ci has 4 MB limit on the build log and APEX core "mvn test"
>> produces around 3.7 MB of output. We will not be able to add more unit
>> tests to the project unless we reduce verbosity of the output. Changing log
>> level is one of possible solutions, though it may not be the best one as it
>> will be harder to troubleshoot test failures in the travis-ci environment.
>> I suggest that we put some effort here before the limit is reached.
>> Vlad

View raw message