[00:15] <robru> Ursinha: LOL ^ ;-)
[00:15] <robru> I think it's working ;-)
[00:18] <Ursinha> robru: \o/ awesome!
[00:24] <jdstrand> hey, rtm silo 007 needs the new apparmor 2.8.96~2652-0ubuntu5 that is in utopic. so, I need a resync. is that self-serve? if not, how do I do that?
[00:27] <robru> jdstrand: well, your landing request just says 'apparmor' which implied you are responsible for uploading that to the silo yourself. you probably wanna change that to 'sync:ubuntu,utopic apparmor' and then you can just run the build job and it'll sync in the new apparmor for you
[00:28] <jdstrand> robru: ok, thanks. at the time, I did upload it. I could just upload it again, but wasn't sure if there was a better way
[00:28] <jdstrand> thanks
[00:32] <robru> jdstrand: you're welcome. whether or not you consider the heaping pile of untested citrain code "a better way" is up to you.
[00:32] <robru> jdstrand: also you need to reconfig after changing that landing request
[00:39] <robru> sigh
[00:40] <robru> watch-ppa is still busted.
[00:42] <robru> jdstrand: hm seems like the upload failed. the ppa only has 0ubuntu4
[00:42] <robru> I love how the utter lack of the uploaded package in the PPA qualifies as a successful build.
[00:45] <robru> jdstrand: i guess try rebuilding, if it fails again you'll have to manually upload to the PPA then do a WATCH_ONLY build. I'm off for dinner, may check back in later.
[00:46] <elopio> plars: still here? my gallery run didn't save the subunit file https://jenkins.qa.ubuntu.com/job/generic-click-autopilot-runner-mako/581/?
[00:47] <elopio> maybe the run command is generating only the xml, not the subunit.
[00:54] <jdstrand> robru: so, I tried the sync, but it gave me a new version that was lower than what is currently in the rtm, so I did just 'apparmor', then reconfigure then watch only. it failed cause ubuntu4 was in there, so I deleted it, prepared the ppa, reconfigured then watch only. it seems to all be working now
[00:54] <jdstrand> I forgot to mention I uploaded ubuntu5 to it somewhere along the way
[01:23] <robru> jdstrand: right. One day ci train will be replaced with something that works. One day.
[02:10] <imgbot> [02:21] <ToyKeeper> robru: Any chance we can get rtm/landing-002 (UITK) into the next RTM build?
[02:21] <ToyKeeper> IIRC, that starts in about 40 minutes.
[02:29] <ToyKeeper> robru: I'm not sure how long that process takes.
[02:29] <plars> elopio: hmm, the one I thought you were pointing at before was the one under generic-mediumtests-utopic
[02:29] <robru> ToyKeeper: depends on the autopkgtests in the proposed migration
[02:30] <robru> ToyKeeper: well you can just forget about that because ci train just decided to delete the silo.
[02:32] <plars> elopio: so you would see them here for instance: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-utopic/3702/?
[02:32] <plars> elopio: what's the distinction between those two jobs? do you know offhand?
[02:32] <robru> ToyKeeper: https://ci-train.ubuntu.com/job/ubuntu-landing-009-2-publish/19/console also the MPs aren't even approved. jeez
[02:33] <ToyKeeper> A wise old wizard once said, "Nothing is ever easy."
[02:43] <robru> ToyKeeper: so I'm EOD, but get bzoltan1 to approve the merges, then get Mirv to publish in utopic, and then once that's done we can rebuild & retest & publish the RTM packages.
[02:44] <ToyKeeper> robru: Thanks.  I'm just sending a summary to QA, since we were kinda planning on doing promotion testing on this image and that's not going to happen.
[03:09] <imgbot> [03:11] <robru> oh holy god
[03:13] <robru> oh, it seems queuebot restarted, thankfully i dont see anything wrong with the spreadsheet
[03:42] <bzoltan1>
[03:44] <bzoltan1> robru: ToyKeeper: I hold back the approval to have a sencond run of the RTM silo002 tests. The first run was OK and I have shared th eresults with brendand-nexus5.  Here you go with the latest results -> http://people.canonical.com/~bzoltan/ap-2014_09_22-RTM-SILO2-KRILLIN/
[03:44] <bzoltan1> Mirv: ^
[03:55] <imgbot> [03:55] <imgbot> [04:01] <bzoltan1> Mirv: robru: bregma: ToyKeeper: and here is the first half of the Ubuntu tests -> http://people.canonical.com/~bzoltan/ap-2014_09_22-UBUNTU-SILO9-MAKO/ For some reason the calculator tests hanged, so I had to restart in the morning.
[04:03] <bzoltan1> ToyKeeper: brendand-nexus5: robru: Mirv: I see lots of hanging, crashing AP tests. The adb connection can get unstable and some of the tests just do not work. So i trust only the fully OK tests. I would suggest heavy manual and visual tests before releasing the new UITK. With more autopilot we can not get any further from this point.
[04:06] <Mirv> :( I'm not looking forward to validating my qtbase patch release then
[04:09] <veebers> bzoltan1: any idea where the hangs/crashes originate? (i.e. autopilot, the tests, adb)
[04:15] <imgbot> [04:15] <imgbot> [04:24] <Mirv> bzoltan1: so, what's the situation with rtm 002? QA says it has signed it off, but you say it's not? and for some reason you've just kicked a no-change rebuild of it?
[04:30] <Mirv> bzoltan1: reading the backlog further, it seems robru says ci train deleted the packages. ok then. robru btw: they could have been salvaged by going to Copy Packages and doing binary copy of the deleted packages to the PPA itself.
[04:31] <Mirv> it's obviously the same version that QA signed off, but I'm unsure how to proceed now
[04:31] <bzoltan1> veebers:  yes, there ... tests, adb, autopilot. In short, no idea.
[04:32] <veebers> bzoltan1: heh ack
[04:32] <bzoltan1> Mirv:  I have not kicked off anything right now. I rebuilt both silos yesterday evening and run the AP tests overnight.
[04:33] <Mirv> bzoltan1: oh, right, it was robru who kicked the rebuild
[04:33] <bzoltan1> Mirv:  From my point the RTM silo2 and the Ubuntu silo9 are good to go. If QA has signed them than it is a shared responsibility to release.
[04:33] <Mirv> bzoltan1: anyhow, it was no-change rebuild that finished an hour ago
[04:33] <Mirv> bzoltan1: I published silo9. robru just mentioned "we can rebuild & retest & publish the RTM packages". I think traditionally for no-change rebuilds smoke-testing has been enough, could you do that?
[04:34] <bzoltan1> Mirv:  What I mean is that the last two regressions (icon in gallery and messed header in dialer) were both _visual_ regression and not functional. So there are things we can not capture with 900+ tests.
[04:34] <Mirv> bzoltan1: ah, right, now I get the context :)
[04:35] <bzoltan1> Mirv:  the rtm silo2 has been rebuilt and retested -> http://people.canonical.com/~bzoltan/ap-2014_09_22-RTM-SILO2-KRILLIN/
[04:36] <Mirv> bzoltan1: but it was rebuilt again 1h ago because train destroyed the packages. no changes though, but I was wondering if you could install them on your rtm device and just 5min smoketest.
[04:36] <Mirv> (I assume robru needed to do a reconfigure and at that point train removed them)
[04:37] <bzoltan1> Mirv: I know :) it sounds suspicious, but I just wish to be honest and open about the risks.
[04:37] <robru> Mirv: bzoltan1 yes there's a bug in the train that makes it delete ppa packages during a reconfigure. I neutered that bit of code just now as it had bit me one too many times, so this issue shouldn't pop up again, but still i needed to rebuild the packages
[04:37] <bzoltan1> Mirv: The RTM silo2 has exactly the same version as the Ubuntu silo9 and the version I have run 4 full round tests.
[04:38] <robru> bzoltan1: yes but that package was deleted and rebuilt despite being the same version, so it's not really "the same" package
[04:39] <robru> Mirv: didn't know you could copy deleted packages back into a PPA, thanks for that
[04:39] <Mirv> robru: heh, thanks for the fix, it has bitten me too enough times
[04:39] <bzoltan1> robru:  do you want me to re-run the tests again? I have no problem with that. Only it would add 4-6 hours.
[04:40] <Mirv> bzoltan1: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-002/+packages <- 58 minutes ago <- it's the same as built 10h ago <- but we have tradition that even after no-change rebuild the new packages are still installed on device and the device is at least rebooted
[04:41] <Mirv> robru: in the past we've done just smoke-testing if the source hasn't changed but a packages has been rebuilt
[04:41] <bzoltan1> Mirv:  I go and do that right now. Plus I wil run few tests... the UITK and the browser for example
[04:42]  * bzoltan1 is flashing version 56
[04:43] <Mirv> bzoltan1: ok then
[04:43] <robru> bzoltan1: sorry for the trouble, blame the train, but take consolation in the knowledge that this bug won't bite again ;-)
[04:44] <bzoltan1> robru:  this is absolutely no problem :)
[04:45] <bzoltan1> robru:  I am eating my morning oatmeal and drink my tea ... all the same what I do in the meantime :)
[06:45] <rsalveti> Mirv: congrats
[06:48] <bzoltan> Mirv:  the rtm silo2 with the #56 boots and looks identical to the previous version.
[06:49] <Mirv> rsalveti: thanks :) MOTU makes lifes a bit more easy
[06:50] <Mirv> bzoltan: cool, publishing
[06:50] <rsalveti> yeah :-)
[06:51] <tvoss> good morning :) can I get a silo assigned for line 75?
[06:52] <bzoltan> Mirv:  thank you.
[06:53] <Mirv> tvoss: landing-019
[06:53] <tvoss> Mirv, excellent,thank you
[06:53] <bzoltan> Mirv:  how about the silo9 for Ubuntu?
[06:54] <bzoltan> Mirv:  it is as good and as tested as the RTM.
[06:55] <Mirv> bzoltan: already pubished when I woke up
[07:05] <bzoltan> Mirv:  that is cool
[07:10] <brendand> bzoltan, some problems with the uitk landing?
[07:10] <bzoltan> brendand: not as I know
[07:11] <popey> anyone updated their nexus 4 beyond ubuntu-touch/devel-proposed 251 this morning?
[07:11] <brendand> bzoltan, ok it's published. i read in the morning there were some issues
[07:11] <bzoltan> brendand: Mirv: I am not sure if we need to ping somebody on #ubuntu-release
[07:19] <Mirv> bzoltan: beta freeze is in effect until Thursday
[07:20] <Mirv> not sure if pinging would help
[07:22] <rsalveti> popey: latest image is dead here for me it seems
[07:23] <popey> rsalveti: which one?
[07:23] <rsalveti> wonder if apparmor related
[07:23] <rsalveti> a bunch of packages got dropped as well
[07:23] <rsalveti> trying to flash 48 on krillin (utopic)
[07:23] <rsalveti> can't get out of the boot logo
[07:26] <bzoltan> Mirv:  you mean that there is no chance to land the UITK  on our trunk before Thursday?
[07:29] <Mirv> bzoltan: well, feel free to try on the release channel. alternatively, it is possible to force merge&clean if you want to eg start preparing the next one. the uitk has landed anyway where it matters to us.
[07:29] <bzoltan> Mirv: for me the trunk matters the most
[07:31] <Mirv> bzoltan: I meant rtm/14.09, so no reason not to clean
[07:34] <ogra_> rsalveti, remove lightdm from the upstart stanza in the adbd job via recovery
[07:35] <rsalveti> ogra_: hm, why?
[07:35] <ogra_> to debug why it hangs ?
[07:35] <rsalveti> how this got broken?
[07:35] <rsalveti> oh, indeed
[07:35] <sil2100> o/
[07:35] <rsalveti> testing my landing with 47 now, will retest 48 later
[07:35] <ogra_> rsalveti, it broke with the last media-hub landing
[07:35] <rsalveti> but we can trigger 49 already, new kernel and new android
[07:35] <sil2100> Damn, I hope I didn't catch a cold yesterday, brrr
[07:36] <rsalveti> how could, not even booting
[07:36] <rsalveti> http://people.canonical.com/~ogra/touch-image-stats/252.changes
[07:36] <rsalveti> this is the changes file
[07:36] <ogra_> rsalveti, yeah, thats a bit weird, we know unity8 tests han hard with that package
[07:36] <ogra_> oh
[07:36] <ogra_> you are talking about utopic
[07:36]  * ogra_ was talking rtm :P
[07:37] <ogra_> rsalveti, hmm, what was the customization hooks chnage ?
[07:37] <rsalveti> utopic because I need it for my landing :-)
[07:37] <bzoltan> Mirv:  so it is possible to merge from the RTM silo2?
[07:37] <ogra_> looks like one package that could intercept the boot
[07:37] <rsalveti> ogra_: I think related with apparmor
[07:37] <ogra_> yes
[07:38] <ogra_> precompiled profiles
[07:38] <rsalveti> surprised by the amount of dropped packages
[07:38] <rsalveti> and wonder why that
[07:38] <ogra_> yeah, some deps seem to have been dropped
[07:39] <ogra_> nothing should break the boot though
[07:40] <rsalveti> yeah
[07:40] <bzoltan> ogra_:  I have question :) How can I tell from adb shell that the device is booted up to the welcome wizard?
[07:41] <Mirv> sil2100: ogra_  new uitk now in rtm... image build?
[07:41] <ogra_> bzoltan, should be checkable via initctl (if not via something like pgrep)
[07:41] <Mirv> bzoltan: utopic can be m&c:d before it's in release pocket, if needed for next preparations
[07:41] <ogra_> Mirv, sure, if sil2100 agrees ... trhough i wonder if we shouldnt roll back media-hub first
[07:43] <bzoltan> Mirv:  thanks, now I understand it. Cool
[07:45] <bzoltan> ogra_:  I have no idea what to look for with initctl
[07:47] <sil2100> ogra_: let me take a look at that roll-back
[07:59] <seb128> hey there
[08:00] <seb128> is there a known issue with CI runs on merge requests failing with "I: Unlock failed"
[08:00] <ogra_> rsalveti, would you mind top approving https://code.launchpad.net/~ogra/phablet-tools/phablet-tools-fix-edge-intro/+merge/235440 ? seems sergiusens forgot about it and i need to land it today
[08:01] <ogra_> seb128, i know that mterry and plars discussed unlocking flakiness in unity8 a few times over the last week
[08:01] <seb128> ogra_, do you know if there is a bug recording the discussion?
[08:01] <ogra_> *in unity8 unlocking (sorry)
[08:01] <ogra_> not sure
[08:04] <ogra_> seb128, bug 1370644
[08:04] <seb128> ogra_, danke
[08:04] <ogra_> :)
[08:05] <sil2100> ogra_: I'll revert the 3 packages that landed for RTM
[08:05] <ogra_> sil2100, +1
[08:05] <ogra_> sil2100, do we want to wait with an image build ?
[08:08] <sil2100> ogra_: yeah, I guess it would be best
[08:08] <sil2100> ogra_: I'll need your help with uploading dbus-cpp though
[08:08] <sil2100> (since it's in main)
[08:10] <Mirv> Feels like: -6'C... I can feel it
[08:10] <sil2100> ...winter is coming? ;)
[08:11] <Mirv> I wish :)
[08:11] <sil2100> ogra_: can you fetch dbus-cpp from http://people.canonical.com/~lzemczak/packaging/ and upload to RTM?
[08:11] <sil2100> ogra_: I'll upload the two others then
[08:13] <Mirv> sil2100: was utopic mir 0.7.3 all fine, or do we want to wait for the next image build before publishing it to rtm?
[08:13] <Mirv> (QA has signed it off now)
[08:13] <sil2100> I think it was fine, but let's wait with the publishing for us to kick a new image
[08:14] <sil2100> Just in case ;)
[08:14] <Mirv> sounds good
[08:14] <Mirv> I hope davmor2 is not back, since I don't have cats today either
[08:14] <ogra_> sil2100, bah, i 'll need to re-pack it ... (teh direct upload will be rejected if the sseries isnt 14.09)
[08:15] <sil2100> It's not 14.09? Damn, then the revert script still has issues
[08:15] <sil2100> grrr
[08:15]  * sil2100 repacks the others too
[08:15] <ogra_> Changes:
[08:15] <ogra_>  dbus-cpp (4.0.0+14.10.20140909~rtm.is.4.0.0+14.10.20140808-0ubuntu1) utopic; urgency=medium
[08:17]  * sil2100 fixes the script too
[08:17] <sil2100> Anyway, uploading the rest now
[08:19] <sil2100> ogra_: to make sure qtubuntu-media builds against the right media-hub, I'll have to wait for media-hub to build first in the archive
[08:19] <sil2100> So it will take a moment I guess
[08:20] <ogra_> sil2100, ok, then after the meeting
[08:22] <davmor2> Mirv: you'd better have cats, that or we really need popey to have salem in the room
[08:23] <popey> \o/ cats
[08:26] <davmor2> Morning all
[08:31] <sil2100> ogra_, davmor2, Mirv: be there in a minute
[08:32] <Mirv> thanks popey for saving the day
[08:34]  * popey stabs chrome
[08:34] <popey> also firefox
[08:38] <davmor2> popey: stick with the webbrowser app :D
[08:40] <popey> all browsers suck
[08:40] <popey> [FACT]
[08:49] <davmor2> popey: maybe you just use them wrong :P
[08:49] <ogra_> mandel, tickle
[08:49] <popey> not possible
[08:50] <davmor2> popey: inconceivable, you mean surely :)
[09:00] <ogra_> psivaa, hmm, looking at the console log of the 252 test ... do you actually have adbd runnin on the device after it failed ?
[09:01] <psivaa> ogra_: let me check
[09:01] <ogra_> (it seems like it can adb shell but no upstart user session is running ... that indicates that the adbd emergency shell started ... which it only does if lightdm crashes or the container doesnt come up)
[09:02] <popey> can someone ( psivaa ?) tell me what the latest comment on this means? https://code.launchpad.net/~zeller-benjamin/reminders-app/sdkcompat/+merge/233743 - I tried re-running, same error.
[09:02] <mandel> ogra_, yes?
[09:02] <ogra_> mandel, two things ...
[09:02] <ogra_> mandel, i need top approval on https://code.launchpad.net/~ogra/phablet-tools/phablet-tools-fix-edge-intro/+merge/235440
[09:02] <mandel> ok
[09:02] <sil2100> mandel: hey!
[09:02] <ogra_> mandel, and the other issue is that tvoss obvously ybroke media-hub when he ported it to dbus-ccp ...
[09:03] <ogra_> mandel, and then went on holiday ...
[09:03] <sil2100> mandel: right, can you help us fixing that? Do you know the dbus-cpp code-base well?
[09:03] <ogra_> mandel, we look for someone who understands that stuff :)
[09:03] <mandel> la puta de oros (do not look for that in a dictionary)
[09:03] <mandel> ogra_, sil2100 on it!
[09:03]  * ogra_ hugs mandel
[09:03]  * sil2100 hugs mandel as well
[09:04] <mandel> sil2100, ogra_ can you let me know the issues/symptoms ?
[09:04] <ogra_> one sec
[09:04] <ogra_> we have a bug for that
[09:04] <psivaa> ogra_: adbd is running with 252
[09:04] <sil2100> mandel: so, the media-hub that's in utopic seems to be broken now (due to the mentioned porting to dbus-cpp) and it's causing the unity8 autopilot tests to hang
[09:04] <sil2100> https://bugs.launchpad.net/bugs/1371454
[09:04] <sil2100> mandel: this is the main bug I guess ^
[09:05] <mandel> sil2100, ogra_ ok, and do we know the MR that broke this?
[09:05] <sil2100> mandel: let me find those, one moment
[09:05] <ogra_> psivaa, can you log in and do: sudo lxc-info --name android
[09:05] <sil2100> ogra_: btw. did we try only downgrading dbus-cpp to fix this bug?
[09:06] <ogra_> psivaa, as well as: sudo initctl status lightdm
[09:06] <ogra_> sil2100, i doubt that would work, since a bunch of hard dependencies were added
[09:07] <sil2100> mandel: so, it got broken somewhere in these merges:
[09:07] <sil2100> mandel: http://paste.ubuntu.com/8409382/
[09:08] <mandel> ok
[09:08] <sil2100> ogra_: since with the media-hub landing, there was also a dbus-cpp landing which didn't change the ABI or anything (was only some quick bugfix)
[09:08] <mandel> sil2100, ogra_ I'll investigate and will ping you with info
[09:08] <sil2100> ogra_: maybe that one small change actually causes havoc?
[09:08] <sil2100> mandel: you're our hero!
[09:09] <psivaa> ogra_: 'lightdm stop/waiting' and http://pastebin.ubuntu.com/8409388/
[09:10] <ogra_> psivaa, thanks !
[09:10] <ogra_> so lightdm definitely crashes on start
[09:10] <ogra_> (and the adb emergency shell works as expected, yay !)
[09:12] <psivaa> popey: i'll take a look
[09:12] <psivaa> popey: Also, could you please ping 'cihelp' for the queries like this in the future if there is no specific vanguard is available.
[09:12] <popey> thanks
[09:12]  * ev hugs psivaa
[09:12] <psivaa> :D
[09:12] <popey> ok
[09:21] <mandel> sil2100, ogra_ did you see that downgrading gstreamer seems to fix the issue?
[09:21] <ogra_> mandel, oh ? i thought it doesnt
[09:21] <mandel> ogra_, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1371454/comments/13
[09:21] <ogra_> mandel, hmm, right
[09:21] <sil2100> Wait, it does? But we don't have the new gstreamer in RTM and it's reproducible there
[09:22] <sil2100> Or do we?
[09:22] <ogra_> my last knowledge was comment 12
[09:23] <psivaa> popey: for that MP, continuous-integration -> approved and it's the Autolanding that failed. This could be due to a review still being in 'needs fixing' fro mzanetti. that needs to be 'approved' before landing
[09:23] <mandel> sil2100, ogra_ is going back a number of revs.. I'll take a look at what has changed, maybe it will give us a clue
[09:23] <ogra_> mandel, only two ubuntu versions though
[09:23] <popey> psivaa: oh, interesting. thanks.
[09:23] <popey> mzanetti: ^
[09:24] <ogra_> mandel, but if it is really gstreamer, probabaly involving Laney would make sense
[09:24] <mandel> ogra_, yes
[09:24] <mzanetti> popey: ?
[09:24] <mzanetti> popey: what branch
[09:24] <popey> mzanetti: https://code.launchpad.net/~zeller-benjamin/reminders-app/sdkcompat/+merge/233743
[09:29] <popey> thanks mzanetti
[09:30] <sil2100> ogra_: but how come it's reproducible on RTM if gstreamer hasn't been updated?
[09:30] <sil2100> ogra_: I mean, I don't remember us updating gstreamer at all in RTM
[09:30] <ogra_> sil2100, it has ... kgunn was going back two versions
[09:30] <seb128> you guys are still discussing gstreamer issues?
[09:31] <ogra_> seb128, see bug 1371454
[09:37] <ogra_> sil2100, sorry, got distracted ... the new gstreamer landed around the day we did the initial rtm sync ... thats why you never saw an upload
[09:46] <mandel> ogra_, approved
[09:46]  * ogra_ hugs mandel again
[09:47] <ogra_> damn ... i cant get an adb shell on 252
[09:47]  * ogra_ wonders whats different with the smoke test devices
[09:47] <ogra_> psivaa, that adb shell you did, was that on mako ?
[09:47] <ogra_> oh
[09:47] <psivaa> ogra_: yes
[09:48] <ogra_> seems i'm just to impatient ... now the screen blanked
[09:48] <ogra_> i guess it was just busy with apparmor and now respanwns lightdm til it fails
[09:48]  * ogra_ leans back and waits a bit more
[09:50] <mandel> ogra_, small question, I just updated my devices and they do not longer boot, have you guys seen that?
[09:51] <mandel> ogra_, it was via system image updates (not ubuntu-device-flash)
[09:51] <ogra_> mandel, yes
[09:51] <ogra_> investigating (see a few lines above)
[09:51] <mandel> ogra_, any pointers on how to fix it?
[09:51] <ogra_> well, or trying to
[09:51] <ogra_> while sivaa can get in via adb in the lab, i cant hre
[09:52] <ogra_> mandel, ubuntu-device-flash ... and use the --revision option
[09:52] <ogra_> to go back to 251
[09:53] <mandel> ogra_, Device initctl: unable to determine sessions
[09:53] <ogra_> mandel, thats fine, since there is no session running :)
[09:54] <ogra_> why the heck does everyone else get in and i dont !
[09:56] <mandel> ogra_, same as why I got the maps working ;)
[09:56] <ogra_> golden hands ?
[09:57] <mandel> ogra_, no, we are just too good looking to have broken software
[09:59]  * ogra_ is stroking his fingers through his hair ...
[09:59] <ogra_> hmm ... that might be true
[09:59] <ogra_> :)
[09:59]  * sil2100 wonders why media-hub doesn't want to migrate
[09:59] <ogra_> deps ?
[10:00] <sil2100> All are pushed, both qtubuntu-media and media-hub are in -proposed as valid candidates
[10:00] <sil2100> Maybe we just need a publisher run?
[10:01] <Laney> https://launchpad.net/ubuntu-rtm/+source/media-hub/+publishinghistory
[10:01] <Laney> it did
[10:01] <sil2100> Although the update_output.txt does have something strange
[10:01] <Laney> where's proposed-migration for rtm, ooi?
[10:01] <seb128> sil2100, it migrated https://launchpad.net/ubuntu-rtm/+source/media-hub
[10:01] <seb128> Laney, http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/update_output.txt
[10:01] <Laney> oh, I see it
[10:01] <Laney> you can see "accepted: media-hub" there
[10:01] <Laney> that means it did go
[10:03] <davmor2> sil2100: this is a problem https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1370064
[10:06]  * sil2100 sighs
[10:06] <sil2100> davmor2: is that confirmed?
[10:07] <davmor2> sil2100: yeap jibel me and brendand can all reproduce it both ways
[10:07] <davmor2> sil2100: it also happens from all 3rd party, unfavourited scopes too
[10:09] <brendand> davmor2, i'm not sure it should be a blocker. it only happens in that view
[10:09] <brendand> davmor2, and it is recoverable. although it is a regression
[10:09] <davmor2> brendand: no I didn't say blocker I said issue
[10:09] <davmor2> sil2100: add it to user visible
[10:10] <davmor2> sil2100: especially as it seems to be being, worked on already
[10:12] <ogra_> sil2100, bug 1332538 is what breaks 252
[10:12]  * ogra_ tries a fresh flash of 252 to confirm ...
[10:20] <ogra_> ah, wait, the lab uses freshly flashed images
[10:20] <ogra_> so that might just be a coincidence
[10:22] <davmor2> ogra_: 252 on a fresh flash here didn't even start the wizard
[10:23] <ogra_> root@ubuntu-phablet:~# ls -l  /var/lib/|grep lightdm
[10:23] <ogra_> drwxr-x--- 6        111 lxc-dnsmasq     4096 Jun  6 14:12 lightdm
[10:23] <ogra_> well, all lightdm owned bits are now owned by the non existing user with the UID 111
[10:25] <sil2100> ogra_: anyway, can you kick a new image for RTM?
[10:25] <sil2100> :)
[10:25] <sil2100> All should be migrated
[10:25] <sil2100> davmor2: will do!
[10:25] <ogra_> sil2100, oh, the roll-back too ?
[10:27] <davmor2> ogra_: ofcourse I blame developer mode and that oliver bloke, he's always breaking the images for fun......oh wait that's you right ;)
[10:27] <ogra_> :P
[10:28] <ogra_> davmor2, can you get in anyhow ?
[10:29] <ogra_> (flashing will still take ~30min for me)
[10:30] <davmor2> ogra_: having a look give me 2 seconds
[10:30] <ogra_> thx
[10:31] <ogra_> davmor2, oh, and did you flash with --wipe ? (or --bootstrap)
[10:32] <davmor2> ogra_: bootstrap
[10:32] <ogra_> k, that should definitely get you a virgin system with the right UIDs
[10:33] <davmor2> ogra_: bugger forgot to enable developer-mode reflashing back in about 10 minutes
[10:33] <ogra_> ah, crap
[10:34] <davmor2> ogra_: won't be a minute only need to flash the image is on my system
[10:35] <oSoMoN> sil2100, Mirv: can silo 17 (utopic) be published?
[10:36] <davmor2> ogra_: I blame Mirv's lack of cats jinxing the day ;)
[10:36] <ogra_> haha, yeah
[10:36] <ogra_> sil2100, image triggered
[10:37] <sil2100> \o/
[10:37] <sil2100> oSoMoN: let me take a look
[10:38] <ogra_> sil2100, so all roll backs are in ?
[10:38]  * ogra_ thought he'd need to dput dbus-cpp still
[10:38] <sil2100> ogra_: oh, you didn't do that yet ;p?
[10:38] <ogra_> no
[10:38] <sil2100> I thought you did
[10:39] <sil2100> Please push, it didn't require anything else, it just had some isolated bugfix
[10:39] <ogra_> sil2100, hmm, k, did you re-pack already ?
[10:39] <Mirv> sorry about that :(
[10:42] <ogra_> sil2100, the dbus-cpp package still says "utopic"
[10:45] <imgbot> [10:48] <davmor2> ogra_: right I'm back with an adb-able system what do you want me to try?
[10:48] <sil2100> Ah, I thought you would re-pack ;) Ok, let me do that
[10:49] <sil2100> ogra_: uploaded to the same place
[10:49] <ogra_> sil2100, thanks
[10:50] <ogra_> davmor2, well, not sure, check syslog or so :)
[10:55] <Mirv> ogra_: so is that #57 going to be alright regardless of dbus-cpp?
[10:55] <ogra_> Mirv, no idea
[10:56] <Mirv> hmm
[10:58] <ogra_> sil2100, uploaded
[10:58] <ogra_> i doubt it will make thhis image buuild though
[11:00] <davmor2> ogra_: I see a bunch of issues http://paste.ubuntu.com/8409857/
[11:01] <ogra_> davmor2, i dont ... well, at least not the root cause
[11:01] <ogra_> i see that lightdm restarts over and over
[11:01] <ogra_> but tthats something we know already
[11:03] <davmor2> ogra_: I guess it is linked to the issue as lightdm is never displayed.
[11:03] <ogra_> sure
[11:03] <ogra_> the prob is that we dont know why
[11:04] <davmor2> ogra_: let me check my working rtm image against it and see what we cet from that
[11:04] <ogra_> i see mtp-server crashing like crazy
[11:05] <ogra_> and apport is collecting something new
[11:05] <davmor2> ogra_: no crash report though
[11:06] <davmor2> ogra_: there is nothing in /var/crash at least
[11:06] <ogra_> right
[11:06] <ogra_> i stopped it here
[11:07] <davmor2> ogra_: does it matter that userdata is owned by root on rtm and system on utopic?
[11:07] <sil2100> ogra_: thanks!
[11:08] <ogra_> davmor2, it shouldnt
[11:09] <ogra_> davmor2, is that on the same device ?
[11:09] <ogra_> note that krillin is indeed different (using native partitions)
[11:09] <davmor2> ogra_: no krillin for rtm, mako for utopic
[11:10] <ogra_> right
[11:12] <dholbach> what are the ffe/release rules for touch?
[11:13] <dholbach> I'm asking because of https://launchpad.net/bugs/1352142
[11:14]  * ogra_ disables apparmor ... lets see
[11:14] <ogra_> dholbach, we dont have ffe's
[11:14] <Laney> there's a standing exception
[11:14] <Laney> bug #1371635
[11:16] <ogra_> Laney, well, who cares... its a meta update anyway
[11:16] <Laney> in this case, but the general statement wasn't accurate
[11:20] <ogra_> we dont have FFes in RTM i should have said :)
[11:22] <ogra_> http://paste.ubuntu.com/8410032/
[11:22] <ogra_> hmpf
[11:22] <davmor2> ogra_: http://paste.ubuntu.com/8410033/
[11:22] <ogra_> davmor2, yeah, i'm one step further already :)
[11:23] <davmor2> ogra_: I'm just look through everything in /var/log currently. I'll keep pasting though then it gives you a confirmation on what you are seeing :)
[11:24] <ogra_> uh, oh
[11:24] <ogra_> new android ?
[11:24] <ogra_> hmm
[11:25] <ogra_> but a trivial change that shouldnt do any harm
[11:25] <davmor2> ogra_: http://paste.ubuntu.com/8410071/
[11:25] <ogra_> right
[11:26] <davmor2> ogra_: were there any lxc changes?
[11:26] <ogra_> no
[11:27] <davmor2> ogra_: http://paste.ubuntu.com/8410083/
[11:27] <ogra_> there was a new device traball, but only a one line change to a script in there
[11:28] <davmor2> ogra_: there is nothing in the android.log in the same dir
[11:28] <ogra_> thats fine
[11:28] <ogra_> sudo lxc-info -nandroid 2>/dev/null
[11:28] <ogra_> check that
[11:29] <ogra_> or: ps ax|grep " /init"|grep -v grep
[11:30] <ogra_> oh
[11:30] <ogra_> phablet@ubuntu-phablet:~$ /system/bin/logcat -d
[11:30] <ogra_> phablet@ubuntu-phablet:~$
[11:30] <ogra_> no logging in the container
[11:31] <davmor2> ogra_: hmm didn't the cgroup stuff land again?
[11:31] <ogra_> nope
[11:32] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/252.changes
[11:32] <ogra_> there we go
[11:33] <ogra_> http://paste.ubuntu.com/8410114/
[11:33] <ogra_> rsalveti, ^^
[11:33] <ogra_> rsalveti, looks like your last android upload broke the display drivers
[11:33] <ogra_> davmor2, you dont happen it have a krillin where you could cross check utopic on ?
[11:36] <Mirv> cgroup landed in utopic afaik, but not in rtm (there's a line for rtm landing to be done later)
[11:37] <Mirv> sil2100: how about that mir landing now, or will it be postponed until the image after the currently building one too?
[11:38] <ogra_> Mirv, right, but not in 252
[11:38] <Mirv> yeah, it's old news already
[11:38] <davmor2> ogra_: I thought cgroups had landed in utopic :)  I can check after Lunch which has just been called
[11:39] <ogra_> davmor2, right, but i dont think it is relevant for our issue
[11:39] <ogra_> ricmm, do you have an idea why we would get http://paste.ubuntu.com/8410114/  ?
[11:40] <ogra_> the android rebuild should only have a single line change (dropping the forced adbd start from init.rc)
[11:40] <ogra_> but it seems like we got additional issues with it
[11:42] <sil2100> Mirv: this image *should* be ok, so I think we can land Mir
[11:43] <ogra_> http://launchpadlibrarian.net/185512365/android_20140902-2009-0ubuntu3_20140922-1903-0ubuntu1.diff.gz
[11:43] <ogra_> hmm
[11:43] <ogra_> lots more than just the init.rc change
[11:44] <ogra_> sil2100, si i guess our issue lies somewhere inside that diff above
[11:44] <ogra_> which makes the driver die with: E/qdmemalloc( 9259): unrecognized pixel format: 0x0
[11:44] <ogra_> http://paste.ubuntu.com/8410114/
[11:47] <cwayne> brendand ping
[11:48] <ogra_> davmor2, could you try to downgrade (re-flash or however) to http://system-image.ubuntu.com/pool/device-e7561895515ac25e5747711c7b6e947ba39238b874b798290138304c639dbb94.tar.xz with 252 ?
[11:49] <brendand> cwayne, hey - about silo 008 right?
[11:49] <cwayne> brendand yea, just saw your comment on trello
[11:51] <brendand> cwayne, that test doesn't work for me
[11:51] <cwayne> brendand: did you flash 14.09-proposed-customized on a krillin?  i forgot to mention it had to be a krillin..
[11:51] <brendand> cwayne, ah - customized is a special image
[11:52] <brendand> cwayne, missed that part. ok i'll reflash and try again
[11:52] <cwayne> brendand: that's step 1!
[11:52] <cwayne> :)
[11:53] <brendand> cwayne, well it's *part* of step 1 :)
[11:53] <brendand> cwayne, anyway my bad. shouldn't take long to redo it
[11:55]  * ogra_ twiddles thumbs waiting for 252 to re-flash with the 251 device tarball
[11:55] <imgbot> [11:55] <imgbot> [11:55] <Mirv> sil2100: ok then, thanks for confirming
[11:57] <ogra_> pete-woods, are you fixing the build errors in silo 007 at some point ? it is blocking a critical bugfix that needs to land before thu
[11:57] <ogra_> (ubuntu 007 that is)
[11:59] <ogra_> sigh ... k rolling back the device tarball doesnt seem to help :(
[12:00] <ricmm> ogra_: hey
[12:00] <ogra_> yo
[12:00] <ricmm> whats the issue?
[12:00]  * ricmm looks
[12:00] <pete-woods> ogra_: I will reconfigure the silo with only the critical
[12:00] <ogra_> ricmm, 252 doesnt boot anymore
[12:00]  * ogra_ hugs pete-woods
[12:00] <ricmm> thats nice
[12:00] <pete-woods> :)
[12:00] <ricmm> is that on N4 ?
[12:00] <pete-woods> ricmm: yep
[12:01] <ogra_> ricmm, yeah ... i see lightdm respawn like crazy and u-s-c dies
[12:01] <ricmm> well the E/qdmemalloc( 9259): unrecognized pixel format: 0x0 looks wrong
[12:01] <ricmm> maybe a Mir landing?
[12:01] <ogra_> right
[12:01] <ogra_> nope
[12:01] <ricmm> that changes pixel formats
[12:01] <ogra_> we only had apparmor and gstreamer
[12:01] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/252.changes
[12:01] <pete-woods> trainguards: hi. can I please get silo 007 reconfigured? (https://ci-train.ubuntu.com/job/ubuntu-landing-007-0-reconfigure/build?delay=0sec) thanks!
[12:01] <ricmm> do you have a logcat diff from 251 ?
[12:02] <ogra_> not really ... and flashing 251 takes me another hours over my slow line
[12:02]  * ogra_ waits for davmor2 to return from lunch ... he is faster in testing/flashing
[12:02] <ricmm> ogra_: :)
[12:03] <ricmm> this is agood excuse to charge my mako
[12:03]  * ricmm plugs it to the 2A adap
[12:03] <ogra_> ricmm, but i rolled back to the 251 device tarball ... which i would have expected to help :/
[12:03] <ogra_> http://launchpadlibrarian.net/185512365/android_20140902-2009-0ubuntu3_20140922-1903-0ubuntu1.diff.gz has the android changes
[12:03] <ogra_> seemingly papi changed as well as hybris
[12:04] <ogra_> (along with the two line change that was the actual reason for the upload)
[12:04] <ogra_> +libhybris (0.1.0+git20131207+e452e83-0ubuntu27) utopic; urgency=medium
[12:04] <ogra_> +
[12:04] <ogra_> +  * debian/rules: using hardening=-stackprotectorstrong as that's not
[12:04] <ogra_> +    supported with gcc 4.7
[12:04] <ogra_> that looked suspicious
[12:04] <ogra_> (but then ... i cant boot with the tarball rolled back)
[12:07] <ogra_> ricmm, oh, and http://paste.ubuntu.com/8410032/ might be interesting too
[12:07] <ricmm> well yea
[12:07] <ricmm> thats the other side of the logcat error
[12:07] <ricmm> its failing to allocate due to the wrong pixelformat
[12:07] <ogra_> hmm, so my hand-rolled-back device tarball doesnnt even get the container up
[12:07] <ricmm> what I dont understand is where the wrong pixel format is coming from
[12:07] <cjwatson> hardening=-stackprotectorstrong doesn't look especially suspicious; that amounts to "keep building as before with new dpkg-dev"
[12:08] <ogra_> cjwatson, well, not sure how the armv6 android build copes with that :)
[12:08] <cjwatson> ogra_: err, what?
[12:09] <ogra_> the android container is armel ...
[12:09] <ogra_> and v6
[12:09] <cjwatson> ogra_: this *disables* stack-protector-strong (new in gcc-4.9), so that it can be built with older toolchains
[12:09] <ogra_> it just pulls in the hybris binaries during build
[12:09] <ricmm> it should have no impact, thats fine
[12:09] <cjwatson> ogra_: the effect of hardening=-stackprotectorstrong is to go back to the compiler flags used by default with previous versions of dpkg-dev
[12:09] <ricmm> ogra_: what about some permissions change on gralloc?
[12:09] <ricmm> and/or apparmor rules for it
[12:10] <ricmm> dev/gralloc
[12:10] <ogra_> ricmm, well, we have a new apparmor in that change set
[12:10] <ricmm> can you try and role back those rules
[12:10] <cjwatson> ogra_: without that change the armv6 build would certainly fail!
[12:10] <ogra_> well, first i need a working device again
[12:10] <ogra_> cjwatson, right, but if it not fails, do we know what other defaults are there that could harm us ?
[12:11] <cjwatson> ogra_: just diff the build logs
[12:11] <jdstrand> is there anything in /var/log/syslog for apparmor?
[12:11] <cjwatson> rather than trying to guess in advance
[12:11] <jdstrand> also, what branch is this?
[12:11] <jdstrand> utopic or rtm?
[12:12] <ogra_> jdstrand, there is, but only the general session strartup noise when lightdm respawns endlessly
[12:12] <ogra_> jdstrand, utopic
[12:12] <ogra_> 252
[12:12] <ogra_> jdstrand, http://paste.ubuntu.com/8409857/
[12:12] <jdstrand> are you able to adb shell in?
[12:13] <jdstrand> what does /var/log/upstart/apparmor.log say?
[12:14] <ogra_> just re-flashing a completetly bricked install here ...
[12:14] <ogra_> i'll check afterwards
[12:17] <ogra_> cjwatson, oh, btw, do you have any idea why these packages were dropped http://people.canonical.com/~ogra/touch-image-stats/252.changes ? (doesnt look like they could be a dep of any of the changed ones)
[12:18] <ogra_> (and there is no meta upload or seed change either)
[12:18] <davmor2> ogra_: right I'm back flashing krillin now
[12:18] <sil2100> davmor2: ping!
[12:18] <ogra_> davmor2, thanks
[12:18] <davmor2> sil2100: what
[12:18] <jdstrand> so, a) there was only one policy change for desktop that only allowed more access, not less. b) there were changes to the parser to make things more robust in the face of corrupt caches, not less, and, most importantly, c) there were changes to the script the upstart job uses to make things faster for cache loads and, most importantly, d) lightdm is not confined so if its job is started, none of the above should matter
[12:18] <jdstrand> actually, there is only one most importanly, the last one :)
[12:19] <ogra_> jdstrand, right, lightdm start ... u-s-c dies then and lightdm tries to respawn
[12:19] <jdstrand> (yay for rewording as you type)
[12:19] <sil2100> davmor2: so, I know we have utopic issues right now, but could you also take a look promotion-wise on #57 on krillin?
[12:19] <mzanetti> sil2100: silo ubuntu/006 tested
[12:19] <sil2100> RTM
[12:19] <sil2100> mzanetti: excellent, publishing
[12:19] <davmor2> sil2100: after I try this out on krillin yes
[12:20] <cwayne> davmor2: sil2100: btw I might need to request a custom tarball test-pass today/tomorrow if that's ok
[12:20] <sil2100> mzanetti: so, hmm... we don't have a free silo for RTM - let me prepare everything so that we don't forget about the RTM sync
[12:20] <mzanetti> sil2100: one question: So there's still an earlier landing of unity8 which is already in utopic, but not yet in RTM because of a dependency not synced over
[12:21] <sil2100> mzanetti: what dependency needs to get synced?
[12:21] <davmor2> cwayne: aim it for tomorrow looking like chaos today ;)
[12:21] <mzanetti> sil2100: unity7
[12:21] <mzanetti> sil2100: silo rtm/004
[12:21] <sil2100> cwayne: thanks for the info, ETA for that will be tomorrow I guess
[12:22] <mzanetti> sil2100: when that is over, we still have rtm/006 to sync
[12:22] <sil2100> mzanetti: could you poke someone to test unity7 on some RTM device?
[12:22] <sil2100> So that we can land it ASAP
[12:22] <mzanetti> sil2100: and then we need a new one for the stuff we currently have in ubuntu/006
[12:23] <sil2100> mzanetti: and where is the earlier unity8 landing?
[12:23] <mzanetti> rtm/006
[12:24] <mzanetti> hmm... I can't find the row i the spreadsheet any more
[12:25] <mzanetti> sil2100: seems the spreadsheet's row for rtm/006 has disappeared
[12:26] <cjwatson> ogra_: https://launchpad.net/ubuntu/+source/ubuntu-html5-theme/0.1.2+14.10.20140922.1-0ubuntu1
[12:26] <ogra_> cjwatson, WOAH !
[12:26] <mzanetti> sil2100: ah no... row 17
[12:26] <ogra_> thanks !
[12:26] <ogra_> thats unexpected :)
[12:27] <sil2100> mzanetti: ok, then hm, maybe let's wait with publishing silo 006 then
[12:27] <mzanetti> sil2100: works for me
[12:27] <sil2100> mzanetti: since I'm afraid that otherwise we'll get confused :)
[12:27] <mzanetti> sil2100: I think bregma will release unity7 soon. hopefully today
[12:27] <cjwatson> ogra_: are you suspecting an undeclared dependency on binutils or something?
[12:28] <cjwatson> I doubt dpkg-dev itself is part of anyone's boot chain :)
[12:28] <davmor2> ogra_: right I'm flashed just waiting to see if it boots, not holding my breath on that one though ;)
[12:28] <ogra_> cjwatson, no, i was just wondering why they are dropped at all ... and having a package depend on dpkg-dev feels so wrong :)
[12:28] <cjwatson> well indeed
[12:28] <davmor2> ogra_: what do you want me to check?
[12:28] <bregma> mzanetti, the Unity 7 sync was waiting for an RTM silo last I heard
[12:29] <ricmm> bear in mind that the pixel format is for some reason 0, that means the pf it tried to alocate with was either *wrong* or was made 0 when going over hybris
[12:29] <ogra_> davmor2, well, actually only if it behaves any different to mako ... since they have different device tarballs
[12:29] <ricmm> is it possible that the hybris flag is doing more than we think it is?
[12:29] <mzanetti> bregma: I think its ready to be tested here: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-004
[12:29] <ogra_> davmor2, to rule out the android side
[12:29] <ogra_> ricmm, that was my suspicion ...
[12:30] <ogra_> jdstrand, Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd ... only that in /var/log/upstart/apparmor.log (for each lightdm respawning it seems)
[12:30] <bregma> hmm, does not show up in my ci-trani dash,
[12:30] <ogra_> ricmm, but OTOH cjwatson sounded like i would be on the wrong track
[12:31] <bregma> mzanetti, can you possibly test the Unity 7 sync?  I do not have a device
[12:31] <cjwatson> ogra_: did you diff build logs?
[12:31] <ogra_> cjwatson, not yet
[12:31] <mzanetti> bregma: sure. is there anything I need to test in special?
[12:31] <cjwatson> that should be the next step if you have any suspicions at all in this direction
[12:32] <mzanetti> bregma: like a certain test plan, or things known to be fragile on unity7 landings?
[12:32] <bregma> mzanetti, the only thing that counts is the schema
[12:32] <cjwatson> argh, except that libhybris does not have verbose build logs!
[12:32] <bregma> nothing else is actually used
[12:32] <mzanetti> ok, there isn't much chance of breaking something else then
[12:32] <mzanetti> bregma: ack. will execute unity8's test plan on it
[12:32] <bregma> mzanetti, easiest test you will ever do
[12:32] <mzanetti> :)
[12:33] <jdstrand> ogra_: yep, that is normal
[12:33] <ogra_> right, thought so
[12:33] <cjwatson> how's it managing that?  it uses autoconf and automake ...
[12:33]  * sil2100 goes for lunch
[12:34] <jdstrand> one day, we should turn on the rsyslog profile by default, but not today
[12:34] <cjwatson> (and launchpad-buildd exports V=1 which should cause all such builds to be verbose)
[12:36] <cjwatson> ricmm,ogra_: anyway, hardening=-stackprotectorstrong has the effect of reverting to the basic stackprotector feature, i.e. -fstack-protector --param=ssp-buffer-size=4.  If you weren't doing anything special before then AFAIK that's what you got with older versions of dpkg-dev.
[12:37] <cjwatson> I've just checked the code and it does nothing else.
[12:38] <ogra_> cjwatson, right, but it indicates that the general defaults changed in 4.9 ...
[12:38] <ogra_> perhaps hardening=-stackprotectorstrong isnt enough
[12:38] <cjwatson> Not in 4.9
[12:38] <cjwatson> GCC 4.9 introduced the -fstack-protector-strong option, which dpkg-dev (separately) started using.
[12:39] <cjwatson> This wasn't a change in defaults in GCC 4.9.
[12:39] <ogra_> ok
[12:39] <cjwatson> Anyway, once you get to this kind of discussion, IME you're better off debugging directly ...
[12:39] <cjwatson> Tends to turn into a wild goose chase otherwise.
[12:40] <cjwatson> Also, libhybris isn't actually using GCC 4.9 to build (that being the entire reason it had to use hardening=-stackprotectorstrong in the first place), so any change in defaults in GCC 4.9 would be entirely irrelevant.
[12:41] <ogra_> oh !
[12:41] <cjwatson> Effectively libhybris is just unwinding http://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/scripts/Dpkg/Vendor/Debian.pm?id=f7e10180d3ead4f3187ab48557d8aee3bd85ea4a for itself.
[12:41]  * ogra_ sees a lot of
[12:41] <ogra_> Sep 23 14:41:02 ubuntu-phablet kernel: [  205.556874] init: ubuntu-espoo-service main process (6043) killed by ABRT signal
[12:41] <ogra_> Sep 23 14:41:02 ubuntu-phablet kernel: [  205.556935] init: ubuntu-espoo-service main process ended, respawning
[12:41] <ogra_> and in /var/log/upstart/ubuntu-espoo-service.log there is ...
[12:42] <ogra_> terminate called after throwing an instance of 'std::runtime_error'
[12:42] <ogra_>   what():  org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
[12:42] <ogra_> why would a system service try to start a session dbus ?
[12:44] <ogra_> cjwatson, ricmm, so davmor2 just confirmed that krillin has the issue too ... that rules out android i guess
[12:44] <ogra_> (since on krillin there was no new android build)
[12:45] <sil2100> Mirv: I'll redeploy the binsync now if anything
[12:46] <Mirv> sil2100: ok.
[12:47] <brendand> cwayne, looks fine. why not test cases for the other MMI codes?
[12:47] <brendand> cwayne, that factory reset one is neato
[12:48] <cwayne> brendand: just cause the landing itself is just enabling any, so as long as 1 works, that hook is working correctly
[12:48] <cwayne> plus that was the shortest one :)
[12:50] <cwayne> trainguards can I get an RTM silo for line 73 please :)
[12:57] <ogra_> jdstrand, davmor2, so i rolled back all apparmor changes on 252 ... no change in behavior
[12:58] <jdstrand> ok, thanks, I'm going to step away then
[12:58] <davmor2> ogra_: yay that apparmor ruled out then \o/
[12:59] <ogra_> customization hooks now
[12:59] <davmor2> ogra_: what do the removed packages do?
[12:59] <ogra_> davmor2, they shouldnt have any effect
[12:59] <davmor2> ogra_: binutils in particular
[13:00] <ogra_> lets see, i'll revert one by one now
[13:00] <ogra_> sigh, that espoo service crashing is annoying
[13:00] <ogra_> makes the logs pretty unreadable
[13:03] <ogra_> ok, just for fun i installed dpkg-dev now
[13:03]  * ogra_ reboots
[13:05] <sil2100> Mirv: ok, so as per silo 003 I see the binsync still works ;p
[13:08] <tsdgeos> cprov: do we you know where unity-phablet-qmluitests-utopic runs? is it a VM or the phone?
[13:09] <cprov> tsdgeos: I can find out, but suspect it's a vm
[13:10] <ogra_> hmm
[13:10] <ogra_> so the only thing i havent rolled back yet is gstreamer
[13:10] <tsdgeos> cprov: ok, tx
[13:10] <tsdgeos> cprov: it's so slow some of our 5seconds timed waits are starting to fail :D
[13:10] <ogra_> (and lxc-android-config, but thats already in rtm and didnt break there)
[13:11]  * ogra_ needs a break
[13:11] <ogra_> oh, wow
[13:11] <ogra_> my mako is melting
[13:11] <cprov> tsdgeos: it's a vm
[13:12] <davmor2> ogra_: wow both here
[13:12] <tsdgeos> cprov: ok, thanks i'll try to make it more timing resstant then, tx
[13:12] <cprov> tsdgeos: any idea why its performance is degrading ?
[13:12] <tsdgeos> cprov: sure, we are making it load more things :D
[13:13] <ogra_> ricmm, hmm ... 1101 root      20   0    8244   1624   1224 S  98.8  0.1   4:00.86 Binder_2
[13:13]  * ogra_ doesnt get it
[13:14] <cprov> tsdgeos: well, yeah, but let us know if we can something about it.
[13:14] <tsdgeos> cprov: it's fine know that i realized it's just because the vm is slow i can fix the tests
[13:20] <brendand> jhodapp, silo 14 has been around for almost a week - did you finish testing it yet?
[13:20] <jhodapp> brendand: that's not my landing, that's ycheng's
[13:20] <brendand> jhodapp, is he supposed to test it?
[13:21] <jhodapp> brendand: yeah, he should be...he's new to the silo process though so that's why it's been slow going
[13:22] <brendand> seb128, how about that indicator-transfer landing?
[13:22] <brendand> seb128, silo 10
[13:22] <seb128> brendand: what about it?
[13:22] <seb128> brendand: "make it happen"?
[13:22] <davmor2> sil2100: right flashing rtm now
[13:22] <sil2100> davmor2: \o/
[13:22] <brendand> seb128, has it been tested?
[13:22] <sil2100> davmor2: having fingers crossed
[13:23] <seb128> brendand: it can't be tested, that's a launchpad side thing that is only going to happen once the package is in the distribution
[13:23] <brendand> seb128, ah enable translations. in that case mark it as tested and qa sign off N/A
[13:23] <seb128> brendand: ok
[13:24] <seb128> brendand: done, should I publish it as well?
[13:24] <brendand> seb128, no a member of the landing team will i believe
[13:24] <brendand> sil2100, ^
[13:24] <seb128> well, I can do it
[13:24]  * seb128 clicks
[13:25] <brendand> jdstrand, silo 007 is really old
[13:26] <brendand> mzanetti, how about rtm silo 006?
[13:30] <jdstrand> brendand: yes, I talked to Mirv and robru about it already. I wanted a particular fix before landing. that fix was uploaded to the ppa last night. we don't want to push apparmor without cwayne's landing
[13:30] <brendand> jdstrand, which cwayne landing? the one about MMI codes that just went in, or the next one?
[13:30] <jdstrand> brendand: the one about apparmor caching
[13:30] <cwayne> brendand: the next one
[13:31] <jdstrand> ogra_: you still have trouble with mako?
[13:31] <mzanetti> brendand: still blocked on waiting for rtm silo 004
[13:32] <brendand> mzanetti, we need bregma to do his bit then
[13:32] <mzanetti> brendand: no, I already agreed with bregma that I'll test it for him
[13:33] <mzanetti> brendand: have flashed it just now to my krillin and am starting with the test plan
[13:35] <ogra_> jdstrand, not mako related, but yeah, everyone has a non booting device with 252
[13:35] <jdstrand> ogra_: what kernel does it have?
[13:36] <ogra_> jdstrand, should that matter ?
[13:36] <jdstrand> it is not inconceivable-- apparmor changes landed in the kernels
[13:36] <ogra_> jdstrand, but the new kernels didnt land in the image
[13:36] <jdstrand> ok, good
[13:37] <ogra_> jdstrand, and beyond that krillin still has the same device tarball and kernel from before
[13:37] <ogra_> it must be on the rootfs side
[13:37] <jdstrand> so
[13:37] <jdstrand> if there was a gstreamer change, and you are seeing binder going haywire
[13:37] <ogra_> i have rolled back everything but gstreamer from the 252 change set
[13:38] <ogra_> doing that now
[13:38] <jdstrand> right
[13:38] <jdstrand> ogra_: also curious if you have any apparmor denials
[13:38] <ogra_> none at all
[13:38] <ogra_> i dont get that far :)
[13:38] <jdstrand> gstreamer uploads are notorious for changes things and breaking under the policy
[13:38] <jdstrand> changing*
[13:38] <jdstrand> ah
[13:38] <ogra_> lightdm starts ... apparmor does its normal log spam for session startup, lightdm respawns
[13:39] <sil2100> huh, that would be strange that it would be caused by gstreamer, but I guess that can happen
[13:39] <ogra_> unity-system-compositor dies
[13:39] <jdstrand> weird
[13:39] <ogra_> and on the android side there is a pixelformat error
[13:39] <ogra_> ricmm was looking into that one ... but i havent heard from him yet
[13:40] <ogra_> hmmmm
[13:41] <ogra_> so where does that getreamer stuff even come from ?
[13:41] <ogra_> i dont see a related upload
[13:41] <ogra_> i mean, yes, i see a gstreamer upload but no -plugins-bad
[13:43] <ogra_> ah, oh
[13:43] <ogra_> there it is
[13:45] <ogra_> hmm
[13:45] <ogra_> and the former version of that same package FTBFS
[13:45] <ogra_> (on armhf)
[13:46] <ogra_> so i cant easily roll that back
[13:46] <ogra_> sigh
[13:50] <ogra_> ok, downgraded gstreamer
[13:51] <davmor2> ogra_: roll the whole image back to 251 and add packages instead ;)
[13:51] <mzanetti> brendand: bregma: rtm silo 4 tested.
[13:51] <mzanetti> sil2100: ^
[13:51] <ogra_> davmor2, i fear thats what i will have to do
[13:51] <ogra_> sigh
[13:51] <ogra_> thats stealing my day
[13:52]  * ogra_ had tons of landings and other stuff planned today
[13:52] <bregma> mzanetti, thanks,
[13:53] <ogra_> sigh ... and there goes another hour ... waiting for 251 to download
[13:53]  * sil2100 can't unbrick his krillin
[13:53] <ogra_> sil2100, on utopic ?
[13:53] <sil2100> mzanetti: thanks!
[13:53] <mzanetti> sil2100: flashing 56 and then dist-upgrading worked for me
[13:53] <ogra_> mzanetti, ugh
[13:54] <sil2100> ogra_: no, RTM, I have it broken since some time
[13:54] <ogra_> "dist-upgrading"
[13:54] <mzanetti> ogra_: ?
[13:54] <ogra_> mzanetti, that will only get you wrong results when testing etc
[13:54] <davmor2> sil2100: volume-up+power and then go into fast boot and then bootstrap it :)
[13:55] <sil2100> davmor2: yeah, trying that since 30 minutes - it's not moving
[13:55] <sil2100> davmor2: ubuntu-device-flash mentions that it downloaded the files, probably pushed them to the device and... it stays there doing nothing
[13:57] <mzanetti> ogra_: can you elaborate on that please?
[13:58] <ogra_> mzanetti, dist-upgrade might leave stuff around that you wouldnt have when doeing a s-i upgrade
[13:58] <ogra_> migrations might not happen as they do in s-i etc
[13:58] <mzanetti> hmm... interesting. can you give an example so I fully understand it
[14:00] <ogra_> mzanetti, not of the top of my head ... but we had issues before where things behaved different
[14:01] <ogra_> apt is fine for devel devices on which you dont test ... but for testing i wouldnt even make the image writable (and instead just remount,rw / for the time where i use *dpkg* for installing the packages ... and immediately make it ro again)
[14:03] <barry> trainguards: looks like line 47 in the spreadsheet is a dupe, or a left over from landing in utopic.  line 46 is rtm and is currently getting cleaned.  should i just delete row 47, or is there some better way of cleaning that dupe up?
[14:04] <sil2100> barry: hey, you can just delete the row
[14:04] <barry> sil2100: cool, thanks
[14:04] <sil2100> brendand, davmor2: do you guys want a QA sign-off on the unity7 rtm landing?
[14:04] <lool> trainguards, I have an emergency fix to land
[14:05] <ricmm> ogra_: any luck?
[14:05] <ricmm> was having lunch
[14:05] <lool> this is related to a broken landing from friday
[14:05] <sil2100> brendand, davmor2: your call here, since I don't know how much of unity7 is used in our touch images - it was set to not requiring QA sign-off
[14:05] <sil2100> lool: oh? What do you need to land and where?
[14:05] <ogra_> ricmm, nope, i rolled back all packages but had no change
[14:05] <ogra_> ricmm, trying the other way round now and will use 251 and install them one by one
[14:05] <ricmm> weird
[14:05] <lool> sil2100: utopic-proposed has a broken espoo-service since firday evening due to an erroenous silo publishing
[14:06] <ogra_> ricmm, and krillin (which had no android update at all) exposes it too, so i think we can safely rule out android anyway
[14:06] <lool> sil2100: basically comment said not to publish but it was published; it wasn't my silo but tvoss'; I published the corresponding custom tarball dependency back then, but I didn't update a config file in ubuntu-location-provider-here
[14:06] <lool> so it respawns like crazy
[14:06] <sil2100> Argh
[14:06] <lool> I hadn't noticed because I had it changed locally and hadn't reflashed (only upgraded)
[14:06] <lool> sil2100: it should just be utopic-proposed though
[14:06] <sil2100> lool: ok, but it only got into utopic, right?
[14:07] <sil2100> lool: let me see if we have a silo
[14:07] <ogra_> ricmm, since we knoe the last gstreamer breaks unity8 tests (makes them hang hard) ... i start to suspect one of Laney's last gstreamer changes to be involved somehow
[14:07] <lool> problem is that with some code consolidation, we now need to pass --bus system to espoo-service , otherwise it looks for a session bus and fails
[14:07] <lool> sil2100: yes, utopic only for now
[14:07] <lool> eventually this will all migrate to rtm, but in due time
[14:07] <ricmm> ogra_: canyou get a logcat with 251
[14:07] <ricmm> see ifthe pixel format 0x0 message is still there
[14:07] <ogra_> ricmm, from inside the container, yes
[14:07] <sil2100> lool: ok, we have a silo for that then, do you have a landing row in the spreadsheet with the merge fix?
[14:07] <ricmm> with a working 251 I mean
[14:08] <ogra_> ricmm, where would it go ? ... why would it be not there
[14:08] <ogra_> ah
[14:08] <ogra_> yeah, will check
[14:08] <lool> sil2100: no, I need to prepare it now
[14:08] <ogra_> flashing over my 2MBit like is just time consuming
[14:08] <sil2100> lool: ok, we'll have one silo free for you then, just ping me once it's ready :)
[14:08] <ogra_> still downloading ...
[14:08] <ricmm> ogra_: you should get satellite or something
[14:08] <ogra_> ricmm, i was pondering that
[14:08] <ricmm> there are some european providers that push up to 20 mbit
[14:08] <ricmm> iirc
[14:08] <davmor2> sil2100: I didn't even know the 2 were compatible :)
[14:08] <ricmm> or 30
[14:08] <ogra_> there is a pretty cheap offer
[14:08] <ogra_> yeah
[14:09] <ogra_> astra just started a cheap product
[14:09] <ricmm> right
[14:09] <sil2100> davmor2: what do you mean? Which two?
[14:09] <sil2100> davmor2: ah
[14:09] <sil2100> davmor2: this
[14:09] <sil2100> davmor2: so there are some bits that are shared
[14:09] <davmor2> sil2100: unity7 unity8
[14:10] <sil2100> davmor2: I think some schema files or something
[14:10] <ricmm> ogra_: 35 EUR
[14:10] <davmor2> brendand: what do you think ^
[14:10] <ricmm> pretty cheap!
[14:10] <sil2100> davmor2: and an unity8 landing that's in the rtm queue needs this new unity7 files
[14:10] <ogra_> yep
[14:10] <ogra_> ricmm, but unusable for hangouts ;)
[14:10] <ogra_> to much latency
[14:10] <ricmm> well, you can keep the dsl for that
[14:11] <ricmm> :)
[14:11] <ogra_> so it would only serve as a second
[14:11] <ogra_> and is weather depending ...
[14:11] <ogra_> (i have an 1.20m dish for TV ... and even that goes down in heavy rain)
[14:12] <ricmm> still, for 20mbit for whenit really matters... its worth it
[14:12] <ricmm> just get it and stop complaining
[14:12] <ricmm> tell mike to pay it
[14:12] <ricmm> ;)
[14:12] <ogra_> haha
[14:13] <ogra_> and my new tesla too !!11
[14:13] <ricmm> :)
[14:13]  * ogra_ twiddles thumbs watching the ubuntu logo rotate in recovery
[14:13] <ogra_> so hypnotic
[14:15] <ogra_> ... and never ending ...
[14:15] <ogra_> *yawn*
[14:16] <lool> sil2100: row 76
[14:16] <ogra_> oh, rebooting \o/
[14:16] <ogra_> aaand ... i have a spinner
[14:16] <ogra_> looks good
[14:17] <sil2100> lool: ACK
[14:18] <ricmm> ogra_: great, get the logcat and lets see if the msg is there
[14:18] <ogra_> one sec
[14:18] <ricmm> just in case, to not chase red herrings :)
[14:19] <ogra_> ricmm, well, logcat is full of compaints by mpdecision ... no graphics driver messages at all
[14:20] <sil2100> lool: o/
[14:20] <ogra_> so if it was there it scrolled out of the rinbuffer
[14:20] <lool> thanks
[14:21] <ricmm> ok
[14:21]  * ogra_ starts with upgrading the gstreamer plugins now
[14:22]  * ogra_ reboots and crosses fingers
[14:22] <ogra_> bah
[14:22] <ogra_> spinner ...
[14:23] <ogra_> now apparmor
[14:29] <ricmm> ogra_: ?
[14:29] <ogra_> ricmm, gstreamer didnt cause it ...
[14:29] <ogra_> waiting for apparmor upgrade to finish
[14:30] <ogra_> Setting up apparmor-easyprof-ubuntu (1.2.26) ...
[14:30] <ogra_> (may take a while)
[14:30] <ogra_> ... and it doesnt lie :)
[14:32] <ycheng> help needed to publis ubuntu-rtm landing-014
[14:33] <sil2100> davmor2: how's testing RTM going?
[14:34] <davmor2> sil2100: slowly
[14:34] <sil2100> davmor2: any big things so far?
[14:35] <davmor2> sil2100: not yet but there are a lot of tests left
[14:37] <ogra_> finally apparmor upgrade is done ...
[14:37] <ogra_> rebooting
[14:37] <davmor2> sil2100, dbarth_: issue number one.  Added twitter account and I'm still waiting for the Accounts page to finish loading, stab online accounts repeatedly to see if that helps
[14:38] <ogra_> sigh, ok
[14:38] <ricmm> ??
[14:38] <ogra_> no breakage with apparmor upgraded either
[14:38] <ricmm> mm
[14:38] <ogra_> i dont get tthat
[14:39] <ycheng> fginther: help need to publish ubuntu-rtm/landing-014
[14:40] <ogra_> customization hooks dont break it either
[14:40] <fginther> ycheng, publishing and landings are performed by the trainguards. trainguards, please see ycheng's request ^
[14:42] <ricmm> ogra_: did you fire a 253 just to check?
[14:42] <ricmm> maybe the build did something funny
[14:42] <davmor2> ogra_: remove binutils I still think it is the removed stuff that is breaking the universe, just cause it isn't meant to doesn't mean it isn't :)
[14:42] <ricmm> like that one time the order of installs broke Mir
[14:43] <ogra_> davmor2, binutils would only harm you if you compile something
[14:43] <cjwatson> davmor2: which is all well and good to say but we would need to know why
[14:43] <ogra_> (and any of the other stuff as well ... or if you want to handle packaging)
[14:43] <ycheng> trainguards, help need to publish ubuntu-rtm/landing-014
[14:43] <ogra_> but for your entertainment, i just upgraded the html5 stuff and removed them all
[14:43] <ogra_> lets see ... rebooting
[14:44] <ogra_> aaaand ... there is the spinner
[14:44] <ogra_> so i replaced everything but lxc-android-config
[14:44] <ogra_> (which is already in rtm and doesnt break anything there)
[14:44] <ogra_> SIGH !
[14:44] <ogra_> what a wasted day
[14:45] <ricmm> so again
[14:45] <ricmm> wheres the build diff of the image
[14:45] <ycheng> fginther: should there be a irc nick call trainguards ? it's not there !?
[14:45] <ogra_> ricmm, "build" diff ?
[14:45] <sil2100> ycheng: trainguards is an ailas all trainguards are being pinged on
[14:46] <davmor2> ycheng: it's a trigger for the people on guard
[14:46] <sil2100> ycheng: what's up? :)
[14:46] <ogra_> ricmm, http://people.canonical.com/~ogra/touch-image-stats/252.changes is all i can give you
[14:46] <ricmm> ogra_: is there a logfor theactual image build?
[14:46] <ricmm> I remember we saw one once when the order of packages affected the Mir alternatives
[14:46] <ogra_> sure, but how would that help you ?
[14:46] <ycheng> sil2100: help need to publish ubuntu-rtm/landing-014
[14:46] <fginther> ycheng, no, there is no irc nick for that, it's just used as an IRC marker
[14:46] <davmor2> ycheng: the camera app hasn't been marked as tested by the dev so qa won't look at it till it is
[14:46] <ogra_> ricmm, i thought that was fixed via hardcoding
[14:47] <ricmm> yea, but there might be other stuff we dont know about
[14:47] <ricmm> just an idea, considering you already exhausted bi-directional bisecting of the packages...
[14:47] <ogra_> ricmm, https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/utopic/ubuntu-touch/
[14:47] <sil2100> ycheng: what's wrong? Let me take a look
[14:48] <ycheng> sil2100: mark in colume K ? sorry it's my first time to....
[14:48] <ycheng> sil2100: line 33
[14:50] <sil2100> ycheng: ok, do you have write access to the spreadsheet?
[14:50] <ycheng> sil2100: negative
[14:50] <ricmm> ogra_: I think its there
[14:50] <ricmm> check the last working image
[14:50] <ricmm> there is a /root/80-enable-libhybris.chroot: 3: /root/80-enable-libhybris.chroot: dpkg-architecture: not found running here
[14:50] <ricmm> I: making libhybris the default alternatives for _egl_conf
[14:50] <ricmm> update-alternatives: error: no alternatives for _egl_conf
[14:51] <ricmm> whereas the working one has:
[14:51] <ricmm> I: making libhybris the default alternatives for arm-linux-gnueabihf_egl_conf
[14:51] <ricmm> update-alternatives: using /usr/lib/arm-linux-gnueabihf/libhybris-egl/ld.so.conf to provide /etc/ld.so.conf.d/arm-linux-gnueabihf_EGL.conf (arm-linux-gnueabihf_egl_conf) in manual mode
[14:51] <ricmm> whats 80-enable-libhybris.chroot ?
[14:51] <ogra_> /root/80-enable-libhybris.chroot: 3: /root/80-enable-libhybris.chroot: dpkg-architecture: not found
[14:51] <ogra_> I: making libhybris the default alternatives for _egl_conf
[14:51] <ogra_> update-alternatives: error: no alternatives for _egl_conf
[14:51] <ogra_> bah
[14:51] <ricmm> you are too slow
[14:51] <ogra_> you beat me
[14:51] <ricmm> lol
[14:51] <ogra_> heh
[14:51] <ricmm> better to keepthe DSL
[14:51] <sil2100> ycheng: ok, let me give that to you then - but I'll anyway mark it as ready for you
[14:51] <ricmm> otherwise youwill beslower
[14:51] <ricmm> !
[14:51] <ogra_> lol
[14:51] <ricmm> my keyboard is dying on me
[14:51] <sil2100> ycheng: what image did you test it on?
[14:52] <ycheng> sil2100: rtm image installed about 8 hours ago
[14:52] <cjwatson> oho.  dpkg-architecture is absolutely the wrong thing to use there
[14:52] <ricmm> so yes, this could point to Mir trying to use the wrong EGL impl to decide the available pixel formats
[14:52] <ycheng> sil2100: I leave the phone in the office and now I am home
[14:52] <ricmm> and then pushing aninvalid value to gralloc
[14:52] <cjwatson> that should be dpkg --print-architecture, probably
[14:52] <cjwatson> actually no
[14:53] <cjwatson> livecd-rootfs should be calculating DEB_HOST_MULTIARCH at build time and substituting it into those scripts
[14:53] <ycheng> sil2100: does this channel works 24hours ? in such case I can work tomorrow day time. (I am +8)
[14:54] <cjwatson> ogra_: want me to fix this?
[14:54] <ogra_> cjwatson, yes please
[14:54] <ogra_> though i'd like to know why it starts to cause issues all of a sudden
[14:54] <sil2100> ycheng: yeah, but now worries, I'll take care of it after my meeting now
[14:54] <ricmm> its just failing to parse the arch I guess
[14:54] <ricmm> ogra_: well it wasnt running before
[14:54] <cjwatson> ogra_: because dpkg-architecture is a build-time tool, and is in dpkg-dev
[14:54] <cjwatson> which is no longer in the image
[14:54] <ricmm> ohhh
[14:54] <ricmm> go figure
[14:54] <ycheng> sil2100: thanks
[14:55] <ogra_> oh !
[14:55] <ogra_> lovely !
[14:55]  * ogra_ puts all the blame on slangasek then
[14:55] <ogra_> :D
[14:55] <dbarth_> davmor2: is that new? network issues? which image?
[14:55] <slangasek> it wasn't my fault that someone was using it without a declared dependency ;)
[14:56] <ogra_> yeah, i wasnt serious :)
[14:56] <ogra_> thanks for revealing the bug :)
[14:57] <sil2100> hah
[14:58] <cjwatson> ogra_: is there an open bug for all this which I should close?
[14:58] <ogra_> nope
[14:58] <cjwatson> ok
[14:59] <sil2100> ogra_: me and slangasek were just discussing the ubuntu-html5-theme landing that's related ;)
[15:00] <ogra_> heh
[15:01] <slangasek> yes, I was just discussing how to break the rtm image too!
[15:01] <slangasek> er, I mean get it landed
[15:01] <ogra_> haha
[15:06] <davmor2> dbarth_: latest rtm on krillin, no idea everything seemed to work as expected but it wouldn't return to accounts.  in the end the phone timed out and the account was never created, worked fine the second time though
[15:07] <davmor2> dbarth_: image 57
[15:12] <slangasek> sil2100: I'm getting strange failed-build mails from some of the silos; not packages that I've uploaded, and it doesn't seem like I'm receiving enough of them to account for all the package build failures in all silos (or maybe it is?) - do you know why this is?
[15:13] <slangasek> sil2100: maybe I'm actually receiving notifications for all build failures in all silos...
[15:13] <ogra_> you should
[15:13] <ogra_> we all do
[15:14] <ogra_> (you will learn to love tvoss for (ab)using silos for test builds :P )
[15:14] <jhodapp> sil2100, what happened here? https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-011-1-build/32/console
[15:15] <sil2100> slangasek: hm, not sure, but maybe indeed you are receiving all the FTBFS e-mails then
[15:15] <sil2100> jhodapp: let me look
[15:15] <seb128> sil2100, do you understand the issue with http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-010 ?
[15:15] <sil2100> jhodapp: ugh
[15:15] <slangasek> sil2100: right, ogra_ says we receive them all... I guess people are generally better than expected about making sure their software is buildable before it goes to silo :-)
[15:15] <slangasek> and I'll filter off these mails - thanks
[15:16] <sil2100> seb128: ah, ok, so this was a bug that snuck into CI Train that got fixed, but packages that got built in previously have this problem... all that's needed to fix that is a watch_only build and re-publish
[15:17] <seb128> sil2100, can you do that?
[15:17] <sil2100> jhodapp: ok, now THIS looks broken, but it looks like something happened in the jenkins machine
[15:17] <sil2100> seb128: sure :)
[15:17] <seb128> sil2100, thanks
[15:17] <sil2100> No worries, clicking and publishing
[15:18] <sil2100> davmor2: progress report please!
[15:18] <ogra_> progress is going forward
[15:18] <sil2100> Good news then
[15:18] <sil2100> Better forward than backward
[15:18] <ogra_> that would be regress :)
[15:18] <jhodapp> sil2100, Jenkins passed it for the CI build...why did it fail on the rtm branch?
[15:20] <cjwatson> ogra_,ricmm,davmor2: https://launchpad.net/ubuntu/+source/livecd-rootfs/2.244
[15:20] <sil2100> jhodapp: I guess there might have been something singular, let's rebuild
[15:20] <jhodapp> ok
[15:20]  * ogra_ hugs cjwatson
[15:20] <ricmm> cjwatson: awesome, thanks
[15:21] <sil2100> jhodapp: because this log just shows that there was something completely broken, with the log file showing corrupted stuff
[15:21] <ricmm> ogra_: fire off another one!
[15:21] <ogra_> ricmm, needs to land first
[15:21] <sil2100> cjwatson: thanks :)
[15:21] <ricmm> ogra_: dput
[15:21] <dbarth_> davmor2: it feels like a network issue, but i'll try cutting network in the middle to reproduce
[15:21] <ogra_> ricmm, 1h or so
[15:21]  * sil2100 waits for it to migrate
[15:21] <ricmm> scp to the archive machines
[15:21] <ricmm> release
[15:21] <ogra_> the binaries ?
[15:21] <ogra_> heh
[15:22] <ricmm> ;)
[15:22] <sil2100> ricmm and his barbaric methods ;)
[15:22] <davmor2> dbarth_: the setup seemed to finish it is just the return to accounts that didn't happen I'll have a dig through the logs after and see if anything shows up
[15:24] <jhodapp> sil2100, ok
[15:24] <jhodapp> sil2100, it also showed specific compile errors, but it shouldn't have
[15:26] <sil2100> Yeah, if it happens again we'll have to take a look at what's up with the jenkins machine
[15:26] <Mirv> ycheng-afk: I'm usually available around noon in your utc+8 timezone
[15:28] <dbarth_> davmor2: ok, send me the logs if you see something weird
[15:28] <davmor2> dbarth_: will do
[15:32] <kgunn> sil2100: you guys viewing this as a blocker
[15:32] <kgunn> https://bugs.launchpad.net/media-hub/+bug/1371454
[15:33] <Mirv> bfiller: note the unapproved branch https://code.launchpad.net/~renatofilho/address-book-app/release-18-09-2014/+merge/235149
[15:33] <bfiller> Mirv: arg, let me fix
[15:34] <cwayne> trainguards can I get an RTM silo for line 72?
[15:34] <bfiller> Mirv: done
[15:35] <sil2100> cwayne: lucky you! We have one silo free
[15:35] <cwayne> sil2100: :D
[15:35] <Mirv> bfiller: thanks
[15:35] <Mirv> yeah, just freed one :)
[15:37] <bzoltan> Mirv: Is it possible to merge the landing branch to the UITK trunk today?
[15:38] <lool> trainguards, testing completed on silo 20 with urgent fix for espoo service respawn in utopic; ok to publish?
[15:38] <sil2100> lool: yes, please! We might have that in the next utopic image then
[15:38] <lool> I've tested by tailing the log and seeing the respawns were gone, then that it was working at its best in osmtouch; I based testing on #250 due to stability of latest images
[15:39] <lool> publishing
[15:39] <AlbertA2> trainguards: can I get a silo for line 63?
[15:39] <cjwatson> lool: don't attempt an image build yet though
[15:40] <lool> cjwatson: ack; I dont need one
[15:40] <sil2100> AlbertA2: on it!
[15:43] <brendand> dobey, you know the Delta app doesn't install right? https://wiki.ubuntu.com/Process/Merges/TestPlan/pay-service
[15:44] <sil2100> AlbertA2: so, I cannot normally assign a silo for you sadly.. silo ubuntu 006 has already platform-api locked
[15:44] <sil2100> AlbertA2: that platform-api landing will land soon though
[15:45] <AlbertA2> sil2100: np, I'll wait
[15:45] <dobey> brendand: i just noticed that now on staging yes. i'm not sure why it's failing yet. it doesn't need to install to verify the jsoncpp fix though, and is not caused by jsoncpp
[15:46] <AlbertA2> sil2100: for line 35, I see it didn't get into the QA queue can it be added manually? This is the one you had to rebuilt in the PPA
[15:48] <sil2100> AlbertA2: hm, it's probably because the status is 'failed' - let me rebuild with watch_only and fix it up, it'll appear in the queue then
[15:48] <AlbertA2> sil2100: ok thanks!
[15:48] <sil2100> I was sure it was ok :|
[15:48] <sil2100> It seems the button didn't get pressed correctly
[15:49]  * sil2100 blames his fingers
[15:49] <ogra_> bad button !
[15:49] <sil2100> AlbertA2: sorry for that!
[15:49] <AlbertA2> sil2100: np it's all a black box to me...:)
[15:51] <brendand> dobey, yes it's an existing issue
[15:56] <bzoltan> sil2100: Mirv told me that the Ubuntu silo9 will not land to Utopic because of the freeze. I wonder what will no happen with the landing branch. How and when it can be merged to the UITK trunk. I could start the next landing already.
[15:57] <sil2100> bzoltan: yeah... I think we would have to ask for an exception for that ;/
[15:57] <Mirv> sil2100: and I told bzoltan we can m&c before the release pocket migration, since the release is now already in rtm
[15:57] <sil2100> Mirv: hm, right, makes sense
[15:58] <Mirv> sil2100: my thinking was that the focus is currently on rtm, and trunk can easily reflect that while beta freeze lasts for two more days
[15:58] <sil2100> bzoltan: ok, so as Mirv mentioned, it should be ok to m&c already
[16:01] <popey> fuuuuuuuuuuuuuuuu
[16:01] <Mirv> bzoltan: trunk is now up-to-date
[16:01] <Mirv> popey: the bi-daily chrome/firefox/hangouts fuuu?
[16:04] <popey> yes
[16:07] <brendand> dobey, for the test cases, do i need to be able to reset my account on staging?
[16:07] <popey> who maintains the youtube scope?
[16:07] <brendand> dobey, so that it clears my purchase history and cards?
[16:07] <cwayne> popey: pete-woods
[16:08] <popey> pete-woods: youtube scope asks for access to my youtube account via online accounts, but I have two google accounts on my device. It asks about the "wrong" one (my canonical one)
[16:08] <dobey> brendand: to be able to purchase things that have already been purchased, yes
[16:09] <dobey> brendand: you will have to ask in #u1-internal to have your purchases reset on staging for your account, to accomplish that
[16:09] <bzoltan1> Mirv:  Thank you!
[16:09] <cjwatson> ogra_:  livecd-rootfs | 2.244   | utopic           | source, amd64, arm64, armhf, i386, powerpc, ppc64el
[16:10] <cjwatson> new build probably worthwhile
[16:10] <dobey> brendand: however, simply deleting the account in system settings, and then searching again after about 30 seconds in the scope, should show the price instead (assuming the package is not installed)
[16:10] <ogra_> cjwatson, yep, after the meeting
[16:10] <cjwatson> ogra_: want me to kick it now then?
[16:10] <ogra_> cjwatson, oh, that would be great !
[16:11] <cjwatson> ogra_: done
[16:11] <ogra_> cjwatson, thanks
[16:12] <dobey> ok, need to get lunch here
[16:16] <jhodapp> sil2100, still failed to build again
[16:16] <brendand> dobey, are there any other paid apps for testing?
[16:16] <jhodapp> sil2100, https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-011-1-build/33/console
[16:18] <sil2100> jhodapp: hm, let me check that after the meeting
[16:18] <jhodapp> k
[16:18] <pete-woods> popey: yeah, I could well believe that happens. could you log a bug against unity-scopes-shell + unity-scopes-api saying. "hey, let me choose an account to use!"
[16:19] <popey> yes
[16:22] <popey> done bug 1373019 pete-woods
[16:25] <ogra_> sil2100, RTM image triggered
[16:25] <pete-woods> popey: thanks!
[16:26] <sil2100> ogra_: \o/
[16:29] <sil2100> ogra_: btw. I think I already asked that, but probably forgot... who besides you has the powa to promote images?
[16:29] <ogra_> sil2100, everyone in the cdimage team
[16:30] <ogra_> sil2100, but it isnt documented well and my promote.sh script doesnt cope with the new "all arches go out of sync wrt version numbers" changes
[16:30] <sil2100> jhodapp: looking into that now
[16:31] <ogra_> so currently its all manual (one promotion for each image)
[16:31] <jhodapp> sil2100, thanks
[16:33] <jhodapp> sil2100, hmm, I'm getting the same build error locally now when trying to build on the latest rtm image
[16:33] <jhodapp> sil2100, must be a valid issue then, let me see about fixing it
[16:34] <rsalveti> ogra_: 252 didn't even had the new android still :-)
[16:34] <sil2100> jhodapp: ok, but anyway I'm a bit worried seeing the log there from CI Train itself, as it's looking a bit bad
[16:34] <ogra_> rsalveti, it had once new android
[16:34] <ogra_> not the latest, yeah
[16:34] <sil2100> jhodapp: but for the actual failure yes, it might be the case
[16:34] <ogra_> *one new
[16:34] <rsalveti> ogra_: saw https://code.launchpad.net/~ogra/phablet-tools/phablet-tools-fix-edge-intro/+merge/235440  is already approved, it seems you pinged me right after I went to bed, so all good :-)
[16:35] <imgbot> [16:35] <jhodapp> sil2100, ok so maybe 2 problems
[16:35] <ogra_> rsalveti, yeah, and i didnt even get to land it (wanted to do that yesterday, but nobody approved it)
[16:36] <robru> sil2100: why did you land your branch without fixing any of the issues I raised?
[16:36] <rsalveti> ogra_: it seems you had a lot of fun finding the issue with dpkg-dev
[16:37] <ogra_> rsalveti, yeah :) eynjoy the backlog :)
[16:37] <ogra_> i could write a small novel now
[16:37] <sil2100> robru: so, I mentioned that to slangasek already, the changes for adding tests is now in a separate branch - the reason is that the changes required to enable proper testing are quite big and risky, which would require additional re-testing
[16:37] <rsalveti> :-)
[16:37] <robru> sil2100: landing untested stuff isn't risky?
[16:37] <sil2100> robru: so there is a follow-up merge that's currently worked on, but will be in mergable state soon
[16:38] <sil2100> robru: it's tested manually
[16:38] <rsalveti> cjwatson: hey, quick question, wanted to sync latest livecd-rootfs into rtm, but noticed http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/revision/956
[16:38] <rsalveti> cjwatson: would that cause any issue as rtm still got an older software-properties package?
[16:38] <robru> sil2100: manual tests don't catch regressions on trunk. if code doesn't have test coverage, it's untested by definition.
[16:39] <ogra_> rsalveti, it should be synced soon (software-properties)
[16:39] <rsalveti> ogra_: do we have someone taking care of that?
[16:39] <ogra_> i thought colin was handling that
[16:40] <ogra_> (if not, it probably makes sense to push it into an rtm silo)
[16:40] <sil2100> robru: it will be covered by tests
[16:41] <cjwatson> rsalveti: quite possibly.  I'd handed over software-properties to mvo to sort out but that may still need work
[16:42] <cjwatson> rsalveti: I have to go, can we save this for tomorrow?
[16:42] <robru> sil2100: yes, please finish the tests soon.
[16:42] <sil2100> robru: the branch is uploaded but still work in progress, I'm ripping out some bigger bits from the big build blob
[16:42] <rsalveti> cjwatson: sure
[16:42] <cjwatson> rsalveti,ogra_: (RTM silo 17, in progress)
[16:42] <Ursinha> sil2100: I think what I missed the most was an explanation in the MP on why that was approved even with robru's remarks
[16:43] <ogra_> awesome
[16:43] <Ursinha> sil2100: I understand there are cases and cases, but you know, communication is a pita, so the more information the better :)
[16:44] <sil2100> Ursinha: yeah, sorry about that, it's easy to miss things out when there is a lot on one's head, wasn't my intention
[16:44] <Ursinha> sil2100: I'm sure it wasn't
[16:45] <Ursinha> sil2100: I know it's hard to change habits, you've been working almost by yourself on that code so it's hard to change the mindset to communicate everything because there are other people that care :)
[16:46] <ogra_> Ursinha, just subscribe to the branch and you get a wonderful stream oddf email spam ;)
[16:46] <ogra_> *of
[16:49] <Ursinha> ogra_: heh, I am subscribed to that branch so I get all MP emails :) I'm talking about other kinds of change
[16:50] <sil2100> sergiusens, rsalveti: hey! How does the 'land first in ubuntu-rtm' approach work for you so far?
[16:52] <bfiller> robru: I need silos for lines 54, 75, and 80 when any become available
[16:52] <sergiusens> sil2100: fine; we just need to not let anyone land the other way around anymore ;-)
[16:52] <sil2100> ;)
[16:56] <bfiller> robru, sil2100: actually now need silos for lines 54, 75, 80 and 81 when you can :)
[16:56] <ogra_> Ursinha, *winds* of change (might be smelly though) ?
[16:57] <dobey> brendand: tvstalker and tabugame i think, "evil app" too if it's still there
[16:58] <robru> bfiller: ok got you silo utopic 9 to start, still going though
[16:59] <robru> bfiller: utopic 14 as well
[16:59] <bfiller> robru: thanks!
[16:59] <plars> ogra_: I did just see it have to retry waiting for the session locally with mako+rtm, so maybe there's still a little bit of a delay there?
[16:59] <plars> + adb-shell sudo -iu phablet env '|grep' UPSTART_SESSION=unix
[16:59] <plars> ADB_RC=1
[16:59] <plars> + '[' 0 -lt 5 ']'
[16:59] <plars> + loopcnt=1
[16:59] <plars> + echo 'Retry [1/5] after 60 seconds...'
[17:00] <ogra_> trainguards, please a silo for line 84
[17:00] <ogra_> plars, cant be
[17:00] <robru> bfiller: you're welcome. only one silo left, I guess to be fair I'll give it to ogra...
[17:00] <plars> ogra_: proof? ^
[17:00] <plars> :)
[17:01] <ogra_> plars, hmm, i wonder if it behaves different on your server with multiple devices attached
[17:01] <ogra_> i definitely ran scripts here to test that
[17:01] <plars> ogra_: this is at home with a single device attached
[17:01] <jhodapp> sil2100, do you know if tvoss' changes for media-hub, dbus-cpp and qtubuntu-media have landed in the rtm branch? It seems like it hasn't, which would cause these build errors
[17:02] <plars> ogra_: besides, we're grepping for something in the environment of the session on the device itself, nothing to do with the host system
[17:02] <sil2100> jhodapp: hah, so... regarding that:
[17:02] <ogra_> plars, no, but adb protocol races or some such
[17:03] <ogra_> plars, i definitely dont see that here ... i wonder how that can be
[17:03] <plars> ogra_: I don't think so, we would have seen an error from adb in that case rather than just ADB_RC=1
[17:03] <ogra_> plars, is that with a proper "adb wait-for-device" ?
[17:03] <brendand> dobey, there's another pre-existing bug about the progress bar continuing to say in progress after cancelling
[17:04] <robru> ogra_: trying to assign your silo, just gotta wait a bit for one to free up (it's freeing right now, just slow)
[17:04] <ogra_> plars, a simple while loop that calls the above and "adb shell env |grep ... " is definitely not giving me such stuff
[17:04] <ogra_> robru, k, no worries
[17:05] <cwayne> you can free rtm/008 by publishing it :) it's an isolated bug fix so shouldn't need qa signoff
[17:05] <ogra_> plars, in any case please drop the sudo (if possible everywhere over time)
[17:05] <ogra_> the shell you get in is already one sudo and two bash wrappings :)
[17:05] <sil2100> jhodapp: we reverted the media-hub landing for RTM because it was causing a nasty bug in unity8 autopilot tests, causing the tests to hang
[17:05] <ogra_> no need to add another one
[17:06] <sil2100> jhodapp: so sadly, that code needs to get fixed first for it to be reuploaded
[17:06] <dobey> brendand: the fix for that is in rtm silo 6
[17:06] <jhodapp> sil2100, oh that one, I thought kgunn just showed that it was due to a libgstreamer update?
[17:06] <plars> ogra_: worse, it's after a wait-for-device and an extra sleep 60 that's been in there for ages
[17:07] <ogra_> plars, i dont get that ... is your adb startup hacked on the device somehow
[17:07] <plars> ogra_: I have several things I'm looking at around the ci scripts today, so I'll have lots of opportunity to try to reproduce it
[17:07] <sil2100> jhodapp: it might be gstreamer, but the truth is that gstreamer upload was really really old - and I think we even now confirmed that it was the dbus-cpp upload coming with media-hub that caused that regression
[17:08] <jhodapp> sil2100, ah interesting, ok
[17:08] <sil2100> jhodapp: since our image with just media-hub and qtubuntu-media reverted still had the issue, since the dbus-cpp revert didn't make it in time
[17:08] <jhodapp> sil2100, well I'll modify my MR then to use the old media-hub function prototypes
[17:08] <sil2100> jhodapp: if it's fixed in the next image then we'll know that it were the dbus-cpp changes at fault
[17:08] <ogra_> plars, right, but it is technically not possible ... especially not after a 60sec sleep, something must slow your lightdm down really massively to even get into that state
[17:08] <jhodapp> sil2100, ok, is tvoss aware of this?
[17:09] <plars> ogra_: this is calling a tool called adb-shell which is just a wrapper for adb that runs the command over adb, echos $? on the device, and grabs that return value to send back
[17:09] <sil2100> jhodapp: sorry for that... sadly tvoss is on holidays so we couldn't easily resolve this ;/
[17:09] <ogra_> plars, there is a minor possibility of a race that probably has a window of halfg a second
[17:09] <jhodapp> sil2100, it's ok, know when he's back?
[17:09] <sil2100> jhodapp: in two weeks :(
[17:10] <jhodapp> sil2100, oh man
[17:10] <kgunn> jhodapp: what will it mean ?
[17:10] <ogra_> plars, sure, but the device only starts adbd once the session is ready ... you would have to have a session startup time of more than a minute if your 60sec sleep still shows it ... thats impossible
[17:10] <sil2100> jhodapp: we tried poking mandel for help
[17:10] <jhodapp> kgunn, it means we won't get mpris support unless someone fixes that
[17:10] <kgunn> eeeewwwww
[17:10] <plars> ogra_: I don't disagree, I'm just telling you what I saw
[17:10] <kgunn> jhodapp: and we need that for the sound panel to control audio right ?
[17:10] <jhodapp> indeed
[17:10] <sil2100> The revert was supposed to be temporary, but it seems we don't have anyone knowing the coode to fix that
[17:11] <ogra_> plars, right, i dont understand how you can see that :) ... i saw it in the logs too
[17:11] <jhodapp> sil2100, yep, we need to spread the dbus-cpp knowledge for sure...it's been a repeated pain point
[17:11] <plars> ogra_: shared hallucination then? :)
[17:11] <sil2100> kgunn, jhodapp: if you could find someone that knows dbus-cpp and how to use it to work on this, we would love having this fixed
[17:11] <ogra_> plars, adbd is "start on started lightdm" ... the first thing that does is fire up init whichh populated the variable
[17:11] <ogra_> *populates
[17:12] <kgunn> sil2100: not sure anyone does...but...let me see if a mir guy could try....couple of days beats 2 weeks
[17:12] <ogra_> plars, the chances that you kick in between lightdm and the session startup (which cant be more than 1sec) are extremely low ... there must be something really wrong
[17:12] <kgunn> sil2100: since mir guys might be use to tvoss-style :)
[17:12] <ogra_> plars, how did you work around the edges into issue ?
[17:13] <ogra_> probably that or the wizard get in the way or some such
[17:13] <kgunn> jhodapp: can you help in terms of an isolated test case ?....like do we know how dbus-cpp is gettingin this state ?
[17:13] <plars> ogra_: by calling: adb shell "sudo dbus-send --system --print-reply --dest=org.freedesktop.        Accounts /org/freedesktop/Accounts/User32011 org.freedesktop.DBus.Properties.   Set string:com.canonical.unity.AccountsService string:demo-edges variant:       boolean:false"
[17:13] <kgunn> something other than "run unity8 test" (or at least shorter)
[17:13] <ogra_> yeah, thats correct
[17:13] <plars> (ignore whitespace breakage by cut/paste)
[17:13] <ogra_> yeah
[17:13] <sil2100> tvoss-style, heh ;)
[17:13] <ogra_> (i'm just landing the final bit for the fix btw)
[17:14] <plars> ogra_: cool
[17:14] <kgunn> sil2100: like kung fu...monkey style, tiger style....tvoss style
[17:14] <jhodapp> kgunn, not yet, I haven't had any time to look into this at all yet
[17:14] <jhodapp> kgunn, dbus-cpp is a bear
[17:14] <ogra_> plars, hmm, now that we talk about that ... i'm not actually sure the wizard uses the same session var as we have later in the session ...
[17:14] <kgunn> jhodapp: sil2100 ...ok, sounds like we still need to wait and confirm anyway ?
[17:14] <ogra_> plars, can you try with the wizard already disabled
[17:14] <jhodapp> kgunn, yes we do
[17:14] <kgunn> may or may not be dbus-cpp
[17:15] <plars> ogra_: what do you mean?
[17:15] <ogra_> plars, do you see it in every run on every boot or only in the frst one ?
[17:15] <plars> ogra_: the error I posted earlier?
[17:15] <ogra_> it could indeed be that if the wizard is started the env is different
[17:16] <plars> ogra_: that was just the first boot so far, haven't looked deeper into it yet
[17:16] <robru> ogra_: ok you got utopic 20
[17:16] <ogra_> so that might allow you to access the device befor the var is populated
[17:16]  * ogra_ hugs robru
[17:16] <ogra_> plars, right, the wizard might be the issue here
[17:16] <robru> ogra_: you're welcome!
[17:17] <plars> ogra_: is it enough to disable the wizard though, or does it need to reboot between?
[17:17] <ogra_> plars, thats the only explanation i have ... as i said, in a normmal boot it is technically not possible to connect
[17:17] <plars> ogra_: I think we'd need to throw in an extra reboot
[17:17] <ogra_> ... before the var is populated
[17:17] <ogra_> plars, no, it shoudl be fine after the wizard was disabled and the normal session started
[17:18] <robru> brb, breakfast
[17:18] <plars> ogra_: but the normal session isn't restarted after you run phablet-config to disable the wizard I don't think. iirc it just touches a file or something
[17:18] <jhodapp> sil2100, can you ping me after you've confirmed that the next image is ok?
[17:19] <ogra_> plars, oh !
[17:19] <jhodapp> sil2100, we'll make sure to find someone to look into it once dbus-cpp is confirmed
[17:19] <ogra_> plars, yeah, then we mmiss one reboot here
[17:19] <sil2100> jhodapp: sure, we'll know once smoketesting starts (and the image finishes building)
[17:19] <ogra_> silly bot
[17:19] <jhodapp> sil2100, cool, thanks
[17:25] <jhodapp> sil2100, ok trying another build
[17:26] <sil2100> jhodapp: just remember! The revert was only in the archive, so if you release trunk then those changes need to get back
[17:27] <jhodapp> sil2100, I don't quite follow, can you explain that?
[17:27] <sil2100> jhodapp: so... we reverted the media-hub, qtubuntu-media and dbus-cpp packages in the archive, so the archive doesn't have the 'broken' ones anymore - but we didn't commit the revert to trunk
[17:28] <sil2100> jhodapp: so trunk still has the dbus-cpp related changes
[17:28] <sil2100> jhodapp: this means that if anyone releases media-hub (some new release) it will re-introduce the reverted changes
[17:28] <jhodapp> sil2100, right exactly...so when we do release it we'll just need to update qtubuntu-media again
[17:29] <pmcgowan> is it safe to upgrade yet?
[17:29] <sil2100> jhodapp: yes
[17:29] <jhodapp> sil2100, yeah ok
[17:29] <sil2100> jhodapp: and make sure that the issue is fixed
[17:40] <imgbot> [17:40] <imgbot> [17:40] <ogra_> sil2100, hmmm
[17:40] <ogra_> i see the lib ... but i dont see dbus-cpp
[17:42] <sil2100> ogra_: the lib was what was upgraded with the landing
[17:42] <ogra_> hah
[17:42] <ogra_> my own package cheated me :PP
[17:42]  * ogra_ saw dbus-property-service in the same landing
[17:43] <ogra_> and i was somehow reading dbus-cpp :P
[17:43] <plars> ogra_: I did try taking out the sudo -iu phablet on the second run, and it all worked perfectly this time. It could just be really rare
[17:43] <plars> and I just got (un)lucky
[17:43] <ogra_> plars, well, the sudo might add some extra weirdness
[17:43] <sil2100> ;p
[17:43] <plars> ogra_: perhaps. I'll remove the sudo at least for now, but I'd like to do some more testing before removing the check altogether
[17:43] <ogra_> plars, it is already like inception of shells :) you just added one more layer
[17:43] <plars> yep
[17:44] <ogra_> yeah, keep the check
[17:44] <ogra_> especially for the fiirst boot where the wizard might give us even a wrong value for that var
[17:44] <ogra_> subsequent boots should theoretically be fine though
[17:44] <plars> ogra_: iirc we only do the retry loop twice, and they are only for the provisioning step, not the other boots
[17:45] <ogra_> ah, cool
[17:45] <pmcgowan> ogra_, are images all fixed?
[17:46] <pmcgowan> I mean booting ok
[17:46] <ogra_> pmcgowan, i havent seen utopic finish
[17:46] <pmcgowan> ok
[17:46] <davmor2> sil2100: so there is definite flakiness in the video scope other than that I'm fairly happy I'm going to dig into the flaky video scope now anf the twitter account issue so I wouldn't promote this image but it is about [---] this far from being a good un :)
[17:46] <ogra_> plars, ^^^
[17:47] <sil2100> davmor2: uh
[17:47] <ogra_> plars, if you want to try the edges-intro fix
[17:47] <sil2100> davmor2: so no +1 on this one? What are the blocking issues? The video scope and twitter account?
[17:47] <ogra_> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-020
[17:47] <ogra_> twitter .. tsk ... just tell them to use telegram
[17:48] <davmor2> sil2100: video scope is a definite twitter may just of been a network glitch or something but I'll need to look into it to know
[17:49] <sil2100> davmor2: do we need thostr or pstolowski regarding the video scope then?
[17:49] <sil2100> I wonder who we can ping regarding those
[17:49] <elopio> fginther: could you review this one? https://code.launchpad.net/~canonical-platform-qa/ubuntu-clock-app/xvfb_and_qml_tests/+merge/235682
[17:49] <sil2100> davmor2: if you could fill in bugs for those then it would be awesome
[17:50] <davmor2> sil2100: yeap let me have a quick dig into the twitter issue but I can file one for the video scope as that is a definite issue
[17:53] <sil2100> davmor2: how did these issues slip to the image?
[17:53] <sil2100> Did we have any scope related landings?
[17:54] <davmor2> sil2100: no but it could be media-hub and the revert that have broken it, doesn't seem to effect music scope only video
[17:55] <davmor2> sil2100: it may also have something to do with the scope login on youtube maybe too many moving targets and we only test one at a time probably
[17:58] <sil2100> davmor2: could you pass on that info to ToyKeeper? And ask her to perform similar checks on the new image that finished building? (#58)
[17:58] <davmor2> sil2100: will do
[17:59] <rsalveti> ogra_: are we still building one image for utopic?
[18:00] <ogra_> rsalveti, if it didnt fail ... let me check
[18:01] <rsalveti> seems it failed to build
[18:01] <rsalveti> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/utopic/ubuntu-touch/
[18:02] <ogra_> rsalveti, right, i'm not sure if that was a test build for stgrabers livecd-rootfs changes thopugh
[18:02] <rsalveti> oh, right, could be
[18:02] <ogra_> (since it uses the PPA)
[18:02] <ogra_> but cjwatson said he had triggered an image
[18:02] <rsalveti> but then it means we didn't trigger one for utopic
[18:02] <ogra_> irritating
[18:02] <ogra_> i'll trigger one :/
[18:02] <rsalveti> alright, thanks
[18:02] <ogra_> bah
[18:03] <ogra_> isotracker says its re-building
[18:03] <rsalveti> weird
[18:04] <davmor2> ogra_, sil2100: do either of you happen to know the project to file against for the video scope?
[18:04] <ogra_> no idea, sorry
[18:14] <cjwatson> ogra_: I triggered it for utopic, but I think it got stuck behind a test build or something
[18:14] <cjwatson> ogra_: I had to go out for a thing at school so couldn't chase it
[18:15] <ogra_> cjwatson, right, the tracker doesnt like to let me stop the request though
[18:16] <davmor2> sil2100: https://bugs.launchpad.net/unity-scope-mediascanner/+bug/1373067
[18:18] <sil2100> davmor2: thanks :)
[18:42] <balloons> fginther, ping
[18:45] <robru> we got 6 free RTM silos, anybody ready for one?
[18:50] <balloons> plars, ping
[18:50] <plars> balloons: hi
[18:54] <balloons> plars, hey, so wanted to chat about something, as you look at dashboard results probably more than anyone :)
[18:54] <balloons> do you think this problem occurs often? https://bugs.launchpad.net/ubuntu-clock-app/+bug/1369990
[18:56] <plars> balloons: yeah, we've talked about it on the call before. I think that's the same as the one ogra_ was trying to fix with the latest build right?
[18:56] <plars> ogra_: or is that different from the unity8 stuff?
[18:58] <plars> it does seem to still happen in the latest mako rtm though, so perhaps not :(
[18:58] <balloons> plars, well I mention it as I think I'd like to see the autopilot launches tweaked to all for these long starts
[18:58] <balloons> plars, that said, the fact it takes so long should also be measured and debugged
[18:59] <plars> balloons: we don't call autopilot directly
[18:59] <balloons> plars, ohh right, you are through phablet-test-run
[18:59] <balloons> but regardless, it calls it
[19:04] <balloons> plars, so in order for CI to change nevertheless you would need phablet-test-run to support it. That's good to file away
[19:05] <balloons> ahh indeed you can pass it now, I thought you could
[19:05] <robru> jdstrand: you tested apparmor in rtm?
[19:05] <jdstrand> robru: yep
[19:06] <robru> jdstrand: and the thing you were waiting for landed?
[19:06] <jdstrand> robru: I am talking to cwayne and rsalveti about it now
[19:06] <robru> jdstrand: oh ok. let me know when that's sorted and then I'll publish
[19:17] <jdstrand> robru: ok, we decided to not wait on the kernel. cwayne and I have coordinated. I am doing the landing now
[19:23] <jhodapp> robru, rtm silo 11 is ready for publishing
[19:23] <dobey> trainguards: can we get an rtm silo for line 22 in the spreadsheet?
[19:23] <jhodapp> robru, it then needs a sync to utopic
[19:23] <dobey> although i hope the sync:20 isn't wrong now
[19:35] <jhodapp> robru, ping
[19:42] <robru> jhodapp: hey sorry one sec
[19:43] <robru> dobey: don't sync:20 it's wrong
[19:44] <dobey> robru: i didn't. it's been there for like a week :-/
[19:45] <robru> dobey: is it just unit scope click?
[19:46] <robru> dobey: ok you got silo rtm5 please build (or tell me if there's any other packages necessary)
[19:46] <dobey> robru: unity-scope-click yes
[19:47] <dobey> robru: oh, i have to run a build rule for package syncs to rtm now? i thought i wasn't supposed to do that?
[19:48] <robru> dobey: what is this i dont even
[19:48] <robru> jhodapp: you got utopic 13, please build
[19:48] <jhodapp> robru, thanks
[19:48] <robru> jhodapp: but don't build until after it migrates in rtm
[19:49] <jhodapp> robru, ah ok
[19:49] <dobey> robru: huh?
[19:49] <robru> dobey: since when did anything ever happen automatically? of course you have to trigger a build job to make anything happen in the train?
[19:50] <dobey> robru: since when last time i did that for a sync to rtm, and you told me i don't need to do that
[19:51] <robru> dobey: maybe it was a special case and I took care of it for you or something. you always have to trigger a build to make anything happen
[20:05] <davmor2> ogra_: it's your fault
[20:06] <davmor2> ogra_: plug your phone into the pc, phablet-shell into it try and turn the on
[20:15] <robru> jhodapp: ok you can build now
[20:24] <jhodapp> robru, cool
[20:26] <ogra_> balloons, plars, the bug is somewhere between gstreamer, media-hub and dbus-cpp (teh one that makes the AP tests fail)
[20:28] <sergiusens> robru: can I get something for that ^ ?
[20:29] <robru> sergiusens: ok you got rtm7
[20:29] <sergiusens> ty
[20:30]  * sergiusens waits for the magic to happen
[20:31] <robru> sergiusens: you mean, the magical moment when you click the build button?
[20:31] <sergiusens> robru: the magical moment the spreadhseet and the dashboard sync up and reflect what you told me ;-)
[20:32] <robru> sergiusens: you can click the build button in the dashboard as soon as I tell you. no need to wait for that stuff
[20:32] <sergiusens> robru: yeah, it wasn't showing up, took 20 seconds more ;-)
[21:30] <imgbot> [21:31] <ogra_> finally ...
[21:31] <ogra_> (not the silo, the image indeed :) )
[22:18] <popey> ogra_: should i flash back to 251? (I stupidly updated to 252)
[22:32] <robru> bfiller: hmm, ubuntu-keyboard wasn't actually in the release pocket yet, not sure why citrain reported it prematurely. hopefully freeing the silo doesn't stop the publication
[22:32] <bfiller> robru: hope not, sorry I saw merge and clean and hit the button
[22:45] <robru> bfiller: yeah not your fault, no worries
[22:45] <robru> bfiller: looks like it's ok
[22:46] <robru> bfiller: ok you got rtm8, please build
[23:15] <imgbot> [23:15] <imgbot> [23:31]  * popey wonders if 253 is wise to update to
[23:34] <ahayzen> popey, you just volunteered as the guinea pig ;)
[23:38] <popey> heh, it would seem that way
[23:38] <popey> well, it boots
[23:39] <popey> GO GO GO 253
[23:40] <ahayzen> \o/
[23:40] <ahayzen> deploy!
[23:40] <popey> SHIP IT!