Lava testing not specific to a pack/board/release
david.gilbert at linaro.org
Mon Nov 7 17:42:19 UTC 2011
On 7 November 2011 16:15, Paul Larson <paul.larson at linaro.org> wrote:
> On Mon, Nov 7, 2011 at 10:56 AM, David Gilbert <david.gilbert at linaro.org>
>> Sure; it's the one in comment #1 of :
>> It's basically a run and as long as it completes within the timeout (and
>> with the right line of text) then it passes.
> So after an hour, it either exits with the proper text, or just hangs? We
> can handle that I think, but it would be nice if we could make it a bit more
> friendly. Is a 1 hour timeout really needed to reproduce the bug in
No, a 5minute timeout on a Panda is fine.
> Can we have it send a signal and shut itself down with an error
> message on exit once it hits the timeout?
I could probably add something like an alarm() call or the like - however,
it would probably be good to have a generic wrapper like that in Lava, since
you can never trust a test to die sanely - especially in this case since what
we're really triggering is a kernel bug.
More information about the linaro-dev