[02:09] <imgbot> [02:50] <bzoltan> ricmm: https://bugs.launchpad.net/qtmir/+bug/1382414 The breakeage was no introduced by the UITK. I have tested the 1.1.1279.1+14.10.20141014-0ubuntu1 version of the UITK on both 106 and 107 (http://people.canonical.com/~bzoltan/UITK-AP-FAILURES-106-107/) and cornered the rot cause. The new qtmir introduced in the 107 made UITK AP tests fail in a rather incosistent way.
[03:09] <imgbot> [03:42] <bzoltan> elopio:  I think that we should land the silo13 and keep investigating what broke the UITK tests... http://people.canonical.com/~bzoltan/ap-2014_10_18-RTM-SILO15-KRILLIN/README_FIRST
[03:59] <imgbot> [03:59] <imgbot> [04:19] <imgbot> [04:19] <imgbot> [11:11] <ricmm> bzoltan: not sure where you are picking me as saying that UITK is broken
[11:11] <ricmm> bzoltan: my question was in what image did the failrue start, and if you verified the qtmir version at fault by installing a few of them
[17:54] <bfiller> any one around who can publish silo 2? robru? trainguards?
[17:55] <bfiller> fixes the broken sim lock for mako