[11:38] <oSoMoN> hello release masters, I got informed by psivaa that « Failures in boottesting with oxide-qt is known and iirc, the release team does add hint for that to be forced », is that correct?
[11:41] <Laney> oSoMoN: I thought that was supposed to be fixed
[11:42] <oSoMoN> Laney, it apparently isn’t, see https://jenkins.qa.ubuntu.com/job/wily-boottest-oxide-qt/lastBuild/console
[11:43] <Laney> I can see that, but it is *supposed* to be
[11:43] <Laney> So we should first find out what is wrong
[11:44] <Laney> Oh. It's not that unity greeter thing. Man, this output is confusing.
[11:50] <oSoMoN> if I read correctly the output, the test that failed is getpkgsrc, but I’m not really sure what that does
[13:07] <Laney> Possibly fixed the test instead (#ubuntu-ci-eng) if any other release team members come along and get tempted to skip it.
[13:07] <Laney> Waiting for review then we can retry this.
[15:44] <quadrispro> tjaalton, hi there! do you have time for this? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1449892
[16:32] <tjaalton> quadrispro: not before monday
[16:34] <quadrispro> alright thx
[16:36] <tjaalton> i'll upload it then
[16:50] <quadrispro> tjaalton, I've uploaded it already to vivid-proposed, AFAIK needs review
[18:56] <tjaalton> quadrispro: hm ok, i need to import it to git then
[20:12] <barry> infinity: i'm looking at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html  -- esp. python-pip and python-pluggy.  are these blocked because of the recent infrastructure outage or something else?
[20:14] <infinity> barry: pluggy is in NEW.
[20:14] <barry> infinity: oh of course
[20:14] <infinity> barry: pip looks like it's blocked on the python DEP-8 tests sucking.
[20:15] <barry> infinity: i'm looking at the amd64 console output.  looks to me like an infrastructure failure
[20:15] <barry> https://jenkins.qa.ubuntu.com/job/wily-adt-python3.4/lastBuild/ARCH=amd64,label=adt/console
[20:16] <infinity> barry: For amd64 yeah, for i386, not so much.
[20:16] <barry> infinity: ack
[20:17] <infinity> barry: In fact, on i386, the failures look very much related to pip...
[20:17] <infinity> ImportError: No module named 'ensurepip'
[20:17] <barry> yay
[20:17] <infinity> Well, some of the failures anyway.
[20:17] <infinity> That testsuite looks to be a mess.
[20:18] <barry> infinity: indeed.  ok, thanks, i'll stare at doko
[20:19]  * barry hugs infinity 
[20:31] <doko> infinity, barry: how's that? these are all networking failures
[20:31] <barry> doko: and now network is cut off in dep-8 tests :(
[20:31] <infinity> The importerror is a network failure?
[20:31] <doko> barry, is this a final decision?
[20:32] <doko> infinity, which one?
[20:32] <barry> doko: i think it already happened, but i'm not positive, and i don't know whether it will be reversed.  i already disabled some network tests in the system-image dep-8 tests
[20:32] <doko> adt-run [16:32:38]: test failing-tests:  - - - - - - - - - - results - - - - - - - - - -
[20:32] <doko> failing-tests        PASS
[20:33] <doko> infinity, known failing tests are run, but ignored
[20:33] <infinity> That's not confusing.  Kay.
[20:34] <infinity> Right, so it's just the connectivity stuff.
[20:34] <infinity> That conversation is still ongoing.