On 26 June 2014 15:24, Tyler Baker <tyler.baker(a)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(a)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(a)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/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi LAVA Team
I'm impressed about the work you have done so far. Great Job!
I've seen a NI setup in one of your presentation slides.
Does NI supports Linux in a useful way (without LabView)?
And what are the pros and cons and your experience of using NI in a Linux
environment?
Best regards
Markus
# Progress #
* Bug 1328780 - No LAVA API method available to retrieve LAVA job ID #
* LAVA Sprint
* Time
* Bugs - 10%
* various code reviews - 90%
# Plan #
* Continue with pending cards and bugs
--
Senthil Kumaran
http://www.stylesen.org/http://www.sasenthilkumaran.com/
# Progress #
* [REQ-342]
* Waiting for test image (Built debug kernel with all debug options, but
can not have it boot successfully)
* [REQ-304]
* Complete yaml file
# Plan #
* [REQ-343]
* [BUG-1296880]
# Progress #
* [QA-716]
* Submitted the patch and waiting for review
* [QA-715]
* The patch had been submitted and waiting for review
* [REQ-342]
* Wrote dmesg parser and test it with initramfs environment
* Waiting for test image (Built debug kernel with all debug options, but
can not have it boot successfully)
# Plan #
* [REQ-342]
* [BUG-1296880]
# Progress
* LAVA-997: capture stdout line number data from lava-test-case
* LAVA-1348: update lava-android-test after merging linaro-dashboard-bundle into lava-dispatcher in master
* Bug 1290973: ensure lava_test_shell timeout fails
* Preparing for sprint and creating new BBB image for community support
* Time
* cards: 20%
* bugs: 30%
* code reviews: 20%
* bbb: 30%
# Plan
* LAVA sprint & dispatcher refactoring.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
Hi,
I finally got tired of having to remove actions from my job json file
instead of being able to comment them out and hacked up a shell script
that lets me write my jobs in YAML:
https://gist.github.com/mwhudson/89d0f880f85aadca0493
(there is a sample, slightly terrifying, job in YAML in the gist too).
I've only been using this for about 15 minutes but I think I like it
already ;-)
Cheers,
mwh
