They've been re-enabled. Rick Fowler has also moved the devices to a different host (okiku from ps-android-sandybridge). It's possible the old host was suffering from a faulty USB controller/bridge which led to the high failure rate. Hoping this resolves the problem.
Francis On Mon, Nov 4, 2013 at 1:29 AM, Thomi Richards <[email protected]> wrote: > Hi Guys, > > Can someone from the CI team please re-enable the maguro runners in the > autopilot jobs once they're back online? We can run without them for now, I > just want to make sure they re-appear once whatever's ailing them is fixed. > > > Cheers! > > > On Mon, Nov 4, 2013 at 8:17 PM, Chris Lee <[email protected]> wrote: >> >> Hi all, >> >> I noticed while running autopilot-trusty-master[1] that there was an issue >> with the maguro runner. >> Turns out that all the maguro nodes have been stuck in a flashing jenkins >> job for 2+ days i.e. [2] >> >> I didn't want to kill the job in case there where other complexities >> (possibility to brick the devices etc.) so I've left them as is. >> I did however update the config for autopilot-trusty-master so that it >> skipped the maguro runner and just used the mako. >> >> >> Chris >> >> [1] http://10.97.0.26:8080/job/autopilot-trusty-master/ >> [2] http://10.97.0.26:8080/job/touch-flash-maguro-0149C7A50E00B013/107/ > > > > > -- > Thomi Richards > [email protected] -- Francis Ginther Canonical - Ubuntu Engineering - Continuous Integration Team -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
