[02:09] <imgbot> [02:39] <bzoltan> ricmm:  The +107
[02:42] <bzoltan> ricmm:  The #107 introduced the problem.
[02:43] <bzoltan> I have picked this line from you -> (2014-10-17 22:29:41) ricmm: elopio: hey, have you actually confirmed this as breaking autopilot tests for UITK ?
[02:44] <bzoltan> My connection or client my do funky stuff so it might lost my response ->
[02:45] <bzoltan> (2014-10-18 05:50:31) 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:54] <imgbot> [03:54] <imgbot> [04:14] <imgbot> [04:14] <imgbot>