I like this in general, but some things to think about: * Raw serial log is *hugely* important. Without it, some kernel bugs will simply not be visible reliably. * I'm starting to be convinced that we should have to depend on working ethernet - this is already the case with android * Speaking of android... how does this affect testing on android? It sounds as if it may be geared more towards ubuntu image testing * If we require ethernet, what happens when we want to do an ethernet enablement test (this should be coming soon) that wants to bring up/down ethernet interfaces and connect/disconnect them?
Thanks, Paul Larson On Mon, Mar 26, 2012 at 12:55 PM, 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 > > Thanks > ZK > > > > -- > Zygmunt Krynicki > Linaro Validation Team > > _______________________________________________ > linaro-validation mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/linaro-validation >
_______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
