[Linaro-validation] Daily Graphics WG test jobs
asac at linaro.org
Mon May 7 10:23:37 UTC 2012
On Fri, May 4, 2012 at 11:27 AM, Alexandros Frantzis
<alexandros.frantzis at linaro.org> wrote:
> On Thu, May 03, 2012 at 03:02:24PM +0300, Alexandros Frantzis wrote:
>> Hi all,
>> the Graphics WG needs to run daily graphics-oriented test jobs
>> (actually, we only need to run them whenever something changes, but I
>> think this is not implemented yet). We had previously scheduled a daily
>> job as a cron job in the lab, but it seems that that got lost at some
>> Submitting test jobs from a remote machine (e.g. my desktop) is not
>> really an option, since I think it's important for job runs to be
>> independent of the availability of any one person's computer and
>> Our needs have begun to grow (we need more test jobs) and I would also
>> like to experiment a bit, so pestering someone from the validation group
>> to add or modify scheduled runs doesn't seem very efficient. I would
>> much prefer to have an official mechanism that didn't require the direct
>> intervention of the validation group (e.g. "My scheduled jobs" in the
>> v.l.o web site).
>> We would like to have a set of test jobs running again for 12.05. How do
>> you propose we should handle this in the short-term?
> Hi all,
> thanks for all the suggestions. I am going to experiment with the jenkins
> ci.linaro.org infrastructure for now. Feel free to delete the gfx cron job,
> as it seems to be broken anyway.
Let's chat about what you are trying to do on IRC as I am a bit out of
the loop and I feel some of the problems you try to solve also need to
be solved by DevPlatform team...
Also, we would prefer to keep experiments on that machine to a
minimum. experimental hacking on ci.linaro.org is one major headache
when trying to ensure quality of service for that.
Technical Director, Linaro Platform Teams
http://www.linaro.org | Open source software for ARM SoCs
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
More information about the linaro-validation