Just when you thought things were going smoothly...
Since I got a connection to the leased line, I've been running occasional tests to see how it's performing, and the answer is "patchy". Download speed is mostly consistent, but I see drop offs once in a while, while upload speed is variable. Anything from 2Mbps to 9Mbps, and I see the odd dip where it cuts out completely.
I contacted Zen support yesterday morning and they've been having me run various tests which have now concluded in the fault being on their side of the router. They just this minute opened a support ticket for this, and will be trying to fix the problem remotely, hopefully before Monday. In the event that they can't, they will have to send an engineer out.
The upshot of this is that I may have to delay the switch over to the leased line until this is resolved.
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
Hi all,
Origen07 took itself offline because its ethernet interface appears to have died. I've looked at it, and it really does seem to be dead. This is the second such failure (Origen06 for the same reason). I'll investigate on this one, but we might be seeing a trend.
I'll let you know.
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
I noticed in the reports view, several jobs which have been stuck for a while:
http://validation.linaro.org/lava-server/scheduler/job/33203
-------------------------------------------------------------------------------
origen02
------------
A health check running for 4 days. Nothing in the log. I cancelled it, but it was stuck in cancelling. So I went into admin, put it offline, and then online to run a health check again. The job itself is still showing as not finished. How do I track it down on control so that we can kill it properly?
http://validation.linaro.org/lava-server/scheduler/job/33382
-------------------------------------------------------------------------------
origen04
------------
A regular job that failed, pushed its result bundle and then never quite stopped running. Same deal as 33203, but I can't get it to run its health check. Any clues?
http://validation.linaro.org/lava-server/scheduler/job/33372
-------------------------------------------------------------------------------
panda09
------------
Same as origen04 - can't get health check to run.
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 09/27/2012 05:38 AM, Dave Pigott wrote:
> Hi Andy,
>
> I swapped out the two broken snowballs and put in two new ones and
> they've come up just fine. However, when I go to staging and try to run
> a health check on 10, Conmux gives a "Connection refused" message, which
> is really odd, since I can conmux-console snowball10 on control and
> everything is fine. The really weird thing is that I moved it over to
> production, and the test ran fine. Has something changed subtly on
> staging in the last 24 hours or so?
Ah - I should have warned you. I was worried the connection command I
configured wasn't permanent. I'll look into fixing this for good.
Sorry: I should have mentioned that in my first email
-andy
Hi all,
I Thought I'd let you know that we now have 5 more ST-Ericsson Snowball V11 PDKs in LAVA. They went live yesterday afternoon. In total we now have 10 snowballs but only 8 are available because one of them has been sidelined for staging, and another is not playing ball. I'm working on trying to understand if the board is just dead, or if there there is some other issue. At the moment it's not talking to the outside world at all. I'll keep you posted.
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
----------------------------------------------------------------------
rtsm_ve-a15x4-a7x4_01 & rtsm_ve-a15x4-a7x4_02
----------------------------------------------------------------------
http://validation.linaro.org/lava-server/scheduler/job/33484/log_file
Classic problem, that I also had with the tc2s yesterday. The health check references a snapshot that no longer exists because it's fallen off the bottom.
Andy: I'll look and see if I can find a release that will work on FM. I'll let you know if I succeed (although it should be obvious by the "board" state).
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
Hey Dave,
Thanks for getting all the new snowballs up and running!
As an FYI: I marked snowball10 as "retired" in production and
configured it to run off staging. I'm working through the health check
there now, but I think things are cool.
Hi All,
I notice that there are still some jobs being submitted to LAVA with the device-type "vexpress". This device type is now deprecated and has been replaced by the more specific device type vexpress-a9. The jobs seem to be coming from CI and Android. Could someone amend these submissions?
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
Hi,
I've just had a visit from a couple of guys from the ARM Fast Models team, and they asked an interesting question, namely would there be any interest for us of fast models of current hardware, such as Panda-es, new Samsung board etc.
Off the top of my head, I couldn't think of any, except if we say wanted to run a cluster type test where we might need several dedicated boards, but don't have sufficient real hardware. What about anyone else? Thoughts/ideas?
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
Hi,
We currently do a few builds in Linaro that can boot on a whole set of
device_types.
Example: vexpress android can be build only once, but run in LAVA on
vexpress-a9, -15, -TC2 and fastmodel XX,YY,ZZ, etc.
Unfortunately, we don't really support that use case very well in our
CI so we end up submitting the artifact of a build to only one
device_type automatically.
One approach to that problem would be to grow a feature in the
scheduler to accept jobs that have a list of device_types in the job
description.
Thoughts? Other ideas?
--
Alexander Sack
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
