linaro-release team mailing list archive

[Paul Larson <paul.larson@xxxxxxxxxxxxx>]

It looks like that was just part of the problem.  I don't think it's 50% (nowhere close) but I did find
http://validation.linaro.org/lava-server/scheduler/job/1212
Which seems to indicate that it didn't manage to see address in a reasonable amount of time.  I checked 20 results, and there were a few other failures to upload for other known reasons, but this was the only one like this.  I'd like to keep it open until we understand a little more.  There should be some changes coming soon to help us see things like this a little better, and at least submit *some* kind of result, even if it isn't possible to get the full results off the test system.

Long term, I think we want to make some network changes that should help with this, and a few other issues we have:
1. put a router between us and the rest of the linaro network
2. run our own dhcp server off a real server (not a soho wifi router shared with the office)
3. transparent caching proxy
etc.

We should plan to have all the pieces we need for this by the time we
move to a new office if at all possible.  That would seem a sensible
time to switch over and make other major changes since we'll already
have to be down for that.

** Changed in: lava-lab
       Status: New => Confirmed

** Changed in: lava-lab
   Importance: Undecided => Medium

** Changed in: lava-lab
     Assignee: (unassigned) => Dave Pigott (dpigott)

** Changed in: lava-lab
    Milestone: None => backlog

-- 
You received this bug notification because you are a member of Linaro
Release Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/837063

Title:
  regular network issues prevent LAVA result submission (> 50% of jobs)

Status in LAVA Validation Lab:
  Confirmed

Bug description:
  So while doing the kernel CI builds a bit I ended up looking at job on
  the scheduler.

  I was excited how they run, but then I noticed that probably more than
  50% of the jobs do not submit results due to network problems.

  I only looked at the CI builds, not sure if normal image testing is
  also affected.

  Having not reliable lava is release critical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lava-lab/+bug/837063/+subscriptions