Re: [RFC] agent-based remote validation invocation for LAVA

2011-02-16 Thread Mirsad Vojnikovic
On 16 February 2011 06:24, Paul Larson 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 in the far

Re: [RFC] agent-based remote validation invocation for LAVA

2011-02-16 Thread Mirsad Vojnikovic
On 16 February 2011 06:10, Paul Larson 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 >>> while oth

Re: [RFC] agent-based remote validation invocation for LAVA

2011-02-16 Thread Mirsad Vojnikovic
On 16 February 2011 05:27, Zygmunt Krynicki wrote: > W dniu 16.02.2011 11:22, Mirsad Vojnikovic pisze: > > > > Zygmunt has already identified key points for Job Dispatcher to support >> this, but one thing I would like to comment: >> >>Another crazy o

Re: [RFC] agent-based remote validation invocation for LAVA

2011-02-16 Thread Mirsad Vojnikovic
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 a

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-15 Thread Mirsad Vojnikovic
On 9 February 2011 20:12, Paul Larson wrote: > On Mon, Jan 31, 2011 at 11:58 AM, Paul Larson wrote: > >> 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 launch a process or thread to handle

Re: LAVA scheduler spec

2011-02-15 Thread Mirsad Vojnikovic
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 wrote: > >> Ah, you are correct, that's excellent - a user story in the scheduler >> should then look something like this: "Dave w

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-14 Thread Mirsad Vojnikovic
On 9 February 2011 20:12, Paul Larson wrote: > On Mon, Jan 31, 2011 at 11:58 AM, Paul Larson wrote: > >> 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 launch a process or thread to handle

Re: LAVA scheduler spec

2011-02-10 Thread Mirsad Vojnikovic
On 10 February 2011 05:41, David Gilbert wrote: > On 10 February 2011 13:14, Mirsad Vojnikovic > wrote: > > > > > > On 10 February 2011 04:30, David Gilbert > wrote: > > >> OK, there were a few cases I was thinking here: > >> 1) A batch of n

Re: LAVA scheduler spec

2011-02-10 Thread Mirsad Vojnikovic
On 10 February 2011 04:30, David Gilbert wrote: > On 10 February 2011 12:19, Mirsad Vojnikovic > wrote: > > That I wrote: > > >> I'd like to add as user stories: > >> Dave wants to rerun a test on a particular machine to see if a > >> failure

Re: LAVA scheduler spec

2011-02-10 Thread Mirsad Vojnikovic
On 7 February 2011 02:05, David Gilbert wrote: > On 4 February 2011 21:53, Paul Larson wrote: > > > > Hi Mirsad, I'm looking at the recent edits to > > https://wiki.linaro.org/Platform/Validation/Specs/ValidationSchedulerand > > wanted to start a thread to discuss. Would love to hear thoughts f

Re: LAVA scheduler spec

2011-02-10 Thread Mirsad Vojnikovic
On 4 February 2011 13:53, Paul Larson wrote: > > Hi Mirsad, I'm looking at the recent edits to > https://wiki.linaro.org/Platform/Validation/Specs/ValidationScheduler and > wanted to start a thread to discuss. Would love to hear thoughts from > others as well. > > We could probably use some more