On 26 June 2014 15:24, Tyler Baker tyler.baker@linaro.org wrote:

Hi Lisa,

That looks normal to me. It's showing the pexpect patterns it's trying to match. Feel free to remove DEBUG from your job if you don't wish to see those messages :)

Typically I enable DEBUG in my jobs when I need LAVA to be very verbose (Debugging LAVA code). When running tests I usually remove DEBUG log level.

Hope that helps!

It does. Just wanted to make sure that's normal.

The only reason I've been enabling the DEBUG logging level in my jobs lately because I've noticed that some of the pm-qa test cases don't get executed and I don't always see LAVA_SIGNAL_ENDRUN like in this log (https://validation.linaro.org/scheduler/job/132774/log_file#L_242_0).

But later find out that there's a lava_test_shell timeout message if I scroll down further :)

On 26 June 2014 15:20, Lisa Nguyen lisa.nguyen@linaro.org wrote:

...

Hi,

I noticed that the text in the logs is garbled whenever I add the DEBUG logging level to my definition. I get results like these:

https://validation.linaro.org/scheduler/job/136626/log_file#L_246_0 https://validation.linaro.org/scheduler/job/136887/log_file#L_229_0

If I don't enable DEBUG, then the log looks fine:

https://validation.linaro.org/scheduler/job/136933/log_file#L_23_364

Is this normal behavior? I'd like to read the name of the test cases clearly in the log :)

Lisa

---

linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation

-- Tyler Baker Tech Lead, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog