[03:46] <fginther> michi, can you provide the branch or job that was giving you problems? I want to make sure I get the right branch updated.
[03:46] <michi> fginther: Sorry, no.
[03:47] <michi> Basically, I found a bug in abi-compliance-checker yesterday.
[03:47] <michi> We need to change the way we dump ABI
[03:47] <michi> using abi-dumper
[03:47] <michi> But Wily has a version of that that is too old.
[03:47] <michi> I could have a branch by tomorrow, I think.
[03:48] <michi> But, basically, all we need is for unity-scopes-api to build for vivid+overlay and xenial, instead of vivid+overlay and wily
[03:56] <fginther> michi, I'm getting lp:unity-scopes-api/devel updated now, all the others should already be good to go for you
[03:56] <michi> Awesome, thank you very much!
[04:01] <michi> fginther: there is a very half-baked branch in silo 48 at the moment, for what it’s worth.
[05:41] <Mirv> renatu: sure
[08:14] <pstolowski> hey trainguards, looks like i hit gcc5 bug on ppc64el in the silo https://launchpadlibrarian.net/225718029/buildlog_ubuntu-xenial-ppc64el.unity-scopes-shell_0.5.6%2B16.04.20151110.1-0ubuntu1_BUILDING.txt.gz , only on xenial
[08:14] <pstolowski> was there any gcc5 update recently in X?
[08:21] <pstolowski> anyway, opened https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1515514
[08:33] <Mirv> pstolowski: thanks for opening the bug! doko will look at it probably soon.
[08:40] <pstolowski> Mirv, yw. i hope we can just revert to a previous gcc5 version for now if this is a problem with a minor update
[08:41] <Mirv> pstolowski: that said, I don't see a new gcc5 version in November
[08:42] <Mirv> last one was 2015-10-29
[08:42] <pstolowski> interesting
[08:48] <pstolowski> Mirv, could very well be some other updated of a dependency that triggered it
[08:48] <pstolowski> Mirv, e.g. /usr/include/powerpc64le-linux-gnu/qt5/QtTest/qtesteventloop.h:48:24: internal compiler error: Segmentation fault
[08:49] <Mirv> pstolowski: seems random, my ppc64el rebuild in your PPA worked. let the bug be there but it seems it's not constant. so just run watch_only build now.
[08:51] <pstolowski> Mirv, okay. it's a bit concerning though..
[10:48] <sil2100> jibel: so, seeing the e-mails... do we have everything we need in the overlay now?
[11:10] <jibel> sil2100, we still need a fix for bug 1515356
[11:11] <sil2100> jibel: you prefer to wait for it with gates closed, or should I snapshot now and we cherry pick once there's something releasable?
[11:11] <jibel> sil2100, as you prefer, you do the copies
[11:12] <sil2100> I'll maybe do the snapshot in a moment then
[11:12] <jibel> sil2100, we won't resume silo landing now anyway
[11:12] <jibel> sil2100, we are a bit late on regression
[11:12] <jibel> regression testing I mean
[12:44] <jgdx> rvr, pong
[12:44] <rvr> jgdx: I don't remember now :)
[12:45] <jgdx> rvr, any time
[12:50] <victorp> sil2100, hi
[12:53] <sil2100> victorp: hey
[12:53] <victorp> sil2100, quick q
[12:53] <victorp> ota8 is going according to plan re: schedule?
[12:53] <sil2100> victorp: well... not entirely
[12:54] <sil2100> victorp: we're a bit late on the regression testing right now as there were regressions spotted, so testing might be delayed slightly
[12:54] <sil2100> Yesterday's holiday for many people also didn't help here
[12:55] <victorp> sil2100, ok, but are talking a day or so?
[12:55] <sil2100> Won't be a huge delay though, but I think we should prepare ourselves for a day/two of a delay
[13:22] <brendand> bzoltan_, the crash is a known issue in testtools it seems, although hard to track down as it only happens occasionally to people
[13:23] <brendand> bzoltan_, we are going to make a version of autopilot which will gather some extra info to pinpoint the problem
[13:23] <greyback> trainguards: hi, qtmir is stuck in proposed due to an armhf compile fail against the rest of xenial -proposed. I've a fix for the compile fail ready. How can I proceed? Kick package out of -proposed and re-do the landing just for xenial?
[14:08] <Mirv> greyback: right, if you don't want to land anything now to vivid (understandable because of the freeze), I'd merge&clean the current landing and do a xenial only one time landing to fix the armhf issue. and thanks, I thought the qtmir bug was Qt 5.5 related but it seems it was generic xenial!
[14:31] <greyback> Mirv: train doesn't allow me to force a Merge & clean. Can you do that, and I'll set up the xenial-only silo?
[14:42] <pstolowski> hello trainguards, may i ask for removing any remains of unity-scope-click from silo 8 & its ppa? i once added u-s-click MP to it but then removed it
[14:44] <kgunn> AlbertA: are we stuck on xenial ppc ?
[14:52] <kgunn> robru: hey, what are our options to get silo 18 published ?
[14:53] <kgunn> i'm bumping up against that silo being needed for biz/prodmgmt folks
[14:53] <kgunn> robru: can we publish with followup on disabling that one test for ppc on xenial? or are we going to have to disable and rebuild first ?
[14:59] <bzoltan_> brendand: Good news... in the meantime I have started to reduce the failures in the UITK to ease the pressure on the testtols
[15:09] <kgunn> trainguards could we get a xenial ppc64el only rebuild attempt on silo18 ?
[15:17] <sil2100> o/
[15:17] <sil2100> pstolowski, kgunn: on both of your requests in a minute
[15:18] <pstolowski> sil2100, k, thanks
[15:22] <kgunn> np
[15:23] <Mirv> greyback: done, go ahead with xenial
[15:23] <greyback> Mirv: thanks
[15:28] <cjwatson> kgunn: I've retried that for you
[15:29] <brendand> bzoltan_, always a good idea :)
[15:43] <sil2100> pstolowski: packages removed
[15:44] <pstolowski> sil2100, thanks. but https://requests.ci-train.ubuntu.com/#/ticket/506 still says unity-scope-click in source package names, is it ok?
[15:44] <pstolowski> sil2100, i tried to edit it before, but it was coming back
[15:45] <sil2100> pstolowski: try doing a watch_only build later, it shouldn't appear anymore as it's not in the PPA
[15:45] <pstolowski> sil2100, ah, ok. thanks!
[16:12] <kgunn> trainguards hooray, can someone now publish ? ^
[16:12] <sil2100> kgunn: 18? :)
[16:13] <AlbertA> sil2100: yeah just did a watch on it so it would take the silo out of build failure status
[16:18] <sil2100> kgunn, AlbertA, jibel: is silo 18 for OTA-8 still?
[16:26] <AlbertA> sil2100: I don't know actually, kgunn?
[16:27] <sil2100> I'm snapshotting the PPA and would like to know if I supposed to copy it over as well
[16:27] <pmcgowan> I expect no landings other than regression fixes
[16:28] <sil2100> Ok then
[17:23] <bzoltan_> brendand:  is there a silo or ppa I could test the new AP package?
[17:24] <brendand> bzoltan_, no there isn't anything yet - unfortunately it needs a new version of testtools that isn't in the archive
[17:25] <brendand> bzoltan_, veebers was looking at that, i'll check back with him later
[17:25] <bzoltan_> brendand: is there a way to work around or hack the testtools?
[17:26] <bzoltan_> brendand:  you mentioned that the problem could be when testtols try to log something after a failed test. is there a way to disable it?
[17:28] <brendand> bzoltan_, if you have a log with the crash in it i can tell you, but i lost my traceback so i can't remember what the function was
[17:29] <bzoltan_> brendand:  just tell me the filenames you need from me... I have a fresh crashed device
[17:29] <brendand> bzoltan_, the crash would be on the terminal where you ran autopilot or phablet-test-run
[17:31] <bzoltan_> brendand: http://pastebin.ubuntu.com/13240221/
[17:32] <brendand> bzoltan_, that's not what i was expecting
[17:32] <bzoltan_> brendand: I was expecting a nicely working AP test too :)
[17:33] <brendand> bzoltan_, that's completely different from the traceback i have
[17:33] <brendand> bzoltan_, i need more context
[17:33] <bzoltan_> brendand:  do you want the individual test what messes up the system?
[17:33] <bzoltan_> brendand:  let me do it
[17:33] <brendand> bzoltan_, ideally i would need to see the whole terminal output including the command run
[17:34] <bzoltan_> brendand: the command was  autopilot3 run ubuntuuitoolkit
[17:34] <brendand> bzoltan_, on the device?
[17:34] <bzoltan_> brendand:  yes
[17:35] <bzoltan_> brendand:  phablet-test-run ubuntuuitoolkit
[18:20] <robru> kgunn: so you need a core dev to publish 18 due to the packaging changes.
[18:20] <robru> kgunn: but it sounds like you missed the cutoff for ota8 if I read correctly
[18:51] <jhodapp> robru, mind doing a dput for qtmultimedia from ppa:jhodapp/ubuntu/ppa to silo 9
[18:52] <robru> jhodapp: sure one sec
[18:52] <jhodapp> thanks
[18:52] <robru> jhodapp: done. you're welcome!
[18:53] <jhodapp> excellent thanks
[19:09] <bzoltan_> jibel: if you see somebody from mir folks.. they might be interested about this - http://pastebin.ubuntu.com/13241002/
[19:13] <kgunn> robru: yeah, no biggie missing ota8, more about enabling some biz guys
[19:15] <sil2100> robru, kgunn: yeah, a core-dev is needed here, it's fine to land to the overlay as we're unfreezing now
[20:17] <boiko> trainguards: can someone please trigger a rebuild of dialer-app for xenial armhf on silo 0?
[20:17] <robru> boiko: on it
[20:19] <boiko> robru: thanks
[20:36] <robru> boiko: you're welcome
[20:58] <robru> much qa
[20:58] <robru> wow