[00:04] <robru> ToyKeeper: define "need" though. like is this something that a customer is urgently demanding? or can it wait for tomorrow?
[00:05] <ToyKeeper> robru: I'm not sure exactly; I got only a brief summary:
 ops-team: The landing gates are closing tonight, silo 000 needs sign off, the rest will wait.
 ops-team: if there is no priority fix tomorrow, we'll have a candidate for ww07 tomorrow morning.
[00:06] <robru> ToyKeeper: well that's more than anybody told me ;-)
[00:06] <ToyKeeper> I missed a lot yesterday because I had an extended power outage...  otherwise I'd probably be better-informed.
[00:07] <robru> ToyKeeper: I can override the publish in spite of the lack of reviews if it is really that urgent, but I'm reluctant to do so because it's three different MPs, none of which have any reviews on them at all. surely lots of people reviewed these changes but nobody bothered to mention it on the MPs.
[00:07] <ToyKeeper> robru: Worst case, we can probably trigger a build a few hours later than planned...  I mean, if the change is important enough to need that.
[00:07] <ToyKeeper> After the people who know the context get back online.
[00:08] <robru> ToyKeeper: yeah that's also true. Ok I'm not going to publish it unless I hear otherwise from management.
[00:08] <cjwatson> Maybe it's worth SMSing the people in question if it's urgent?
[00:09] <robru> cjwatson: couldn't hurt I suppose. you volunteering? ;-)
[00:09] <cjwatson> Nope, I'm about to go to bed :)
[00:09] <robru> cjwatson: sweeet dreams!
[00:09] <cjwatson> Just a suggestion
[00:09] <robru> ToyKeeper: ok I'll SMS pmcgowan
[00:11] <ToyKeeper> robru: I was tempted to block it anyway, due to changes with no tests.  Not sure if right now is the best time to go back to strict QA-nazi mode though.
[00:11] <robru> ToyKeeper: wow, this landing has a lot going for it ;-)
[00:14] <robru> ToyKeeper: ok, sms sent, will let you know if I hear anything
[01:14] <boiko> cjwatson: thanks
[02:05] <imgbot> [02:14] <kgunn> trainguards yo could i get a reconfig on vivid silo 0 ?
[02:14] <robru> kgunn: one sec
[03:05] <imgbot> [04:20] <imgbot> [04:20] <imgbot> [08:53] <Mirv> dbarth: mardy: hey, have you noticed your MP:s are not approved? https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-000-2-publish/28/console
[08:54] <mardy> Mirv: I'll let dbarth approve them, I don't like self-approving :-)
[09:12] <vila> hi there, any pending CI issues around ?
[10:12] <Mirv> mardy: still no dbarth anywhere I guess?
[10:13] <mardy> Mirv: he should be here, but I guess I'll just approve the MPs myself, to save some time
[10:14] <mardy> Mirv: done
[10:14] <Mirv> mardy: ok! top-approve then please. it's really a non-issue other than we can't decide for teams how their processes are.
[10:15] <Mirv> mardy: thanks, seeing those!
[10:22] <jgdx> sil2100, is rtm landing 7 rejected for this milestone?
[10:24] <john-mcaleely> sil2100, I am building a new device tarball
[10:24] <sil2100> jgdx: I remember you sorted out all the doubts from QA, right?
[10:25] <sil2100> jgdx: did you get it signed-off by QA in the end?
[10:25] <jgdx> sil2100, not all. Omar is worried, but I still think he's only seeing that one (really bad) bug.
[10:25] <jgdx> sil2100, no, we're waiting on a fix for that ^ bug
[10:25] <jgdx> sil2100, let's say we do get it fixed by eod, can we still get it landed?
[10:26] <sil2100> jgdx: it'll have to go into the next milestone sadly, since we'll be starting promotion testing around afternoon already - but no worries, this milestone is not a super important one
[10:26] <sil2100> The next will be much bigger
[10:26] <jgdx> sil2100, okay, thanks.
[10:29] <dbarth> Mirv: sorry, now approving
[10:29] <dbarth> mardy approved
[10:29] <Mirv> dbarth: mardy already did, and I published. no worries!
[10:30] <dbarth> hangouts overflow :/
[10:32] <sil2100> \o/
[11:20] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150211-74c2df2.tar.xz
[11:20] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150211-74c2df2.changes
[11:20] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-testresults-20150211-74c2df2.ods
[11:21] <john-mcaleely> sil2100, ^ new device tarball for rtm/milestone. will do landing spreadsheet next
[11:21] <sil2100> Excellent :)
[11:21] <sil2100> john-mcaleely: please update the existing device tarball landing
[11:21] <john-mcaleely> sil2100, ok, will do
[11:22] <john-mcaleely> sil2100, updates
[11:23] <john-mcaleely> updates
[11:23] <john-mcaleely> updated, even
[11:34] <sil2100> \o/
[11:57]  * sil2100 away for lunch
[12:58] <sil2100> jibel, davmor2: is anyone on the device tarball right now?
[12:59] <davmor2> sil2100: I am after Lunch
[12:59] <jibel> sil2100, davmor2 is not only on the tarball, but also testing it
[12:59] <jibel> after lunch :)
[12:59] <sil2100> ;D
[13:13] <pmcgowan> robru, seems you went ahead with silo 0
[13:13] <pmcgowan> which is good
[13:14] <sil2100> We needed a top-approval though, but that happened in the morning
[13:14] <pmcgowan> sil2100, ok
[13:14] <pmcgowan> I am off to the office
[13:14] <sil2100> pmcgowan: we signed-off silo 5 and now all that is left is silo 3 and the device tarball
[13:14] <sil2100> Then we can get the promotion candidate spinned
[13:15] <jibel> pmcgowan, I think there is too much risk to land silo 4 for ww07. Do you think it could be moved to ww09 and we test it first thing after the release of ww07?
[13:15] <pmcgowan> looking
[13:15] <jibel> pmcgowan, it's the update from oxide 1.3 to 1.4
[13:16] <pmcgowan> jibel, do you know what it fixes? seems like zooming and a couple others
[13:17] <sil2100> Saviq: ouch ;) You put the merges in the test plan and vice-versa ;D
[13:17] <Saviq> sil2100, oops
[13:18] <pmcgowan> jibel, I dont think oSoMoN  is online today? he hoped to land it yesterday
[13:18] <jibel> pmcgowan, I don't know the details the diff is 500MB. The rationale is essentially http://www.ubuntu.com/usn/usn-2476-1/.
[13:19] <jibel> pmcgowan, we discussed this morning. He agreed to put it aside if there is a risk for the schedule of this release
[13:19] <pmcgowan> jibel, ok, then up to you, I am ok either way
[13:19] <pmcgowan> if not enough time then defer
[13:20] <jibel> pmcgowan, OK, thanks. Lets move it to next milestone then.
[13:20] <pmcgowan> ok
[13:22] <sil2100> We decided on the meeting to skip that to the next milestone as well
[13:50] <Mirv> I guess saviq would be ok to receive that silo now
[13:50] <Saviq> Mirv, yes please
[13:51] <sil2100> Saviq, Mirv: I assigned it
[13:51] <sil2100> hmmm
[13:51] <sil2100> Why didn't it assign it?
[13:51] <Mirv> that is the question :)
[13:51] <sil2100> WTH
[13:51] <Mirv> Saviq: 004
[13:51] <sil2100> The prepare job even ran
[13:52] <sil2100> https://ci-train.ubuntu.com/job/prepare-silo/4068/console <- duh
[13:52] <Mirv> sil2100: I only see a reconfigure attempt on non-assigned silo
[13:52] <sil2100> Ok, spreadsheet had issues...
[13:52] <Mirv> sil2100: meaning the id got given already. as usual when there is no silo but id field is filled, I clear the id field first.
[13:53] <sil2100> Mirv: it was empty, but maybe it was just something strange happening
[14:12] <sil2100> davmor2: once you test the device tarball, be sure to switch it to 'Granted' in the spreadsheet :)
[14:12] <davmor2> sil2100: no shan't :P
[14:13] <sil2100> Come ooon, don't be like thaat
[14:13] <sil2100> boiko, bfiller: hey! We noticed some autopilot test problems on krillin ubuntu-rtm with dialer-app, camera-app and gallery-app
[14:14] <sil2100> boiko, bfiller: e.g. http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/233:20150211:20150209-094615f/313/
[14:14] <bfiller> sil2100: we'll have a look
[14:16] <sil2100> Thanks!
[14:17] <sil2100> I need to jump out for a moment, brb
[15:02] <sil2100> davmor2: how far are you with testing?
[15:03] <davmor2> sil2100: well I'm testing it after all the hang ups getting it installed
[15:04] <sil2100> Hang-ups? You mean, because of the new tarball?
[15:05] <davmor2> sil2100: yeap and the fact that I need to add a ppa because the utopics ubuntu-device-flash isn't up-to-date and finding out if the recovery image for the one was the same as the vivid one and ........
[15:42] <sil2100> rvr: how's the address-book-app testing going?
[15:43] <rvr> sil2100: Looks good so far, verifying a related bug that I found (but not a regression).
[15:47] <john-mcaleely> sil2100, davmor2 device tarball news?
[15:48] <sil2100> john-mcaleely: davmor2 is still testing it, seems like there were some problems setting it up initially ;)
[15:48] <john-mcaleely> sil2100, ack
[15:48] <davmor2> getting there
[15:49] <rvr> bfiller: https://bugs.launchpad.net/address-book-app/+bug/1420851
[15:49] <sil2100> Once rvr and davmor2 finish and both get uploaded, we'll kick a new image
[15:49] <sil2100> hm, maybe we could disable the importer for the device tarball upload
[15:49] <sil2100> Since we'll build a new image anyway
[15:50] <bfiller> rvr: sounds like a feature to me :)
[15:50] <bfiller> unless it breaks something
[15:51] <rvr> bfiller: haha
[15:51] <bfiller> seriously
[15:53] <rvr> Let's hope it doesn't interpret JavaScript
[15:55] <kenvandine> cihelp, we've been having some flaky CI test runs for ubuntu-system-settings, some of which look like it's just failing to start the app https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/982/testReport/junit/ubuntu_system_settings.tests.test_security/SecurityTestCase/test_locking_control_value/
[15:56] <kenvandine> some other apps have been seeing it too, bfiller can you list the known ones?
[15:56] <rvr> bfiller: sil2100: Address book silo approved
[15:57] <plars> kenvandine: when did that start?
[15:57] <bfiller> cihelp 4 out of 7 failures on camera-app are because it couldn't be started http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/233:20150211:20150209-094615f/313/
[15:57] <kenvandine> sometime last week i think
[15:57] <kenvandine> plars, for settings we've been seeing it from vivid branches
[15:57] <kenvandine> not sure about rtm
[16:00] <plars> bfiller: that's on smoke results on krillin, which is very different from what kenvandine is pointing at
[16:01] <sil2100> rvr: o/
[16:01] <kenvandine> seems like a similar problem though
[16:04] <sil2100> bfiller: https://code.launchpad.net/~renatofilho/address-book-service/fix-1390110-rtm/+merge/245598 <- needs approval :)
[16:04] <bfiller> sil2100: done
[16:05] <plars> bfiller: well at least one failure I see there is because of a missing test dependency it looks like - "ImportError: No module named 'wand'"
[16:05] <bfiller> plars: yes, we know about that one. and there are 2 flaky tests as well. but 4 that fail because the app fails to start
[16:05] <plars> which is probably yet another problem.. kenvandine: looking at the vivid mako smoke tests though, I'm not sure that I see this happening there
[16:06] <plars> bfiller: is it always the same 4? do you know if it's reproducible locally?
[16:06] <bfiller> plars: it's those 4 that seem infra related possibly
[16:06] <bfiller> plars: it's not reproducible locally no, not those 4
[16:06] <bfiller> plars: don't nkow if it's alwyas the same 4
[16:07] <plars> so test_low_disk seems to be one of them, and no it doesn't appear to fail every time
[16:07] <plars> if autopilot is failing to start the app though, I'm not sure what we can do about that in CI
[16:07] <plars> I'll talk to QA and see if they have any recommendations
[16:08] <kenvandine> plars, from the log i pasted, do you agree that it looks like it's failing to start?
[16:08] <kenvandine> for settings it's not always the same tests
[16:08] <kenvandine> i'm pretty sure it's not, jgdx can you confirm?
[16:08] <plars> kenvandine: that would appear to be the case, yes
[16:09] <kenvandine> this was stable for a while
[16:11] <jgdx> kenvandine, seems random to me, but the sim unlock test in security failed twice in a row, with similar symptoms
[16:26] <plars> kenvandine: bfiller: from talking to elopio it looks like there's a 10 second timeout waiting for ubuntu-app-launch to either succeed or fail in launching the app. Any chance the app just sometimes takes that long?
[16:27] <kenvandine> plars, it really shouldn't
[16:27] <plars> kenvandine: bfiller: he said the screenshot shows that the app is open though, so somehow there's either a race where it's timing out first, or it fails to see that it's open
[16:29] <bfiller> plars: shouldn't take take 10seconds to open
[16:31] <elopio> is there a way to look at the ubuntu-app-launch log?
[16:33] <plars> elopio: where can we find that log?
[16:34] <elopio> plars: that's my same question, just better phrased :)
[16:35] <plars> elopio: it's entirely possible that we're not capturing it at the moment. But if it's just another log, that could be added perhaps
[16:38] <elopio> tedg: ^
[16:38] <elopio> is there a ual log?
[16:38] <elopio> we are seeing the camera to timeout when being launched with UbuntuAppLaunch.start_application_test
[16:47] <elopio> plars: kenvandine: bfiller: this one http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-vivid-mako/982/testReport/junit/ubuntu_system_settings.tests.test_about/StorageTestCase/test_space_used_by_pictures/
[16:48] <elopio> seems to be cause by this crash: http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-vivid-mako/982/artifact/clientlogs/ubuntu_system_settings/_usr_bin_system-settings.32011.crash
[16:48] <elopio> Saviq: could we put timestamps into the unity8.log ?
[16:50] <Saviq> elopio, bug #1154207
[16:51] <elopio> Saviq: thanks.
[16:54] <davmor2> sil2100: if you would care to check the spreadsheet around line 70
[16:55] <john-mcaleely> ooh
[16:55] <john-mcaleely> I've never done it this way before
[16:55] <sil2100> o/
[16:55] <sil2100> davmor2: yay
[16:56] <john-mcaleely> sil2100, so, do I push now?
[16:56] <sil2100> ogra_: maybe we could switch-off the importer for rtm, publish the tarball and then re-enable it when kicking the image?
[16:56] <sil2100> john-mcaleely: please wait one moment, maybe we can do it more cleanly with the importer off
[16:56] <john-mcaleely> aha. waits
[16:56] <sil2100> It's not a big deal, but still
[16:56] <john-mcaleely> no rush :-)
[16:57] <ogra_> sure
[16:57] <ogra_> sil2100, you know you can do that too now, right ?
[16:57] <sil2100> ogra_: thanks ;) I don't know the foo of that yet
[16:57] <popey> sil2100: is there a meeting today?
[16:57] <ogra_> as cdimage user: crontab -e
[16:57] <sil2100> popey: yes :)
[16:58] <davmor2> sil2100: double check that silo003 got int first please
[16:58] <davmor2> sil2100: and 5 for that matter :)
[16:58] <ogra_> comment the last line
[16:58] <sil2100> davmor2: sure
[16:58] <sil2100> ogra_: oooh
[16:58] <sil2100> It's that easy?
[16:58] <ogra_> and let #ubuntu-release know about it
[16:58] <ogra_> yeah
[16:58] <ogra_> done
[17:00] <sil2100> ogra_: thanks!
[17:00] <ogra_> rsalveti, next vivd build started (FYI)
[17:00] <sil2100> john-mcaleely: you can push the tarballz!
[17:00] <john-mcaleely> sil2100, ack
[17:00] <rsalveti> ogra_: great
[17:01] <john-mcaleely> sil2100, pushed
[17:01] <john-mcaleely> sil2100, do I need to update the spreadsheet now?
[17:15] <imgbot> [17:15] <sil2100> jibel: crap, I remembered what I wanted to poke about - we have ToyKeeper around today?
[17:16] <jibel> sil2100, yes
[17:18] <ogra_> rsalveti, passed the passwd change (and failed on /etc/group as expected) ... i need to add more logic so we get all data on the first run https://launchpadlibrarian.net/197323808/buildlog_ubuntu_vivid_armhf_ubuntu-touch_FAILEDTOBUILD.txt.gz
[17:21] <rsalveti> ogra_: yeah, that would make it way easier
[17:21] <ogra_> the 99 script has that logic, i'll just push that over
[17:28] <ogra_> ok, uploaded
[17:28] <ogra_> lets see how that goes ... then i'll port all of it to snappy
[17:52] <dobey> fginther: hey. is it possible to have the jenkins click autopilot job run the tests by some means other than on a actual device/emulator?
[17:52] <dobey> fginther: or we'd need a new/different job for those cases?
[17:55] <jibel> sil2100, davmor2 will start the sanity test if the image is built on time, and ToyKeeper will continue the verification of the image
[17:55] <sil2100> jibel: image still building
[17:56] <jibel> sil2100, yeah, it should be built in one hour or so
[17:56] <sil2100> ogra_: will you be around in the nearest 30 minutes? I need to drive to pick up my girlfriend from the train station, if by any chance you notice that the build is ready could you re-enable the importer to get the tarballs in place?
[17:56] <sil2100> In case it finishes when I'm not around :)
[17:57] <ogra_> sil2100, will do
[17:57]  * sil2100 doesn't want to make QA waiting
[17:57] <sil2100> ogra_: thanks!
[17:57]  * davmor2 sits here waiting on sil2100 
[18:02] <fginther> dobey, it's technically possible, but CI doesn't have any infrastructure in place for any other method  :-( . We may already have story to address this in our backlog, but it's not something we have prioritized right now
[18:04] <dobey> fginther: ok. lp:pay-ui is a bit of an oddity, so it's not possible to run the tests on top of Mir at the moment. but i'll see if we can't get something worked out so that we can run them on top of both mir or xorg
[18:53] <ogra_> sil2100, https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch looks like it will still be a while til it even starts ... (some admin should bump the build scroe)
[18:56] <ogra_> cjwatson, any chance you could bump that up a little (the system-image importer is off, waiting for that build)
[18:58] <cjwatson> It's probably a lie, but sure
[18:58] <ogra_> just to make sure sil2100 doesnt wait the whole night :)
[18:58] <cjwatson> rescored
[18:59] <ogra_> thanks :)
[18:59] <cjwatson> Latency'll be a bit higher than usual in general while the test rebuild runs, but usually not too bad on armhf
[18:59] <ogra_> ah, that is whats going on ...
[18:59] <ogra_> i was wondering why the publisher is so slow
[19:00] <cjwatson> The publisher shouldn't be any slower than usual; test rebuilds don't affect it
[19:00] <cjwatson> But if you mean the last hour or two, we had some services down while we applied a Launchpad database patch
[19:00] <ogra_> (took 1h for my last livecd-rootfs to show up in proposed)
[19:00] <ogra_> ah, k
[19:00] <ogra_> i'm good at bad timing as usual :)
[19:01] <cjwatson> It's an exciting patch, hopefully you'll see the results in a few weeks :)
[19:03] <ogra_> cool
[19:07] <sil2100> Thanks guys :)
[19:38] <ogra_> rsalveti, another vivid build running, cross your fingers
[19:38] <ogra_> (might choke on gshadow though)
[19:38] <rsalveti> ogra_: :-)
[19:42]  * sil2100 still waits for his rtm image to finish ;p
[19:43] <ogra_> https://launchpadlibrarian.net/197343522/buildlog_ubuntu_vivid_i386_ubuntu-touch_FAILEDTOBUILD.txt.gz
[19:43] <ogra_> as expected :)
[19:43] <ogra_> hmm,, that doesnt look like it used 2.283 at all
[19:44] <ogra_> or it did and i just cant read my own error messages :P
[19:44]  * ogra_ fixes gshadow hash
[19:45]  * davmor2 prods sil2100 repeatedly with the question are we nearly there yet
[19:45] <ogra_> hmm
[19:46] <ogra_> i wonder *why* gshadow actually changed ... there is no GIDs in it
[19:46] <davmor2> ogra_: because it hates us all
[19:46] <sil2100> davmor2: it says it will be done soon
[19:54] <robru> lunch!
[19:55] <jhodapp> rsalveti, due to vivid instability, we need to get a silo with the new media-hub stuff...that's probably best done just by adding a new spreadsheet line right?
[19:56] <jhodapp> rsalveti, for rtm
[19:56] <rsalveti> jhodapp: yeah
[19:56] <rsalveti> normal procedure, but for RTM
[19:56] <jhodapp> rsalveti, cool, thanks
[20:01] <jhodapp> sil2100, can I get a silo for line 77 please?
[20:03] <sil2100> jhodapp: sure :)
[20:03] <jhodapp> sil2100, thanks!
[20:05] <sil2100> jhodapp: hm, it seems it's already assigned to a vivid silo
[20:05] <jhodapp> sil2100, yeah, did you see the comment?
[20:05] <jhodapp> sil2100, we can't properly test in vivid atm, so we need to build and test against rtm
[20:05] <sil2100> jhodapp: yeah, but it means we'll have to free the silo and re-assign to rtm
[20:05] <sil2100> Let me do that
[20:05] <jhodapp> sil2100, that's fine
[20:09] <sil2100> ogra_: ok, it seems the built has finished, can I enable the importer now? :)
[20:09] <ogra_> do you see it on cdimage ?
[20:09] <ogra_> (or in the cdimage www dir on nusakan)
[20:09] <sil2100> ogra_: in the www I see a new image, so I guess
[20:10] <ogra_> you most likkely can, but i usually check that first
[20:10] <sil2100> 20150211.1/
[20:10] <ogra_> sounds fine
[20:10] <sil2100> \o/
[20:11] <ogra_> and the next upload of livecd-rootfs ...
[20:11] <sil2100> Ok, uncommented the last line, let me give a sign on -release
[20:11] <ogra_> this time it shoudl actually build :)
[20:11] <sil2100> Phew ;)
[20:30] <davmor2> sil2100: that's it I'm going now, handing over sanity to ToyKeeper
[20:30]  * ToyKeeper shall be the keeper of the sanity
[20:35] <imgbot> [20:35] <imgbot> [20:46] <rsalveti> ogra_: should we trigger a new imagE?
[20:47] <rsalveti> oh, still in proposed
[20:48] <ToyKeeper> Ah, there it is.
[20:53] <sil2100> o/
[20:53] <sil2100> ToyKeeper: give us a sign how the sanity testing goes :)
[20:53] <ToyKeeper> It's still flashing, but sanity usually goes quickly.  ;P
[20:59] <ToyKeeper> Sweet, recent updates broke adb again.
[21:00] <ToyKeeper> I hope this doesn't delay testing very much.
[21:47] <ogra_> rsalveti, final vivid build running now, this one should get through
[21:48] <rsalveti> ogra_: awesome
[22:29] <rsalveti> ogra_: wtf, failed again
[22:29] <rsalveti> https://launchpadlibrarian.net/197354342/buildlog_ubuntu_vivid_i386_ubuntu-touch_FAILEDTOBUILD.txt.gz
[22:29] <rsalveti> E: Unable to locate package libmirplatform5driver-android
[22:29] <rsalveti> oh crap, new mir
[22:29] <rsalveti> argh
[22:29] <rsalveti> will fix that after I get back from dinner
[22:29] <rsalveti> need to get back the other thread I started last time we had such issue
[22:57] <ogra_> rsalveti, thanks