linaro-validation September 2012

linaro-validation@lists.linaro.org

15 participants
37 discussions

by Dave Pigott

OK. Got the new router, had some teething troubles getting it set up, but I am now connected to it through the leased line as I send this e-mail! Will not do the actual switch over until Monday, because as Alexander noted, I don't want the risk of a disturbed weekend. Thanks Dave Dave Pigott Validation Engineer T: +44 1223 40 00 63 | M +44 7940 45 93 44 Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog

12 years, 11 months

Re: [Linaro-validation] Resolv.conf file missing in test image after deploying on lava -server.

by Dave Pigott

Hi Prakash, As was said in other threads, we sort of understand why resolv.conf isn't there, and it doesn't matter that it's not, so we need to fix the problem where it fails because it isn't there. It should be a trivial fix. Dave Dave Pigott Validation Engineer T: +44 1223 40 00 63 | M +44 7940 45 93 44 Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog On 21 Sep 2012, at 06:58, Prakash Ranjan wrote: > > > ------- Original Message ------- > Sender : Dave Pigott<dave.pigott(a)linaro.org> > Date : Sep 19, 2012 16:10 (GMT+09:00) > Title : Re: [Linaro-validation] Resolv.conf file missing in test image after deploying on lava -server. > > On 18 Sep 2012, at 19:44, Andy Doan wrote: > > > On 09/18/2012 12:44 AM, Prakash Ranjan wrote: > >> Hi All, > >> > >> After deploying any image on my local lava-server setup, in test > >> image , the resolv.conf file is always missing. > >> > >> Here is the complete log link. http//paste.ubuntu.com/1212314/ > >> > >> You can check the job fiel at this link.. http//paste.ubuntu.com/1212328 > >> > >> My master image info : http//paste.ubuntu.com/1212330. > >> > >> Please help me on this issue. > > > > This is a bit of a guess, but I noticed in your job definition you: > > > > 1. flash image > > 2. install lava-test > > 3. boot > > 4. run lava-test > > > > Our jobs normally do those 4 steps but in this order: > > > > 1. flash image > > 2. boot > > 3. install lava-test > > 4. run lava-test > > > > ie steps 2 and 3 are reversed. My guess is that the "boot" step is creating this file so things work for us. You could probably just try that. However, when I look at a current linaro RFS like today's nano image, I see a /etc/resolv.conf in it. > > > > We could probably also patch the dispatcher so it doesn't fail if the file doesn't exist. > > Yeah, I pointed the order issue out to prak on irc yesterday, but he pointed out that there are jobs which do it the other way and succeed, so there's something else going on, and I suspect that it's something to do with the way prak is cacheing the hwpacks and rootfs on his system, but it's difficult to diagnose at a distance. > > Prak filed a bug yesterday to that effect, i.e. to ignore failure on copy, but that feels like a lash up fix because we haven't fully understood what's going on. > > I'll talk to prak again on irc today and see if we can't nail it. > > Thanks > > Dave > > Hi Andy, > I tried with the same order as it was metioned on the linaro web page http://lava-dispatcher.readthedocs.org/en/latest/jobfile.html > Anyway I tried with the both orders as you mentioned above but got the same result. I mentioned the log files in the bug https://bugs.launchpad.net/lava-dispatcher/+bug/1052373 report too. > Here is the log files. > http://paste.ubuntu.com/1218084 -> Complete Log > http://paste.ubuntu.com/1218085 -> Json file > > Prakash > > > <201209211128595_QKNMBDIF.gif>

12 years, 11 months

Re: [Linaro-validation] Resolv.conf file missing in test image after deploying on lava -server.

by Prakash Ranjan

12 years, 11 months

Vexpress status

by Dave Pigott

Hi all, Just a heads up that sometime later today I will be switching the vexpress device type and vexpress-a901 off, and we will be moving to: Device Type Instances vexpress-a5 vexpress-a5-01 vexpress-a9 vexpress-a9-01 vexpress-tc2 vexpress-tc2-01 vexpress-tc2-02 vexpress-tc2-03 vexpress-tc2-04 Notes: * vexpress-tc2-01 will remain offline for external user testing. I'm thinking that perhaps we should switch this around and make that tc2-04 and then remove it from the list to make it tidier * I have one spare a9 tile and a mother board. Does anyone want me to put this in a new motherboard and bring a second a9 online? * Until we have a boot solution for vexpress-a5 that will stay invisible The upshot is, that any jobs you were submitting on a daily basis to device-type vexpress, will now have to be changed to vexpress-a9. Shout now if you want me to delay this switch over. Thanks Dave Dave Pigott Validation Engineer T: +44 1223 40 00 63 | M +44 7940 45 93 44 Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog

12 years, 11 months

Lab health

by Dave Pigott

Only 1 today: ----------------- panda-es03 ----------------- http://validation.linaro.org/lava-server/scheduler/job/32798 Some sort of kernel panic froze the board. Went on to it and rebooted, on the surface seems to be fine. Put back online to re-test Dave Dave Pigott Validation Engineer T: +44 1223 40 00 63 | M +44 7940 45 93 44 Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog

12 years, 11 months

Lab health checks

by Dave Pigott

------------ origen01 ------------ http://validation.linaro.org/lava-server/scheduler/job/32532 wget timeout - restarted. ------------ origen07 ------------ http://validation.linaro.org/lava-server/scheduler/job/32582 Couldn't ping - rechecked and it seems ok now. ------------ origen09 ------------ http://validation.linaro.org/lava-server/scheduler/job/32321 Stream of "timeout waiting for hardware interrupt messages". When I connected to the board it was still producing them and was locked out. Hard reset and it seems ok. Put back online to see if we have a glitch or a failing board. ---------------- snowball03 ---------------- http://validation.linaro.org/lava-server/scheduler/job/32644 eth0 didn't come up, so network failure. Went on the board, did a net restart and all seems ok. Put back online to re-test. Dave Pigott Validation Engineer T: +44 1223 40 00 63 | M +44 7940 45 93 44 Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog

12 years, 11 months

Resolv.conf file missing in test image after deploying on lava -server.

by Prakash Ranjan

12 years, 11 months

more lava wiki changes: meetings pages moved

by Andy Doan

As part of the wiki updates we were making, I've moved our meeting logs and templates over to: https://wiki.linaro.org/Platform/LAVA/Meetings/ I think I've fixed the backlinks, so you'll just need to update your bookmarks.

12 years, 11 months

Re: [Linaro-validation] Resolv.conf file missing in test image after deploying on lava -server.

by Dave Pigott

Hi Prakash, Can you (a) please put in properly qualified URLs next time (you didn't have the ":" after http) and (b) send me the output from lava-master-image-info, rather than lava-device-info. Thanks Dave On 18 Sep 2012, at 06:44, Prakash Ranjan wrote: > http//paste.ubuntu.com/1212330

12 years, 11 months

lava unit testing

by Antonio Terceiro

Hello, I was working on lava-dispatcher today, and I found out that is has (few) unit tests under lava_dispatchers/tests/, and I was wondering if is there a pattern/guideline/etc on how unit tests are used acrosss the lava components. In special: 1) How are we supposed to run the unit tests? I found a .testr.conf file in lava-dispatcher, what gave me some hints, so I started doing $ python -m subunit.run lava_dispatcher.tests.test_suite The output of that was too verbose for my taste, so I ended up using $ python -m unittest lava_dispatcher.tests.test_suite which provides a cleaner output. 2) I had problems running these tests within the system (a VM) where I had lava installed, after activating the virtualenv-like environment with `. /src/lava/instances/$inst/bin/activate`. The commands above were always running the code that was installed in the lava instance instead of the code in the current directory. I guess that is related to the fact that I did not inject that directory to be used by the instance, right? This made me end up running the tests on my main system, where there was nothing installed - only the lava-dispatcher sources + the basic Python stuff. -- Antonio Terceiro Software Engineer - Linaro http://www.linaro.org

12 years, 11 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation September 2012