On Mon, 26 Mar 2012 19:55:59 +0200, Zygmunt Krynicki <[email protected]> wrote: > I've registered another blueprint. This time on LAVA Dispatcher. The > goal is similar as the previous blueprint about device manager, to > gather feedback and to propose some small steps sub-blueprints that > could be scheduled in 2012.04. > > The general goal is to improve the way we run tests by making them more > reliable and more featureful (richer in state) at the same time. > > Please read and comment on the mailing list > > https://blueprints.launchpad.net/lava-dispatcher/+spec/lava-dispatcher-de-emphasize-serial
I basically like this. Let's do it. I think we can implement this incrementally by making a LavaAgentUsingClient or something in the dispatcher, although we'll have to make changes to the dispatcher too -- for example, the lava_test_run actions become a little... different (I guess the job file becomes a little less imperative? Or maybe there is a distinction between actions that execute on the host and those that execute on the board? Or something else?). But nothing impossible. The only thing I'd change is that I don't really see a reason to *not* spam the test output over the serial line and show said spam in the scheduler web UI. We should also store it in neat files on the test image and make sure that those files are what the dashboard's view of events are based on. Cheers, mwh _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
