And, the result comes out: if set logging_level to INFO, the size is 28.4MB:
https://staging.validation.linaro.org/scheduler/job/127307.0 Therefore except split big LAVA jobs to small ones, we still need to figure out a way to handle LAVA's own dispatcher messages even with logging_level as INFO. On 3 June 2015 at 16:39, Botao Sun <botao....@linaro.org> wrote: > Hi, > > To get more information I set "logging_level": "DEBUG" in json file: > > > https://staging.validation.linaro.org/scheduler/job/127250/multinode_definition > > which results a 71.2MB file of Dispatcher Log messages: > > https://staging.validation.linaro.org/scheduler/job/127250.0 > > Except these Dispatcher Log messages, the stdout log in DEBUG mode is also > huge - 12.2MB: > > https://staging.validation.linaro.org/dashboard/attachment/173583/download > > By comparison a 13MB CTS stdout file can become a tiny 454kB after > compressed by xz: > > https://staging.validation.linaro.org/dashboard/attachment/173586/download > > So if we can do the same thing to LAVA's own stdout as well as dispatcher > log, I then can set DEBUG without any worries. > > Idea? > > Thanks. > > > Botao > > > > >
_______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-validation
