[15:40] <elopio> barry: https://code.launchpad.net/~canonical-platform-qa/dialer-app/py3autopilot-sleep/+merge/229483
[15:40] <elopio> that solves the old error that only happens on your branch. We have a couple of new ones in mako, but they are from trunk.
[15:40] <elopio> I'll look at them today.
[15:42] <barry> elopio: great!  i'll merge that into my branch and re-push.  hopefully we're nearly there. :)
[15:44] <elopio> barry: we are always nearly there, that's what's frustrating about this branch :)
[15:45] <barry> elopio: there is that :)
[18:36] <barry> elopio: still almostly nearly there ;)
[18:36] <elopio> barry: yes, but now I'm almost sure it's not your branch the cause of the failures.
[18:36] <barry> elopio: phew :)
[18:36] <elopio> so you are almostly nearly done :)
[18:37] <barry> :-D
[21:05] <elopio> ping veebers: I'm curiours about the new autopilot release. Is it happening soon?
[21:05] <elopio> *curious
[21:05] <veebers> hey elopio, well we have a silo and running gatekeeper tests, but the results from the image aren't that sane, so it makes it hard to confirm that autopilot hasn't regressed anything
[21:05] <veebers> elopio: I'll be checking results again soon, although I'm not sure if much has changed :_\
[21:08] <elopio> veebers: from the run #197, the only one that looks weird is the one on the toolkit.
[21:09] <elopio> with so many errors on the toolkit, I would prefer to release autopilot and get screenshots to be able to diagnose them quickly, even we get one or two regressions.
[21:09] <elopio> let me know if I can give you a hand testing the silo.
[21:09] <veebers> elopio: ack, I'll sort that out this morning. CHeers
[21:10] <elopio> thanks.
[22:06] <veebers> elopio: you around still?
[22:06] <elopio> veebers: I am here.
[22:06] <veebers> elopio: ^_^ hey, if you also agree that the test failures I see on the gatekeeper are expected and match those on the smoke dash then I can change autopilot release to tested (test report here: http://pastebin.ubuntu.com/7955749/)
[22:10] <elopio> veebers: unity8 has been stable for a while now. Those 5 failures shouldn't be there.
[22:11] <veebers> elopio: that's from Run 193 right? that was from last week, they don't appear in the most recent 2 runs
[22:11] <elopio> veebers: ah, ok.
[22:11] <veebers> elopio: (there is a lot of text to take in on that 'report' put there are 3 gatekeeper runs-worth  there)
[22:11] <elopio> veebers: do you have a phone with the silo?
[22:11] <elopio> it would be great if you could run the toolkit test that failed. That one is not expected either.
[22:12] <veebers> elopio: not setup right no, I would have to flash to latest etc.
[22:12] <veebers> elopio: It might be faster for me to run the gatekeeper job to just run the uutk tests, that way we have a report too
[22:12] <elopio> veebers: I have just flashed the latest one. i can give it a try.
[22:12] <veebers> elopio: I'll do both
[22:12] <elopio> veebers: no, the toolkit tests take like 40 minutes at least.
[22:12] <veebers> elopio: ack, let me know if you want me to run the gatekeeper
[22:12] <veebers> elopio: ah ok
[22:12] <thomi> veebers: when you get a moment, perhaps later this week, could you please check why this isn't landing? https://code.launchpad.net/~vorlon/autopilot-qt/split-qt4-qt5-binaries/+merge/229378
[22:13] <veebers> thomi: sure thing