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 point.
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 network.
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?
Thanks, Alexandros
Hi Alexandros,
On 3 May 2012, at 13:02, Alexandros Frantzis wrote:
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 point.
Do you know who set the cron job up? If it's still there I'm sure we can restart it. If not, do you have the details of what tests were run?
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 network.
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).
This certainly strikes me as a great idea. Somewhere you could submit some json jobs that you set a regularity or set of rules on.
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?
As I said, if we can restart what was there, or get the details of what to run, then we can surely help you or point you in the right direction.
Thanks
Dave
Hi
The https://ci.linaro.org/jenkins/ is perfect for this kind of jobs. Deepti can help you setup such job.
BR
/Chi Thu
On 3 May 2012 14:40, Dave Pigott dave.pigott@linaro.org wrote:
Hi Alexandros,
On 3 May 2012, at 13:02, Alexandros Frantzis wrote:
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 point.
Do you know who set the cron job up? If it's still there I'm sure we can restart it. If not, do you have the details of what tests were run?
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 network.
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).
This certainly strikes me as a great idea. Somewhere you could submit some json jobs that you set a regularity or set of rules on.
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?
As I said, if we can restart what was there, or get the details of what to run, then we can surely help you or point you in the right direction.
Thanks
Dave _______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
On 5/3/12 8:37 AM, Le.chi Thu wrote:
Hi
The https://ci.linaro.org/jenkins/ is perfect for this kind of jobs. Deepti can help you setup such job.
+1 - This seems like a better approach to me as well.
BR
/Chi Thu
On 3 May 2012 14:40, Dave Pigottdave.pigott@linaro.org wrote:
Hi Alexandros,
On 3 May 2012, at 13:02, Alexandros Frantzis wrote:
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 point.
Do you know who set the cron job up? If it's still there I'm sure we can restart it. If not, do you have the details of what tests were run?
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 network.
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).
This certainly strikes me as a great idea. Somewhere you could submit some json jobs that you set a regularity or set of rules on.
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?
As I said, if we can restart what was there, or get the details of what to run, then we can surely help you or point you in the right direction.
Thanks
Dave _______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
Hello Dave,
You are welcome to use ci.linaro.org. I have made you part of the "Linaro CI Builder and Testing service" team which is essential to use ci.linaro.org. Please let me know your requirements in a bug @ https://launchpad.net/linaro-ci/+filebug. You can get more information on how to setup a new job and the information that needs to be filled in the bug @ https://wiki.linaro.org/Platform/Infrastructure/LinaroCIQuickReference#How_t... .
On Fri, May 4, 2012 at 3:48 AM, Andy Doan andy.doan@linaro.org wrote:
On 5/3/12 8:37 AM, Le.chi Thu wrote:
Hi
The https://ci.linaro.org/jenkins/ is perfect for this kind of jobs. Deepti can help you setup such job.
+1 - This seems like a better approach to me as well.
BR
/Chi Thu
On 3 May 2012 14:40, Dave Pigottdave.pigott@linaro.org wrote:
Hi Alexandros,
On 3 May 2012, at 13:02, Alexandros Frantzis wrote:
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 point.
Do you know who set the cron job up? If it's still there I'm sure we can restart it. If not, do you have the details of what tests were run?
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 network.
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).
This certainly strikes me as a great idea. Somewhere you could submit some json jobs that you set a regularity or set of rules on.
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?
As I said, if we can restart what was there, or get the details of what to run, then we can surely help you or point you in the right direction.
Thanks
Dave ______________________________**_________________ linaro-validation mailing list linaro-validation@lists.**linaro.orglinaro-validation@lists.linaro.org http://lists.linaro.org/**mailman/listinfo/linaro-**validationhttp://lists.linaro.org/mailman/listinfo/linaro-validation
______________________________**_________________ linaro-validation mailing list linaro-validation@lists.**linaro.org linaro-validation@lists.linaro.org http://lists.linaro.org/**mailman/listinfo/linaro-**validationhttp://lists.linaro.org/mailman/listinfo/linaro-validation
On Thu, May 3, 2012 at 2:40 PM, Dave Pigott dave.pigott@linaro.org wrote:
Hi Alexandros,
On 3 May 2012, at 13:02, Alexandros Frantzis wrote:
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 point.
Do you know who set the cron job up? If it's still there I'm sure we can restart it. If not, do you have the details of what tests were run?
can we get the cron job config file maintained in bzr (or any other VCS) and ensure that we don't manually set things up, but rather regularly pull updates from bzr? In this way we can get people submit their changes and we would create transparency of what is done atm.
Also, what other pieces in LAVA lab are we currently hacking manually that isn't managed through a VCS? I think having an effort to get everything VCS managed etc. might be good.
Michael/Andy: Ideas? Maybe systematically document all the configs etc. we maintain in the lab and review at connect what we do about them?
Replying to all, sorry asac
On Thu, 3 May 2012 16:27:10 +0200, Alexander Sack asac@linaro.org wrote:
On Thu, May 3, 2012 at 2:40 PM, Dave Pigott dave.pigott@linaro.org wrote:
Hi Alexandros,
On 3 May 2012, at 13:02, Alexandros Frantzis wrote:
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 point.
Do you know who set the cron job up? If it's still there I'm sure we can restart it. If not, do you have the details of what tests were run?
can we get the cron job config file maintained in bzr (or any other VCS) and ensure that we don't manually set things up, but rather regularly pull updates from bzr? In this way we can get people submit their changes and we would create transparency of what is done atm.
The cronjobs are run by the lava-auto user in the lab.
They are in bzr already as it happens, although they are at the admittedly random location on LP of:
http://bazaar.launchpad.net/~pwlars/%2Bjunk/generate/
According to crontab -l as lava-auto, we're running
0 9 * * * /home/lava-auto/auto/generate/gwg-daily.sh
ahh, they've been failing with
Traceback (most recent call last): File "./mod-template", line 23, in <module> rootfs_id, rootfs_url = find_latest_rootfs(imagetype) File "/home/lava-auto/auto/generate/find_latest_oneiric.py", line 90, in find_latest_rootfs build_id, filename = find_latest(imageurl, extrapath) File "/home/lava-auto/auto/generate/find_latest_oneiric.py", line 79, in find_latest build_id = "%s.%s" % (lastdate,lastbuild) UnboundLocalError: local variable 'lastdate' referenced before assignment ERROR: <Fault 400: 'Decoding JSON failed: No JSON object could be decoded: line 1 column 0 (char 0).'> EXPERIMENTAL - SUBJECT TO CHANGE (See --experimental-notice for more info)
-- I guess we should set things up so mail from these cronjobs goes somewhere that people actually read...
Also, what other pieces in LAVA lab are we currently hacking manually that isn't managed through a VCS? I think having an effort to get everything VCS managed etc. might be good.
Michael/Andy: Ideas? Maybe systematically document all the configs etc. we maintain in the lab and review at connect what we do about them?
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
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 point.
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 network.
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?
Thanks, Alexandros
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.
Thanks, Alexandros
On Fri, 4 May 2012 12:27:08 +0300, Alexandros Frantzis alexandros.frantzis@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 point.
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 network.
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?
Thanks, Alexandros
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.
I've disabled the cron job. The only jobs we are submitting from cron now are the image tests, and I don't think we'll be doing that for much longer (hi Andy?) so I haven't taken any steps to make sure the scripts are in a more sensible location on LP yet or anything like that.
Cheers, mwh
On 05/07/2012 12:51 AM, Michael Hudson-Doyle wrote:
I've disabled the cron job. The only jobs we are submitting from cron now are the image tests, and I don't think we'll be doing that for much longer (hi Andy?) so I haven't taken any steps to make sure the scripts are in a more sensible location on LP yet or anything like that.
I product pre-built images daily at 19:00UTC for each board with a new hardware pack and combine it with the latest nano and desktop root file systems. I just implemented support for submitting the nano images to LAVA. example:
On Mon, 07 May 2012 12:54:48 -0500, Andy Doan andy.doan@linaro.org wrote:
On 05/07/2012 12:51 AM, Michael Hudson-Doyle wrote:
I've disabled the cron job. The only jobs we are submitting from cron now are the image tests, and I don't think we'll be doing that for much longer (hi Andy?) so I haven't taken any steps to make sure the scripts are in a more sensible location on LP yet or anything like that.
I product pre-built images daily at 19:00UTC for each board with a new hardware pack and combine it with the latest nano and desktop root file systems. I just implemented support for submitting the nano images to LAVA. example:
Does that mean I can disable the other jobs we run from cron?
Cheers, mwh
On 5/8/12 4:00 PM, Michael Hudson-Doyle wrote:
On Mon, 07 May 2012 12:54:48 -0500, Andy Doanandy.doan@linaro.org wrote:
On 05/07/2012 12:51 AM, Michael Hudson-Doyle wrote:
I've disabled the cron job. The only jobs we are submitting from cron now are the image tests, and I don't think we'll be doing that for much longer (hi Andy?) so I haven't taken any steps to make sure the scripts are in a more sensible location on LP yet or anything like that.
I product pre-built images daily at 19:00UTC for each board with a new hardware pack and combine it with the latest nano and desktop root file systems. I just implemented support for submitting the nano images to LAVA. example:
Does that mean I can disable the other jobs we run from cron?
I don't know what all we were doing from cron. However, I suspect we don't need to do daily testing of nano images from cron anymore.
On Tue, May 8, 2012 at 10:18 PM, Andy Doan andy.doan@linaro.org wrote:
On 5/8/12 4:00 PM, Michael Hudson-Doyle wrote:
On Mon, 07 May 2012 12:54:48 -0500, Andy Doanandy.doan@linaro.org wrote:
On 05/07/2012 12:51 AM, Michael Hudson-Doyle wrote:
I've disabled the cron job. The only jobs we are submitting from cron now are the image tests, and I don't think we'll be doing that for much longer (hi Andy?) so I haven't taken any steps to make sure the scripts are in a more sensible location on LP yet or anything like that.
I product pre-built images daily at 19:00UTC for each board with a new hardware pack and combine it with the latest nano and desktop root file systems. I just implemented support for submitting the nano images to LAVA. example:
<http://snapshots.linaro.org/**precise/pre-built/lt-panda/** 137/lt-panda-precise_nano_**20120506-137.info.txthttp://snapshots.linaro.org/precise/pre-built/lt-panda/137/lt-panda-precise_nano_20120506-137.info.txt
Does that mean I can disable the other jobs we run from cron?
I don't know what all we were doing from cron. However, I suspect we don't need to do daily testing of nano images from cron anymore.
This was a relic of when we needed to test images, but didn't have the lava jobs getting kicked off from the build system. So we're not quite there yet it seems, but getting much closer. Is there going to be a summary page generated for each of the builds like what we have on android-build that links to the test results? or just a txt file that points at the job? The summary page is really a nice thing to have, and I've even wondered if it maybe makes sense to make it the consolidation point for both automated and manual tests for that particular build.
Thanks, Paul Larson
On 5/9/12 12:23 AM, Paul Larson wrote:
On Tue, May 8, 2012 at 10:18 PM, Andy Doan <andy.doan@linaro.org mailto:andy.doan@linaro.org> wrote:
On 5/8/12 4:00 PM, Michael Hudson-Doyle wrote: On Mon, 07 May 2012 12:54:48 -0500, Andy Doan<andy.doan@linaro.org <mailto:andy.doan@linaro.org>> wrote: On 05/07/2012 12:51 AM, Michael Hudson-Doyle wrote: I've disabled the cron job. The only jobs we are submitting from cron now are the image tests, and I don't think we'll be doing that for much longer (hi Andy?) so I haven't taken any steps to make sure the scripts are in a more sensible location on LP yet or anything like that. I product pre-built images daily at 19:00UTC for each board with a new hardware pack and combine it with the latest nano and desktop root file systems. I just implemented support for submitting the nano images to LAVA. example: <http://snapshots.linaro.org/__precise/pre-built/lt-panda/__137/lt-panda-precise_nano___20120506-137.info.txt <http://snapshots.linaro.org/precise/pre-built/lt-panda/137/lt-panda-precise_nano_20120506-137.info.txt>> Does that mean I can disable the other jobs we run from cron? I don't know what all we were doing from cron. However, I suspect we don't need to do daily testing of nano images from cron anymore.This was a relic of when we needed to test images, but didn't have the lava jobs getting kicked off from the build system. So we're not quite there yet it seems, but getting much closer. Is there going to be a summary page generated for each of the builds like what we have on android-build that links to the test results? or just a txt file that points at the job? The summary page is really a nice thing to have, and I've even wondered if it maybe makes sense to make it the consolidation point for both automated and manual tests for that particular build.
I'm going to move the .txt file over to an HTML file that works similar to android build in showing results. Its supposed to happen for 12.05.
-andy
On 9 May 2012 08:23, Paul Larson paul.larson@linaro.org wrote:
On Tue, May 8, 2012 at 10:18 PM, Andy Doan andy.doan@linaro.org wrote:
On 5/8/12 4:00 PM, Michael Hudson-Doyle wrote:
On Mon, 07 May 2012 12:54:48 -0500, Andy Doanandy.doan@linaro.org wrote:
On 05/07/2012 12:51 AM, Michael Hudson-Doyle wrote:
I've disabled the cron job. The only jobs we are submitting from cron now are the image tests, and I don't think we'll be doing that for much longer (hi Andy?) so I haven't taken any steps to make sure the scripts are in a more sensible location on LP yet or anything like that.
I product pre-built images daily at 19:00UTC for each board with a new hardware pack and combine it with the latest nano and desktop root file systems. I just implemented support for submitting the nano images to LAVA. example:
Does that mean I can disable the other jobs we run from cron?
I don't know what all we were doing from cron. However, I suspect we don't need to do daily testing of nano images from cron anymore.
This was a relic of when we needed to test images, but didn't have the lava jobs getting kicked off from the build system. So we're not quite there yet it seems, but getting much closer.
We have the LAVA jobs kicked by the build system. Each hwpack build triggers a LAVA job. I've disabled them while LAVA was down and re-enabled yesterday. For the pre-built images, it's on going. See https://blueprints.launchpad.net/linaro-ubuntu/+spec/lava-testing-prebuilt-i...
Is there going to be a summary page generated for each of the builds like what we have on android-build that links to the test results? or just a txt file that points at the job? The summary page is really a nice thing to have, and I've even wondered if it maybe makes sense to make it the consolidation point for both automated and manual tests for that particular build.
Thanks, Paul Larson
On Fri, May 4, 2012 at 11:27 AM, Alexandros Frantzis alexandros.frantzis@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 point.
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 network.
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?
Thanks, Alexandros
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.
linaro-validation@lists.linaro.org
-
Alexander Sack -
Alexandros Frantzis -
Andy Doan -
Dave Pigott -
Deepti Kalakeri -
Fathi Boudra -
Le.chi Thu -
Michael Hudson-Doyle -
Paul Larson