Hi all!
This is very good analysis you have done, and I would just add that Monkey
is only one simpler example where the test execution using abrek is not an
option. Another example from Android world is CTS:
http://source.android.com/compatibility/cts-intro.html. Most certainly, all
test suites
On 16 February 2011 06:10, Paul Larson paul.lar...@linaro.org wrote:
Another crazy option would be to expose LAVA Job Dispatcher directly and
allow people to run jobs. In this case one job would use abrek and some
other tools to invoke tests, process results and send them to the dashboard
On 16 February 2011 06:24, Paul Larson paul.lar...@linaro.org wrote:
On Wed, Feb 16, 2011 at 8:16 AM, Zygmunt Krynicki
zygmunt.kryni...@linaro.org wrote:
Yeah, when you mentioned this now I started thinking. Do we really need a
daemon-like component for the dispatcher in general or just
I have now updated the spec with your comments, thanks!
https://wiki.linaro.org/Platform/Validation/Specs/ValidationScheduler
On 11 February 2011 06:52, Paul Larson paul.lar...@linaro.org wrote:
Ah, you are correct, that's excellent - a user story in the scheduler
should then look something
On 9 February 2011 20:12, Paul Larson paul.lar...@linaro.org wrote:
On Mon, Jan 31, 2011 at 11:58 AM, Paul Larson paul.lar...@linaro.orgwrote:
2. One queue TOTAL. One queue may seem like a bottleneck, but I don't
think it has to be in practice. One process can monitor that queue, then
