[00:00] <ogra_> hah
[00:00] <davmor2> but sometimes even :)
[00:00] <ogra_> cjwatson, apps start fine for me on 288
[00:00] <davmor2> ogra_: I like the new indicators I like how it swipes down very swish
[00:01] <ogra_> why doest my mako on 288 have new indicators ?
[00:01] <ogra_> that still hase the old headers here
[00:01] <cjwatson> ogra_: thanks for the confirmation
[00:02] <ogra_> oooh
[00:02] <ogra_> that horrible dots from the launcher are gone
[00:02] <ogra_> wow, this is the first time utopic fells like it is behind
[00:02] <davmor2> ogra_: why do you think I was hugging Saviq earlier
[00:02] <ogra_> haha
[00:02] <ogra_> that was a well deserved hug
[00:03] <davmor2> ogra_: indeed no ugly dots
[00:03] <ogra_> and the icons fold again
[00:03] <ogra_> hmm
[00:04]  * rsalveti back from dinner
[00:04] <sil2100> cjwatson, ogra_: so we should be safe with the new custom tarball and rootfs then, right?
[00:04] <sil2100> On krillin that is
[00:04] <ogra_> sil2100, well, no idea ... i know we are safe on utopic 288
[00:04]  * sil2100 notes down that we need to sync up utopic later
[00:05] <sil2100> ogra_: if it works on utopic, I would say it should be the same on 14.09
[00:05] <ogra_> yeah, but proof is better at this point in time i guess :)
[00:05] <rsalveti> great, new image is out
[00:07] <ogra_> heh, scrolling through my music still gives the thumbnailer some grief
[00:08] <cjwatson> sil2100: I believe so
[00:12] <davmor2> cwayne: oi mr what the hell
[00:13] <cwayne_> davmor2, ?
[00:13]  * cyphermox back from dinner, if I can help with anything
[00:15] <sil2100> davmor2: ?
[00:15] <sil2100> cyphermox: o/
[00:17] <davmor2> sil2100: there is a tiny bit more than expected in the new tarball ;)
[00:18] <sil2100> davmor2: in a good way or bad way?
[00:18] <cwayne_> I totally told you guys there were some new scopes!
[00:18] <davmor2> cwayne: some I'm gonna hurt you yet ;)
[00:19] <cwayne_> davmor2, :P if it helps, just test the dashboard aggregator, that's where all the new ones are aggregated
[00:19] <cwayne_> we just added scopes that go into dashboard and dashboard itself, so if dashboard works, then they all work
[00:29] <ogra_> bah
[00:29] <ogra_> i thought the dash restarting was fixed
[00:29] <ogra_> why do i still see it here ?
[00:29] <sil2100> It should have been long ago
[00:30] <ogra_> well, when starting 20 apps here it still gets respawned
[00:30] <ogra_> i actually thought that was in Saviq's big silo
[00:30] <ogra_> (was that 23 ?)
[00:31] <ogra_> boing ... again
[00:34] <rsalveti> I think that only landed in utopic
[00:34] <rsalveti> not sure yet if that piece went to rtm
[00:35] <sil2100> Wasn't that in the big silo 6 for ubuntu-rtm?
[00:36] <sil2100> davmor2: any ETA on the custom tarball? :)
[00:37]  * cwayne just verified ringtones work
[00:40] <ChickenCutlass> cwayne: what is that ringtone.  Yani
[00:41] <cwayne> ha, stuff from the customer :)
[00:41] <bregma> is it possiblt to sync my desktop-only landings to utopic still?  Ubuntu final freeze is tomorrow and I have a couple critical fixes waiting to be published (silos 28 and 29)
[00:41] <sil2100> bregma: hey! What do you mean by sync?
[00:41] <bregma> I mean publish, that was a mind slip
[00:42] <sil2100> bregma: sure, basically desktop-only sounds a good thing for publishing
[00:42] <sil2100> The big stop of landings is mostly for touch
[00:42] <bregma> I understand, these are definitely touch-free landings
[00:44] <sil2100> bregma: so, are those nux and unity from silos 28 and 29?
[00:44] <bregma> sil2100, yes
[00:45] <davmor2> oh cwayne come here so I can hit you ;)  bug number one with the new code.  Add a task, schedule it for today, tick it so it is completed, is it removed from the dashboard, is it boat ;)
[00:46] <sil2100> bregma: ok, just to make sure - since I remember we're using some small parts of unity7 in our touch images
[00:46] <sil2100> I think that was the -schemas package?
[00:47] <cjwatson> sil2100: OK, I'm off to bed because dear God look at the time.  slangasek should be back in a bit should there be any snags with livecd-rootfs
[00:47] <sil2100> cjwatson: ok :)
[00:47] <sil2100> cjwatson: I'll wait for slangasek here just in case - goodnight and thanks again for everything!
[00:48] <slangasek> hi
[00:48] <sil2100> Yaay, he's back!
[00:48] <slangasek> just sat down at the keyboard a minute ago; getting through scrollback now
[00:48] <sil2100> bregma: so... just want to make sure the shared package with touch didn't get changed
[00:48] <cjwatson> slangasek: summarised briefly for you in /msg
[00:48] <slangasek> ok
[00:48] <bregma> sil2100, the unity -schemas package would have to be manually synched, but there aren't any schema changes so no need
[00:49] <ogra_> sil2100, hmm, so i thought the dash one was a promotion blocker
[00:49] <sil2100> bregma: ok, sounds good
[00:49] <davmor2> sil2100: cwayne: okay so I have run through everything I don't like the new ringtones but they might grow on me,  then there is  that minor niggle with the tasks other than that the tarball looks good
[00:49] <ogra_> sil2100, it clearly didnt land in rtm yet
[00:49]  * ogra_ just dug through the qtmir changes
[00:49] <cwayne> davmor2: hm, when I refresh the scope it's gone
[00:50] <cwayne> and if it's done it should be gone
[00:50] <sil2100> ogra_: hmmm, you checked that? I was almost sure we had a landing for that
[00:50] <sil2100> But maybe that was utopic only indeed?
[00:50] <davmor2> cwayne: it's gone in the app but not in the scope
[00:50] <ogra_> sil2100, it was fixed in qtmir 0.4.4
[00:50] <ogra_> sil2100, which is not in rtm yet
[00:50] <sil2100> Crap
[00:50] <davmor2> cwayne: let me refresh the scope again
[00:50] <cwayne> davmor2: even after a pull-to-refresh?
[00:50] <ogra_> we landed 0.4.3 today
[00:50] <cwayne> it's gone in mine
[00:50] <slangasek> and I see 288 has been tested already, good; also installing it here atm
[00:50] <sil2100> ogra_: anyway, too lat for that now - let's see if QA find it as a blocker too ;/
[00:51] <sil2100> Anyway, it seems there's a +1 on the tarball
[00:51] <ogra_> sil2100, well, it makes using more than ten apps a pretty awful experience
[00:51] <davmor2> cwayne: ah and now it has gone, maybe the backend scope only checks every so often
[00:51] <ogra_> the dash restarts every few mins and steals the focus (which means a black screen saying "scopes")
[00:52] <cwayne> davmor2: :) yeah, I don't know how often it updates itself, i'm a big fan of pull-to-refresh though :P
[00:52] <davmor2> cwayne: that was about the 3rd time I had
[00:52] <cwayne> sil2100: davmor2: so I'm good to press the magic button?
[00:52] <sil2100> ogra_: hm, you think we should do a quick sync of that?
[00:53] <ogra_> sil2100, i have no idea what a quick sync means in terms of stability and other bugs ... in any case that thing is on our promotion blocker list since a while
[00:54] <ogra_> sil2100, https://launchpad.net/ubuntu/utopic/+source/qtmir/0.4.4+14.10.20141013-0ubuntu1 ...
[00:54] <ogra_> that has more than just the one fix
[00:54] <sil2100> Yeah, so what we could do is cherry-picking this fix, preparing a landing for qtmir-14.09, getting it tested and trying pushing it into this image...
[00:54] <slangasek> ogra_, sil2100: ok - someone explain to me why I should not expedite things by kicking off the next ubuntu-rtm build immediately
[00:55] <sil2100> slangasek: we're still discussing one issue that doesn't seem to have been fixed yet ;/
[00:55] <sil2100> https://code.launchpad.net/~unity-team/qtmir/dash-killed-less-likely/+merge/237915
[00:55] <slangasek> sil2100: there will always be more issues.  It takes < 2h to rebuild; do you expect investigation of this new issue to have any real chance of taking < 2h?
[00:55] <ogra_> slangasek, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379296 ... is longstanding on our blocker list and very user visible (as soon as you have some memory pressure the dash gets into the app lifecycle mgmt)
[00:56] <slangasek> right, my concern here isn't that we have all the bugs fixed
[00:56] <slangasek> my concern is that we're serializing things that ought not be serialized under time pressure
[00:56] <sil2100> ogra_: so the change seems fairly simple, but I don't feel confident we have enough upstream people for that to get properly tested
[00:56] <sil2100> ogra_: so let's leave it for an OTA update
[00:56] <cjwatson> qtmir takes 22 minutes to build
[00:56] <cjwatson> on armhf
[00:56] <cjwatson> that's a fair bit of time in an already very tight schedule
[00:56] <ogra_> sil2100, well, your call
[00:57] <sil2100> cwayne: I guess you can publish your custom tarball, and I think slangasek can build a new image
[00:57] <slangasek> ah, the custom tarball isn't published yet?
[00:57] <cwayne> \o/
[00:57] <ogra_> slangasek, so if sil doesnt want to block on it (and QA is fine with that too (it was their call to not promote with that bug)) then just go and build
[00:57] <slangasek> I thought that was to be published at the same time as the apparmor landing, but ok
[00:57] <slangasek> ogra_: I'm not talking about promotions here at all
[00:58] <sil2100> slangasek: no, we just tested it
[00:58] <ogra_> slangasek, turn off the import images cronjob
[00:58] <slangasek> I'm talking about keeping our build pipe full
[00:58] <slangasek> ok
[00:58] <ogra_> slangasek, then you can have one image for rootfs and tarball
[00:58] <ogra_> and dont need to wait for an import run
[00:58] <slangasek> ok
[00:58] <ogra_> cwayne, needs to publish while the rootfs is buuilding indeed
[00:59] <cwayne> uh, i jsut did it
[00:59] <ogra_> well, then it doesnt matter i guess
[01:00] <ogra_> slangasek, but the plan was to have this image promoteable :)
[01:01] <cjwatson> looks like import-images was commented in time :)
[01:01] <ogra_> cool
[01:01] <cjwatson> so we shouldn't get a spurious extra image
[01:01] <slangasek> ogra_: that is not a reason to leave the build pipeline empty if the actual promotable image is > 1.5h out
[01:01] <ogra_> true indeed
[01:01] <slangasek> cwayne: so that means you've published your new tarball to the "gated" url, correct?
[01:01] <cwayne> slangasek: yes
[01:01] <slangasek> ok
[01:01] <slangasek> kicking off a build
[01:01] <cjwatson> oh, possibly we just did
[01:01] <cjwatson> I see image 108 in there
[01:02] <davmor2> Guys I'm off see you at the sprint,  ogra_ sil2100 slangasek if you can ping ToyKeeper and elopio when the final image is up that would be awesom I'm off to bed night
[01:02] <slangasek> ok
[01:02] <slangasek> davmor2: thanks
[01:02] <cjwatson> so probably no point people spending time testing 108 FWIW
[01:02] <sil2100> davmor2: thanks for all your work today!
[01:02] <sil2100> See you next week!
[01:02] <ogra_> yeah, that was an awesome effort davmor2
[01:02] <cjwatson> that's just 107 plus the new custom tarball
[01:02] <slangasek> oh? so the import ran already?
[01:03] <cjwatson> yeah you were slightly too slow
[01:03] <cjwatson> but no worries
[01:03] <slangasek> ok
[01:03] <cjwatson> slangasek: note that (aiui) iso.qa doesn't work for starting 14.09 builds
[01:03] <ogra_> its just numbers :)
[01:03] <slangasek> cjwatson: no problem, I'm old skool anyway ;-)
[01:03] <cjwatson> ok :)
[01:03] <cjwatson> ah, I see it running now
[01:03]  * cwayne needs to take a bit of a break, will be around in a little bit if anyone needs me
[01:04] <cjwatson> right, really off to bed
[01:04] <cjwatson> night
[01:07] <sil2100> cjwatson: goodnight :)
[01:07] <slangasek> ogra_, sil2100, cwayne, ToyKeeper, elopio: so 108 on krillin -proposed is not expected to matter for testing.  109 should be upcoming and will be the version with the updated custom tarball split; it will be available in ~1.5h but is not considered promotable due to known bug #1379296
[01:07] <sil2100> slangasek: yes :)
[01:07] <slangasek> cjwatson: night, and thanks
[01:08] <slangasek> ok
[01:08] <slangasek> now what's the plan for getting bug #1379296 taken care of?
[01:08] <sil2100> slangasek: we know, at least that was our original vision, since 107 was the one without custom, 108 with custom and 109 with custom + the rootfs
[01:08] <ogra_> slangasek, see the bot ;)
[01:08] <slangasek> sil2100: I'm repeating it to make sure everyone involved is on the same page
[01:08] <slangasek> ok
[01:08] <ogra_> silo 012 has the fix
[01:09] <slangasek> sil2100: are you driving this silo?  the train claims you+Saviq, but I don't see Saviq_ speaking up in scrollback :)
[01:09] <sil2100> Yep, just filled that in
[01:09] <ogra_> slangasek, prob is that all upstreams are asleep now ...
[01:09] <sil2100> slangasek: it's his change so I'll ping him to help out
[01:09] <imgbot> [01:09] <ogra_> yay
[01:10] <sil2100> As I'm only the cherry-picking guy, would like him to double check all is ok before we publish
[01:10] <slangasek> sil2100: yeah, but unlike wherever you are, it's the middle of night for Saviq_ so he might not respond ;-)
[01:10] <sil2100> pffff
[01:10] <ogra_> unlike
[01:10] <ogra_> haha
[01:10] <sil2100> We're in the same TZ so he should be here!
[01:10] <slangasek> heh
[01:10] <ogra_> yeah, slacker
[01:10] <slangasek> so, what's actually realistic here?
[01:10] <slangasek> I don't think you're going to get Saviq_ back at 3am
[01:11] <sil2100> Well, I think silo 12 might only be ready for tomorrow, so it won't be in the promoted image anyway, but we might get it in the next one
[01:11] <slangasek> or 4am
[01:11] <ogra_> we can prepare the silo up to the point where QA signs off
[01:11] <ogra_> 3am is right
[01:11] <sil2100> I wouldn't push it forcefully now, but I can get it built and pre-tested so that it's ready for morning
[01:11] <slangasek> is it ok to promote this image with bug #1379296 present?  Who should make that call, olli_?
[01:11] <ogra_> and have Saviq nod it off tomorrow morning
[01:11] <sil2100> slangasek: I usually leave it up to QA to decide, since they will do promotion testing
[01:12] <ogra_> slangasek, promotion is perhaps fine but i dont thinnk we want to gic it to manufacturer in that state
[01:12] <slangasek> and if we're saying silo 12 won't land until morning, and the promotion needs to happen before then, we should surely let QA know to test image 109
[01:12] <sil2100> It's a serious issue, but for instance Selene missed it out when doing the pre-promotion testing on 105
[01:12] <ogra_> *give
[01:12] <slangasek> sil2100: I think this is a product manager call, not a QA call
[01:12] <sil2100> slangasek: well, that's the plan - QA will test 109
[01:12] <ToyKeeper> slangasek: So...  109 won't be promote-able?  Are we going to wait for 110, or send 109 anyway?
[01:12] <ogra_> slangasek, they should test image 109 for sure ...
[01:13] <sil2100> ToyKeeper: I would say we test 109 for promotion
[01:13] <ogra_> and test the silo on top as well
[01:13] <sil2100> But yeah, would be best to have olli_'s decision
[01:13] <slangasek> ToyKeeper: well, this is what I asserted earlier, but now I understand that 110 won't kick off until the morning UTC
[01:13] <slangasek> so there's a call to be made about whether to release to the OEM with this bug outstanding
[01:13] <sil2100> slangasek: from what olli_ mentioned, we're already REALLY tight in our deadline, so waiting for 110 might be a bit impossiblish
[01:14] <ogra_> will the manufacturer get the same OTAs ?
[01:14] <ogra_> or wont they
[01:14] <slangasek> ogra_: olli_ clarified that this is an image we're giving to the OEM now, but it's not the final image going to factory
[01:14] <ogra_> if we can puch a direct OTA (promote a new one right after with only this fix) that could be doable too
[01:15] <ogra_> slangasek, i know that :)
[01:15] <slangasek> ok, so I didn't understand the question ;)
[01:15] <ogra_> slangasek, the question is if they test as is or allow OTAs to happen
[01:15] <slangasek> if they're getting this image, of course they get the same OTA as everyone else ;)
[01:15] <slangasek> right, well, I don't think we control that
[01:16] <sil2100> Let's not get carried away here on this channel guys ;)
[01:16] <ogra_> heh
[01:16] <ogra_> yeah
[01:16] <ToyKeeper> Not really my call, I'll just test 109 and send the results.  Someone else can decide if it's promote-able even with known bugs.
[01:17] <sil2100> ToyKeeper: could you ask elopio for help? It might take less time then
[01:17] <slangasek> ToyKeeper: ok.  In that case, eta for 109 availability remains ~1.5h :-)
[01:17] <slangasek> thanks
[01:17] <sil2100> From what I know jfunk mentioned elopio can help out as well
[01:17] <slangasek> afk for dinner now for a bit; reachable by phone/text if you need me
[01:17] <sil2100> slangasek: ACK :)
[01:17] <ogra_> slangasek, i might go to bed as well then
[01:18] <ogra_> slangasek, in case you need to promote
[01:18] <sil2100> I might be dropping off soon as well
[01:18] <slangasek> ogra_: probably a good idea :)
[01:18] <slangasek> ogra_, sil2100: thanks to both of you
[01:18] <ogra_> slangasek, rtm-promo.log in my home in nusakan has the promotion commands i used for former images
[01:18] <slangasek> ogra_: yep, got it
[01:18] <ogra_> should be easy to deduct from that
[01:18] <ogra_> (as cdimage indeed)
[01:19] <ToyKeeper> sil2100: Yes, elopio is planning to help...  but since we have a while before the image is ready he's doing something else for a while.
[01:20] <ogra_> ToyKeeper, getting silo 012 signed off on top of 109 would be good as well
[01:20] <ogra_> so that we can potentially land it as hotfix in case time permits
[01:21] <sil2100> Not sure if there will be time for that now though
[01:21] <ogra_> indeed
[01:22] <ogra_> anyway, i'm off as well
[01:22] <ogra_> see you tomorrow
[01:22] <ogra_> sil2100, i assume we have a normal meeting ?
[01:24] <sil2100> ogra_: I guess, if I wake up on time ;)
[01:24] <ogra_> heh
[01:24] <sil2100> Anyway, I'll see how much strength I have, I'll try to test te silo once it builds
[01:24] <sil2100> But anyway I'll send out an e-mail to Saviq_ to pick it up from the morning
[01:24] <sil2100> (since it'll be built already)
[01:24] <sil2100> For now I go clean up some silos
[01:35] <sil2100> ogra_, slangasek: I sent an e-mail to Saviq_, so he should be able to pick it up from the very morning
[01:35] <sil2100> I think 3:30 am is the perfect time for sleep
[01:35] <sil2100> Goodnight everyone!
[01:36] <sil2100> o/
[01:48] <robru> Good god y'all
[01:56] <jhodapp> robru, what's going on with my build? https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/36/console
[01:58] <robru> Hm
[01:58] <pmcgowan> jhodapp, just a guess but 2014-10-16 01:55:32,398 WARNING A version (0.7.1+14.10.20141015.1~rtm-0ubuntu1) is available at the destination archive for that component but is not in the destination branch which is still at 0.7.1+14.10.20140926-0ubuntu1. You need to ensure that your version contains the fix in the destination or you can force rebuild to bypass the check.alues (0 6)
[01:59] <jhodapp> pmcgowan, yeah rsalveti is trying that last route
[01:59] <jhodapp> pmcgowan, thanks!
[01:59] <rsalveti> maybe some repo was not merged properly
[01:59] <rsalveti> let me check the repos
[02:00] <rsalveti> we just had one landing for qtubuntu-media a few hours ago
[02:01] <rsalveti> yeah, latest qtubuntu-media in bzr is not the same one that is available in rtm
[02:01] <rsalveti> let me sync that
[02:05] <robru> That exception is really bizarre. Hopefully rsalveti can fix it
[02:05] <jhodapp> rsalveti, hmm, I merged with trunk before pushing
[02:05] <rsalveti> yeah, I think I know what is wrong
[02:05] <rsalveti> jhodapp: trunk is not reflecting latest
[02:05] <jhodapp> oh no
[02:05] <rsalveti> for some reason the branch tvoss created wasn't merged automatically with the landing
[02:05] <robru> rsalveti: oh is there a silo that was published but not merged?
[02:05] <rsalveti> robru: silo is gone already
[02:05] <robru> Ah
[02:06] <jhodapp> crap
[02:06] <jhodapp> so what's the process to remedy this?
[02:07] <rsalveti> jhodapp: manually mergint it
[02:07] <rsalveti> jhodapp: done for qtubuntu-media
[02:07] <jhodapp> ah right
[02:08] <rsalveti> alright, rebuilding
[02:08] <jhodapp> rsalveti, awesome
[02:08] <jhodapp> thanks
[02:08] <rsalveti> that was me aborting the previous build
[02:09] <jhodapp> rsalveti, ok :)
[02:09] <jhodapp> was just going to ask
[02:09] <imgbot> [02:10] <robru> I should probably change that message to say "build aborted" or something...
[02:11] <rsalveti> argh
[02:12] <rsalveti> jhodapp: ^
[02:12] <rsalveti> jhodapp: might need another merge with trunk
[02:13] <jhodapp> ok
[02:17] <jhodapp> rsalveti, try again
[02:18] <rsalveti> alright, now we wait
[02:18] <jhodapp> :)
[02:18] <jhodapp> rsalveti, eating lunch and dinner...only had breakfast today
[02:18] <rsalveti> haha, know the feeling
[02:18] <jhodapp> :)
[02:22] <jhodapp> rsalveti, the thumbnails of the self-recorded videos are still incorrect...it doesn't utilize qtubuntu-media or qtvideo-node as it goes straight to gstreamer
[02:22] <rsalveti> jhodapp: right, how to fix that?
[02:22] <jhodapp> rsalveti, the thumbnailer needs to listen for the same GstTag that media-hub does and do the still image rotation, height/width swap
[02:22] <rsalveti> wrong window
[02:23] <rsalveti> jhodapp: oh, right
[02:24] <jhodapp> rsalveti, it'd be very similar to what I just did
[02:24] <jhodapp> rsalveti, I'll have to bring Satoris/jamesh up on it
[02:24] <rsalveti> right
[02:24] <imgbot> [02:24] <imgbot> [02:25] <rsalveti> guess this one is with latest device tarball
[02:25] <jhodapp> nice
[02:27] <rsalveti> jhodapp: ok, packages are finally building now
[02:27] <jhodapp> excellent!
[02:27] <jhodapp> time to watch some TV while it builds
[02:28] <jhodapp> oh no
[02:29] <jhodapp> rsalveti, same thing with qtvideo-node
[02:30] <rsalveti> the fuck
[02:30] <jhodapp> rsalveti, lol
[02:30] <jhodapp> that definitely should be in sync with trunk
[02:30] <rsalveti> job is still running
[02:30] <rsalveti> https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/40/console
[02:30] <jhodapp> weird
[02:30]  * elopio flashes 109 to start testing.
[02:30] <rsalveti> still building at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-016
[02:30] <jhodapp> good
[02:39] <rsalveti> aborted the latest run so I can rebuild qtvideo-node
[02:39] <rsalveti> but the packages are still building on the ppa
[02:48] <olli_> ToyKeeper, is 109 the candidate?
[02:49] <olli_> jfunk, did someone notify AlexK
[02:49]  * olli_ waves at elopio too
[02:49] <olli_> elopio, ToyKeeper I have some baby bedtime duty but will then stick around
[02:50] <elopio> hello olli_.
[02:51] <ToyKeeper> olli_: We're testing 109, anyway...  even though it doesn't have a fix for https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379296
[02:51] <ToyKeeper> olli_: Whether it gets promoted is someone else's call.  I'll just report results minus that bug.
[02:51] <olli_> ToyKeeper, yeah
[02:52] <jfunk> olli_: I am talking to Alex at this very moment
[02:52] <jfunk> olli_: he knows already
[02:52] <olli_> jfunk, awesome, sending my mail update too
[02:52] <jfunk> olli_: I am about to send a test status update myself :)
[02:52] <jfunk> then ToyKeeper will send one after leo and her are finished
[02:56] <jfunk> olli_: saw some talk earlier in the channel about important stuff and maybe 110 is the candidate
[02:56] <jfunk> can you comment on that?
[02:59] <olli_> I think sil killed that before he left
[03:00] <jfunk> ack, Alex K confirms
[03:00] <olli_> jfunk, if I am not misreading the backlog, then it was about https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379296
[03:00] <jfunk> thx
[03:00] <jfunk> yes
[03:01]  * olli_ doublechecks
[03:01] <olli_> not on the PM list
[03:01] <jfunk> ok
[03:02] <olli_> slangasek, ^ btw
[03:03] <olli_> missed you q earlier
[03:03] <olli_> your
[03:09] <imgbot> [03:12] <slangasek> olli_: "not on the PM list" - well, it was also marked as fixed already, and no one tracked that it wasn't fixed on ubuntu-rtm, fwiw - not that I'm encouraging us to further block the promotion...
[03:18] <jfunk> olli_: about to EOD
[03:18] <jfunk> olli_: anything else you need?
[03:18] <jfunk> elopio: and ToyKeeper will carry the torch for the next hour or two
[03:18] <jhodapp> rsalveti, can you try out silo 16 to see if it rotates for you cleanly?
[03:18] <olli_> jfunk, I think we are good
[03:19] <jfunk> ack nite then
[03:19] <Mirv> morning
[03:19] <jfunk> thanks
[03:19] <olli_> nn
[03:22]  * Mirv catches up
[03:26] <Mirv> ToyKeeper: hey torchkeeper :) assumably nothing goes in atm. are we waiting for anything in particular? 110 just started building, does it have that unity8 lifecycle fix mentioned above?
[03:27] <olli_> slangasek, so, I was reading the backlog again
[03:28] <olli_> not sure why https://launchpad.net/bugs/1379296 is a worry, it seems like it wasn't on the list to start with
[03:28] <ToyKeeper> Mirv: I don't know if it has the fix or not...  I'm busy with 109.  ;P
[03:29] <Mirv> ToyKeeper: ok!
[03:29] <ToyKeeper> This test plan is really quite long though...  will take a while to finish, even with two of us splitting the work.
[03:31] <Mirv> ToyKeeper: keep up the good work, I'll dig up what I need from publish logs etc
[03:39] <elopio> ubuntu-qa, or anybody: where do I report a bug for the facebook app?
[03:42] <ToyKeeper> Hmm...  remind me not to make embarrassing photos/videos when I might need a screenshot for a bug report.  ;P
[03:42] <elopio> I'm guessing webapps-core. There it goes...
[03:48] <olli> elopio, got an ID?
[03:49] <Mirv> olli: the bug was on promotion blocker list earlier, but apparently it somehow missed rtm and landed only in utopic. it's now cherry-picked in silo 12.
[03:49] <elopio> olli: ID for what?
[03:49] <olli> elopio, webapps-core bug
[03:51] <olli> Mirv, ah, promo blocker list
[03:52] <elopio> olli: bug #1381857
[03:53] <olli> elopio, escalated
[03:54] <elopio> olli: do you want us to report here all the bugs we are finding, or do you prefer just to get the summary email?
[03:55] <olli> elopio, ToyKeeper if you don't mind right here, then I can just escalate accordingly
[03:56] <olli> I'll be around for another 2h
[03:56] <elopio> olli:  bug #1377939
[03:57] <elopio> olli: and two minor details:
[03:57] <elopio> bug #1381857
[03:57] <elopio> bug #1381849
[03:59] <elopio> sorry, I repeated the first.
[03:59] <elopio> It's bug #1381860
[04:00] <rsalveti> jhodapp: working for some use cases
[04:00] <rsalveti> jhodapp: not every rotation though
[04:00] <rsalveti> let me record again to make sure
[04:01] <jhodapp> rsalveti, are the times that it doesn't work always reproducible?
[04:02] <rsalveti> jhodapp: just test 90, 180 and 270
[04:02] <jhodapp> rsalveti, what do you mean?
[04:03] <rsalveti> jhodapp: rotating the device at 90, 180 and 270 degrees while recording
[04:04] <jhodapp> rsalveti, ah makes sense...I only support 1 way right now
[04:05] <jhodapp> rsalveti, the real limitation is we really need to get the transformation matrix from the mp4 container all the way to qtvideo-node
[04:06] <jhodapp> rsalveti, but I should be able to convert those other 3 matrices and hard code them for now
[04:07] <rsalveti> jhodapp: right, we kind of only need to handle 4 use cases
[04:07] <jhodapp> rsalveti, yeah, the 4 orientations
[04:07] <jhodapp> rsalveti, that's all that the qtdemux supports anyway
[04:07] <rsalveti> jhodapp: right
[04:08] <jhodapp> rsalveti, but, it will most likely require 3 other new checks in qtdemux and a rebuild of gst-plugins-good
[04:08] <rsalveti> jhodapp: right, just because this feels to be a partial fix
[04:08] <rsalveti> we can land this way still, but the others are also critical
[04:08] <jhodapp> rsalveti, good find though, I must have always recorded things in the same orientation and so didn't notice
[04:09] <rsalveti> 0' is fine
[04:09] <jhodapp> rsalveti, well let's evaluate in the morning...I should be able to quickly add the others pretty easily
[04:09] <jhodapp> I'm brain dead for tonight
[04:09] <rsalveti> 270 as well
[04:09] <rsalveti> 90' and 180' are both wrong
[04:10] <jhodapp> yeah, so a 90' recorded video needs 180 degrees playback rotation
[04:10] <jhodapp> and 180' needs 270'
[04:10] <rsalveti> recording up-side-down (180) makes it really weird :-)
[04:10] <jhodapp> I bet :)
[04:10] <rsalveti> jhodapp: yeah, nothing to be fixed today still
[04:10] <rsalveti> :-)
[04:11] <jhodapp> the horizontal flip matrix that I apply would be weird on the 180 case
[04:11] <rsalveti> yeah
[04:11] <jhodapp> it was a re-crash course on Linear Algebra
[04:12] <rsalveti> nice :-)
[04:12] <ToyKeeper> olli: Oh, telling you about the bugs here? ...  could be a long list.
[04:12] <jhodapp> it's only been 10 years
[04:12] <rsalveti> yeah, same for me
[04:12] <jhodapp> hehe
[04:12] <ToyKeeper> olli: I've been mostly trying to finish tests, queueing up bugs to file later.
[04:13] <olli> ToyKeeper, wfm
[04:13] <ToyKeeper> olli: Anyway...  I got a muted-volume popup in the welcome wizard: http://toykeeper.net/tmp/phablet/2014-10-15/volume-mute-in-wizard.png
[04:13] <jhodapp> rsalveti, alright, I'm going to head to bed so I'm fresh in the morning...I updated ricmm in private message with where I'm at
[04:13] <olli> ToyKeeper, no rush, just go with your flow and share when ready
[04:13] <ToyKeeper> olli: Ringtones are still lagging ~4s behind the screen update for calls, ~6s behind for incoming SMS.
[04:13] <ToyKeeper> olli: It still says 'unconfined' instead of anything useful for permission requests: https://launchpad.net/bugs/1377939
[04:14] <elopio> ToyKeeper: do you know if to receive a push notification an u1 account is needed?
[04:14] <ToyKeeper> olli: Missing unicode chars in country list: https://launchpad.net/bugs/1381849
[04:14] <jhodapp> rsalveti, have a good one!
[04:14] <jhodapp> rsalveti, thanks for the testing help
[04:14] <ToyKeeper> elopio: Not sure, but I think so.
[04:14] <rsalveti> jhodapp: you too, have a good night
[04:14] <ToyKeeper> olli: The music app's "recent" view can still show old info, like deleted playlists.  It doesn't auto-refresh quite right.
[04:14] <elopio> ToyKeeper: no, I got them from twitter. It's just not immediate.
[04:15] <ToyKeeper> olli: The volume notifier widget hides the volume indicator's control: http://toykeeper.net/tmp/phablet/2014-10-15/volume-hides-volume.png
[04:16] <rsalveti> indeed
[04:16] <ToyKeeper> olli: Videos from the camera show up in the gallery with a date from the future: http://toykeeper.net/tmp/phablet/2014-10-15/videos-from-the-future.png
[04:16] <rsalveti> besides the annoying volume notification on the wizard
[04:16] <ToyKeeper> (but file timestamps are correct)
[04:16] <ToyKeeper> olli: New camera photos show up in the photoroll with a date 8 hours in the future (and I'm in UTC-6, WTF): http://toykeeper.net/tmp/phablet/2014-10-15/photos-from-the-future.png
[04:17] <ToyKeeper> olli: Same shot as above, full-res main camera pics get a black thumbnail in the photoroll preview (but correct thumbnail in the carousel).
[04:17] <ToyKeeper> olli: New photos and videos from the camera aren't shown in scopes until after a new search is made, or a reboot.  (no auto-update based on a new file appearing)
[04:17] <ToyKeeper> olli: The facebook app bug elopio reported: https://launchpad.net/bugs/1381857
[04:18] <olli> ToyKeeper, wow
[04:18] <ToyKeeper> olli: ... on initial login, it can take 5+ seconds to load app icons.
[04:18] <ToyKeeper> olli: The Gallery 'Album' view header covers part of the top image: http://toykeeper.net/tmp/phablet/2014-10-15/album-header-covers-top-photo.png
[04:18] <ToyKeeper> olli:  ... and that's everything so far.  Need to pick a new section of the test plan to start on now.
[04:19] <ToyKeeper> (started with multimedia by request)
[04:20] <ToyKeeper> Right, Scopes are next.
[04:20] <elopio> ToyKeeper: bug #1378618
[04:21] <olli> ToyKeeper, ok, I'll go through the list and where/when you have bugs i can help prioritize
[04:21] <elopio> ToyKeeper: bug #1378618
[04:22] <ToyKeeper> elopio: Thanks!  I noticed that bug too: http://toykeeper.net/tmp/phablet/2014-10-15/volume-hides-volume.png
[04:22] <elopio> sorry, it got sent twice. ToyKeeper: from that bug, the bubble shouldn't appear when the indicator is open.
[04:23] <elopio> but at least now they made it a different color. It used to look worse
[04:26] <elopio> ToyKeeper: for the slow icons on the dash, Saviq pointed to this bug #1379381
[04:26] <elopio> but I think it's a little different.
[04:26] <elopio> if you report it, please add a comment on that bug so Saviq knows there's a new one related.
[04:31] <rsalveti> ToyKeeper: did you open the one that shows the volume indicator on the wizard?
[04:31] <ToyKeeper> rsalveti: To get test results faster, I'm queueing up bugs to file after I send the report...  not filing them as I find them.
[04:31] <rsalveti> ToyKeeper: alright, but is this one in your list?
[04:31] <rsalveti> if so will just let you open it
[04:32] <ToyKeeper> rsalveti: Yes, it's on my list.  I don't mind if you get to it first though...  just remember to send me the link.  ):
[04:32] <ToyKeeper> :) even
[04:32] <rsalveti> sure
[04:33] <elopio> I can't find where to add a reminder in the reminders app.
[04:33] <elopio> Am I blind?
[04:34] <olli> wasn't the new tarball supposed to add the new dashboard scope
[04:34] <olli> cwayne^
[04:34] <ToyKeeper> Ah, that's what the "big change" was about?
[04:35] <olli> duno
[04:35] <rsalveti> I got it here
[04:35] <rsalveti> swipe to the left
[04:35] <olli> found it, didn't --wipe so I guess it's not first one by default
[04:35] <rsalveti> could be
[04:35] <rsalveti> flashed with bootstrap here
[04:41] <rsalveti> ToyKeeper: please confirm: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1381871
[04:43] <ToyKeeper> rsalveti: Done.
[04:44] <rsalveti> ToyKeeper: thanks
[04:52] <ToyKeeper> olli: The default 'Ring' ringtone isn't selectable, so after changing it to something else the user can't go back to default.  (then again, the default is terrible anyway)
[04:52] <olli> :)
[05:00] <ToyKeeper> olli: After setting a new ringtone, it doesn't take effect until the next boot.  :(
[05:00] <olli> ToyKeeper, :/
[05:01] <ToyKeeper> olli: I also somehow managed to break the proximity sensor during one boot, but haven't been able to reproduce the issue.
[05:01] <olli> sorry, seem like I am replying in emoticons
[05:03] <elopio> ToyKeeper: olli: two more small issues
[05:03] <elopio> bug #1381872
[05:03] <elopio> bug #1381874
[05:04] <elopio> the last one should be probably for the flickr scope, but I can't find the project.
[05:04] <olli> elopio, will check
[05:04] <olli> elopio, I squashed as invalid https://bugs.launchpad.net/webapps-core/+bug/1381860
[05:05] <elopio> olli: I made posts on facebook with the cancel account on the bottom.
[05:05] <elopio> s/account/button
[05:05] <ToyKeeper> olli, elopio: Two boots in a row, the proximity sensor stopped working after a few calls.  :(
[05:06] <olli> interesting
[05:06] <elopio> on twitter you are right, the button disappears.
[05:06] <elopio> I'll retry on facebook
[05:07] <olli> ToyKeeper, seems to be gone here too
[05:08] <ToyKeeper> Dead prox sensor is probably a priority.  :(
[05:08] <slangasek> olli: oh; you're right, it wasn't, I misread the tags on the bug before
[05:09] <elopio> olli: bug #1381860 back to new with a screenshot.
[05:09] <olli> ToyKeeper, cancel that, did 6 calls in a row with working proximity sensor
[05:09] <olli> elopio, hah
[05:09]  * olli shakes fist
[05:10] <olli> I was so proud...
[05:10] <olli> ;)
[05:11] <elopio> mess with the best, die like the rest... ;)
[05:15] <elopio> olli: ToyKeeper: should I test maps, even if I won't get the accurate fix ?
[05:15] <elopio> or are we planning to retry the location service landing before delivering the image?
[05:17] <olli> elopio, my understanding according to tvoss is that you get a fix within 10sec
[05:17] <olli> just a bit slower
[05:17] <olli> but I might be wrong
[05:18] <olli> elopio, tvoss should come on not before too long, maybe push back and test something else meanwhile
[05:18] <Mirv> my understanding was that without 004 the GPS is not wired correctly to be a location provider, so it doesn't work
[05:18] <elopio> olli: I'll try.
[05:18] <olli> elopio, I'd suggest to confirm with tvoss before spending time
[05:18] <elopio> Mirv: that's what I thought too, but I didn't try outside without the silo.
[05:18] <Mirv> one gets a "fix" ie approximate location, but it doesn't follow except for those cell id based hops
[05:19] <elopio> olli: ok. Many other things to test anyway. tvoss: please ping when you get back.
[05:20] <ToyKeeper> It really sounds like the number of "not landed yet" functions means this image can't get promoted.
[05:20] <ToyKeeper> 110 perhaps?
[05:21] <Mirv> ToyKeeper: #110 is already building without changes. I think there's nothing in the landing queue that has absolutely been decided is going to land, though, but there are candidates...
[05:22] <Mirv> if #109 has no new blockers, then it may be promoted for real
[05:22] <Mirv> even with the known things that are lacking
[05:23] <olli> https://launchpad.net/bugs/1381857
[05:23] <olli> https://launchpad.net/bugs/1381871
[05:23] <ToyKeeper> Well, the test plan for it is certainly thorough.  Big change from the older manual test plan we used last time I was doing that regularly.
[05:23] <olli> these 2 are the ones I am worried about
[05:28] <Mirv> elopio: how did you test the rtm-004 btw? are there instructions somewhere on how to upgrade lxc-android-config (which fails to unpack when using apt to upgrade to it)?
[05:28] <elopio> Mirv: yes, on the location-service test plan there's a link
[05:29] <elopio> https://wiki.ubuntu.com/Touch/Testing/lxc-android-config
[05:29] <Mirv> elopio: thanks!!
[05:31] <elopio> olli: ToyKeeper: bug #1381876
[05:31] <elopio> unable to reproduce it, though.
[05:34]  * olli tries
[05:37] <olli> can't reproduce
[05:41] <olli> elopio, ToyKeeper, how far in are you in your testing? just so I get a feel of what's still ahead and whether or not to get the coffee maker going
[05:43] <ToyKeeper> Well, that's going to take a while to recover from...  my notebook just spontaneously shut itself off.  (I normally only reboot once per Ubuntu release, and usually have like 200 windows open... so this is pretty disruptive)
[05:45] <olli> urgs
[05:48] <elopio> olli: according to the report, there are 22% of the tests not executed.
[05:49] <olli> ok
[05:49] <elopio> olli: some of the executed ones are from #106. I don't know how to get a number about how many.
[05:49] <olli> so ~1/4 left
[05:49] <elopio> olli: well, if we want to run all on 109, more like 1/2
[05:49] <olli> elopio, /me is really just trying to figure out whether to go to bed ;)
[05:50] <olli> elopio, that is a decision I won't impact, your call, have not been involved in that discussion so I don't think I can help
[05:50] <elopio> olli: tbh, I'm not sure why you are awake :) why don't you go to sleep for a while and get back when the report is ready?
[05:50] <ToyKeeper> olli: Some of the tests were executed on 106 though, not 109.  So, the percent not run yet is higher.
[05:50] <olli> elopio, I am triaging as you file
[05:50] <olli> hoping that victorp or so can take over once awake
[05:51] <olli> but mostly also to provide you mental support ;)
[05:51] <elopio> olli: I know. But we don't find that many bugs. If you do it all at once, it won't take 30 minutes, I think.
[05:51] <ToyKeeper> This test plan is huge...  three people working on it and it's still only about half done.
[05:52]  * elopio dances to The Smiths while testing, for mental support :D
[05:53] <olli> :)
[05:53] <olli> mental/moral
[05:54] <olli> trying to declare your bugs and hard work as invalid... and failing to do so...
[05:54] <olli> you know, that whole motivational thing we mgrs do ;)
[05:58] <ToyKeeper> I still think it's weird that we call it a feature instead of a bug that the user can reply to text messages while the phone is locked.
[05:59] <elopio> olli: It's appreciated. I'm just saying that if you want to sleep, we won't mind and it won't affect the process too much.
[05:59] <olli> ;)
[06:05] <ToyKeeper> elopio: Did you run into any difficulties adding online accounts?  I'm getting an immediate abort while trying to add a google account.
[06:06] <ToyKeeper> elopio: ... just like the facebook account add sometimes does.
[06:06] <ToyKeeper> (and is also currently doing, d'oh)
[06:06] <elopio> ToyKeeper: I'm having problems adding the google one because the confirmation message can take 15 minutes and if the phone locks, the app is closed and I have to restart.
[06:06] <elopio> but I could add the facebook, twitter, u1, flickr and reminders.
[06:07] <ToyKeeper> I've seen this a lot in the past few images...  like last night.  Couldn't add a facebook account without rebooting first (and sometimes it takes more than one boot).
[06:08] <elopio> ToyKeeper: I haven't seen it. But if your window closes, you should get a crash or something on the log, right?
[06:09] <ToyKeeper> elopio: I'm not seeing anything in /var/crash which looks related.
[06:09] <ToyKeeper> Some boots it works, others it doesn't.  I haven't found a way to make it work after failing, aside from a reboot.
[06:10] <ToyKeeper> When it doesn't work, it spins for a few seconds to load the browser and then it immediately aborts and goes back to whatever invoked the add-account action.
[06:13] <olli> elopio, ToyKeeper, alright, I just send a status with what i have gathered from you
[06:13] <tvoss> good morning
[06:13] <olli> will lay down for a few hours, hope to be back in ~5-6h
[06:14] <elopio> ToyKeeper: what should I do if the phone just freezes? media-hub is consuming all the cpu after I opened the camera.
[06:14] <elopio> olli: bye. See you tomorrow.
[06:14] <ToyKeeper> elopio: Is apport doing anything?  Did unity8 crash?
[06:14] <olli> thanks for your late night shift ToyKeeper & elopio!
[06:15] <ToyKeeper> elopio: Definitely a bug, but...  the details from there depend on what you can find out.
[06:15] <elopio> tvoss: hey. I was wondering if I should run the maps tests on image #109 even if the location services didn't land. Or are we planning to get a new image, so I better wait.
[06:15] <ToyKeeper> elopio: Er, is the facebook app installed by default for you?  I didn't get it with the base image.
[06:15] <elopio> ToyKeeper: I don't see any recent crashes.
[06:15] <tvoss> elopio, you can test location without silo 4
[06:15] <elopio> ToyKeeper: yes, I have it.
[06:15] <tvoss> elopio, have to prepare breakfast, with you in a few
[06:16] <ToyKeeper> Okay, so when I flashed 109 I didn't get the facebook app, didn't get the dashboard scope, may have had other stuff missing too.  That worries me.
[06:17] <elopio> ToyKeeper: it finally opened the camera. But media hub is still 97% of the CPU.
[06:19] <ToyKeeper> D'oh, I can't check the scrollback for my flash process because it died when my notebook shut itself off.
[06:19] <elopio> ToyKeeper: maybe you missed the --wipe.
[06:20] <ToyKeeper> Nope, --wipe is always included.
[06:21] <ToyKeeper> Hmm, my UI locked while going back to the main app scope after installing an app.  Got stuck like this until I turned the screen off/on: http://toykeeper.net/tmp/phablet/2014-10-15/back-from-store.png
[06:24] <elopio> ToyKeeper: I got something similar while opening the camera. But I couldn't turn the screen off.
[06:25] <elopio> ToyKeeper: I reported bug #1381893, but I don't think it was the cause. Now I can open the camera and media hub is still on fire.
[06:26] <ToyKeeper> Hmm, File Manager is missing too.
[06:26] <elopio> ToyKeeper: I don't have filemanager.
[06:27] <ToyKeeper> elopio: I haven't seen media-hub freak out on 109 yet, even while opening the camera.
[06:27] <elopio> it's in the store though. Maybe the moved it.
[06:27] <ToyKeeper> File Manager should probably be included by default though...  and it's a default source for pretty much any mime-type.
[06:27]  * ToyKeeper reflashes to check if the missing apps are reproducible
[06:27] <elopio> I agree.
[06:37] <elopio> Chipaca: are you online? are we supposed to get notifications when the gmail account receives a message?
[06:39] <elopio> I'm going to have dinner. bbs.
[06:40] <seb128> on rtm 109, I played a video once and now it doesn't work anymore, is that a known issue?
[06:41] <ToyKeeper> seb128: Weird, I played a bunch of videos and it was fine...
[06:41] <ToyKeeper> seb128: Not a known issue.
[06:41] <seb128> k
[06:41] <seb128> I played it from the gallery, so maybe it's due to that or maybe an unlucky try
[06:41] <ToyKeeper> Oh, could be...  I only tried one in the gallery.
[06:41] <seb128> the video comes from the camera app
[06:45] <ToyKeeper> elopio: So...  after reflashing, I have 7 apps which weren't there the first time I flashed 109.  I wonder if I did the first flash before it had finished uploading parts of the image.
[06:46] <ToyKeeper> elopio: The 7 apps were: Amazon, eBay, Facebook, Gmail, Reminders, Tasks, Twitter.  (notice a pattern?)
[06:46] <ToyKeeper> File Manager is still notably missing.
[06:47] <elopio> I have all of them, except file manager.
[06:48] <ToyKeeper> Oh, the reflash also added the dashboard scope.
[06:48] <elopio> I also had that since the first flash.
[07:24] <tvoss> good morning
[07:25] <tvoss> seb128, known issue, fix for mediaplayer app is in rtm silo 6
[07:27] <seb128> tvoss, hey, thanks
[07:27] <tvoss> seb128, https://bugs.launchpad.net/mediaplayer-app/+bug/1376467
[07:28] <slangasek> elopio, ToyKeeper: so does 109 check out?  sounds like you've run into some problems, but did these resolve themselves on reflash?
[07:29] <slangasek> for the record, File Manager is missing because it's not on the list of click apps that are supposed to be included; if there's functionality that depends on it being present, this may need re-evaluated
[07:29] <ToyKeeper> slangasek: This test plan is quite long...  am in the middle of handing it off to .eu timezone folks to finish.
[07:29] <slangasek> ok
[07:30] <slangasek> then I'll likewise hand back off to .eu for handling the promotion :)
[07:30] <slangasek> ogra_, sil2100: ^^ morning - promotion not yet done, tests in progress, tag you're it
[07:30] <Mirv> ;)
[07:30] <ToyKeeper> :w
[07:30] <ToyKeeper> ... wrong window.
[07:32] <seb128> slangasek, is that list somewhere public?
[07:33] <slangasek> seb128: no
[07:34] <seb128> k :/
[07:35] <ToyKeeper> Not sure why, but results have only been going to a list of Cc'd recipients so far.  In case there's a good reason, I didn't Cc any mailing lists with my summary.
[07:35] <slangasek> ToyKeeper: well, either you get questions from random managers because you did cc: us, or you get questions from random managers because you didn't... pick your poison ;-)
[07:40] <ToyKeeper> Gah!  Well, the good news is I figured out why my notebook spontaneously shut itself off...  the bad news is that something inside seems to short whenever I move it.  :(
[07:43] <ogra_> *yawn*
[07:45] <ogra_> slangasek, did anyone think about asking the lab guys to remove the tests for the non-shipped apps on krillin ?
[07:47] <ogra_> hmm, seeing the test results that obviously not the case
[07:49] <sil2100> o/
[07:49] <ogra_> moin
[07:49] <sil2100> Any good news?
[07:49] <ogra_> not yet i thinnk
[07:49] <ogra_> sil2100, we also forgot to ask paul to remove the tests for all the removed click apps from smoketesting
[07:50] <sil2100> Ah, right... but when I poked him later that night he wasn't responsive anyway
[07:50] <ogra_> ok
[07:50] <ogra_> well, we should hand them a list ...
[07:52] <ogra_> sil2100, i assume you are on ToyKeeper's CC list (i am not) and should know more about the status than me btw :)
[07:53]  * ogra_ re-installs filemanager and terminal
[07:59] <Mirv> sil2100: so the testing has been handed over to our timezone QA people
[07:59] <ogra_> which is only brendand today
[08:00] <ogra_> seb128, iirc there is a bug open (and silo available) for mediaplayer only playing a video once
[08:01] <Mirv> I don't think there was a clear decision on landing 012 if we'd build a new image. tvoss is probably looking at the 004 issues anyway. 005 and 006 are possible landing candidates for known issues.
[08:01] <ogra_> something about the url not being rewrittem
[08:01] <seb128> ogra_, yeah, cf tvoss' reply a bit earlier
[08:01] <tvoss> Mirv, yup, looking at 4
[08:01] <brendand> ogra_, well jibel is also there
[08:01] <ogra_> seb128, oop, 5h sleep dont serve me well :P
[08:01] <ogra_> brendand, oh, right
[08:01] <seb128> ogra_, too much sleep right?
[08:02] <ogra_> definitely :P
[08:03] <jibel> good morning :)
[08:05] <sil2100> Morning!
[08:05] <sil2100> All in all, I guess we first need to address the big 2 blockers on the list from QA
[08:05] <sil2100> Saviq: hey!
[08:06] <sil2100> brendand, jibel: did you guys already pick up the testing? How much more time do you need to finish up?
[08:09] <sil2100> Mirv: anyway, I would concentrate on pushing on the blockers, trying not to land anything besides those
[08:09] <sil2100> Well, strange that QA didn't find the qtmir unity8-dash restarting bug as a blocker btw.
[08:13] <ogra_> sil2100, you only hit it if you open many ram-hungry apps
[08:13] <sil2100> elopio: are you still around?
[08:14] <sil2100> We would need someone addressing mardy's comments on bug LP: #1381857
[08:14] <ogra_> not sure if we have a test that would make you reach the condition where lifecycle mgmt kicks in
[08:15] <sil2100> ogra_: true...
[08:15] <ogra_> (that requires quite a few apps to be open or to have them long running)
[08:16] <jibel> sil2100, which bug # is it?
[08:17] <ogra_> jibel, http://people.canonical.com/~lzemczak/issues/
[08:17] <ogra_> the second one
[08:17] <jibel> ah ok, thanks
[08:18] <sil2100> Anyway, looking a the list I would only consider the facebook one as a real potential blocker
[08:18] <sil2100> The volume-up issue looks to me more like an annoyance
[08:18] <sil2100> seb128: who's the main person responsible for the wizard in system settings?
[08:19] <ogra_> mterry
[08:19] <sil2100> So no one from our TZ?
[08:19] <ogra_> sil2100, whats the "volume up issue" ?
[08:19]  * ogra_ has the feeling you have a buglist
[08:19] <sil2100> ogra_: let me forward you that
[08:20] <ogra_> thx :)
[08:20]  * sil2100 wonders why olli sent the list to single people and not any ML
[08:20] <sil2100> ...even though it's part of my thread which was sent out to phablet and ue-leads
[08:20] <ogra_> ue-leads ... argh
[08:21] <sil2100> Well, this one wasn't sent out there though
[08:21] <sil2100> Just single people were CCd
[08:21] <ogra_> obviously not answered via phablet then
[08:21] <Mirv> sil2100: those new blockers AFAIK only considered new findings during the image testing
[08:21] <ogra_> (which would really have been helpful since many people watch and wait )
[08:21] <seb128> sil2100, mterry and Cimi
[08:22] <sil2100> seb128: thanks!
[08:22] <seb128> sil2100, I can probably help having a look if needed, it's in settings in some way
[08:22] <Mirv> sil2100: I'm not sure still if the 012 (qtmir/unity out-of-mem) was properly considered or not. 005 and 006 probably missed the deadline more simply, and 004 would need another management decision if it would be first fixed and then verified (after all GPS would be nice to have of course)
[08:23] <Mirv> sil2100: but I think the biggest question mark is if 012 should be included
[08:23] <Mirv> and then the new blockers
[08:23] <sil2100> Mirv: yeah, well, normally if QA doesn't find an issue with this during promotion testing, it shouldn
[08:23] <sil2100> 't
[08:23] <sil2100> Since basically IMO we should only consider fixing new blockers, as slipping in anything else is regression potential
[08:24] <sil2100> And if we decide we don't promote this image (109), then it means we loose another 8 hours
[08:24] <sil2100> + time needed to fix the issues pointed out
[08:24] <sil2100> And that's *bad*
[08:24] <Mirv> sil2100: I agree. I just would have liked to have it clearly pointed out that 012 is _not_ wanted :)
[08:24] <sil2100> Since if the new image has *new* regressions, the we're basically, saying it bluntly, fucked ;)
[08:24] <Mirv> not that I've any e-mail / list either so I don't actually know
[08:25] <ogra_> yeah, that should really have gone to phablet
[08:25] <sil2100> Mirv: oh, right, you didn't get this as well
[08:25]  * sil2100 wonders if he should forward it to phablet@
[08:25] <sil2100> I think I should
[08:25] <ogra_> sil2100, cant you just forward it to phablet ?
[08:25] <sil2100> Let me do it
[08:25] <ogra_> hah
[08:25] <Mirv> I did see on IRC that 1381857 and 1381871 were considered worrying
[08:25] <ogra_> *snap*
[08:25] <ogra_> :)
[08:26] <Mirv> and then of course the testing is not fully finished
[08:26] <popey> bug 1381857
[08:27] <popey> bug 1381871
[08:27] <ogra_> funny that nobody thinks that the volume thingie is having no top margin is a UX bug
[08:28] <sil2100> Mirv: yeah
[08:28] <sil2100> Mirv, popey, ogra_: ok, so I forwarded the e-mail to phablet
[08:28] <ogra_> thanks !
[08:28] <seb128> sil2100, popey, ogra_, is that a new issue?
[08:28] <ogra_> seb128, well, the volume UI wasnt in anything yet
[08:28] <ogra_> i think it only entered rtm yesterday
[08:29] <sil2100> seb128: so, olli marked bug 1381871 as a potential blocker - not sure about that, but maybe we could have someone looking at that before we get the final assessment
[08:29] <cjwatson> what's all this stuff about filemanager et al not being installed on upgrade?
[08:29] <ogra_> cjwatson, thats on purpose, no ?
[08:30] <cjwatson> at least some of the apps mentioned were meant to be in the new custom tarball
[08:30] <ogra_> filemanager and terminal are not in the krillin custom tarball
[08:30] <cjwatson> ok not filemanager
[08:30] <cjwatson> but Selene mentioned amazon, ebay, ...?
[08:30] <sil2100> hm
[08:30] <ogra_> (and possibly more, these were the two i noticed)
[08:30] <popey> where was the discussion about which apps are in the tarball?
[08:30] <cjwatson> 07:45 <ToyKeeper> elopio: So...  after reflashing, I have 7 apps which weren't there the first time I flashed 109.  I wonder if I did the first flash before it had finished uploading parts of the image.
[08:30] <sil2100> cjwatson: from the e-mail I have from ToyKeeper, she said that filemanager is missing only
[08:30] <cjwatson> 07:46 <ToyKeeper> elopio: The 7 apps were: Amazon, eBay, Facebook, Gmail, Reminders, Tasks, Twitter.  (notice a pattern?)
[08:30] <popey> I saw a mail from steve this morning
[08:30] <cjwatson> sil2100: ah, ok
[08:31] <sil2100> hmmm
[08:31] <popey> but not where it was discussed.
[08:31] <ogra_> sil2100, then she missed the terminal missing ;)
[08:31] <cjwatson> popey: not so much discussed as instructed.  https://bugs.launchpad.net/barajas/+bug/1367332
[08:31] <cjwatson> afaik it was the product team
[08:31] <sil2100> cjwatson: she sent out the e-mail at 9:00, so I guess the e-mail should be more up-to-date ;p
[08:31] <cjwatson> ok cool
[08:31]  * sil2100 hopes so at least
[08:31] <popey> ok
[08:32] <sil2100> ogra_: but you did an OTA as well right?
[08:32] <ogra_> yep
[08:32] <john-mcaleely> there is a testplan in Barajas about what should be in the krillin tarball
[08:32] <john-mcaleely> that's not (yet) a public document
[08:32] <sil2100> Oh, meeting!
[08:32] <ogra_> yup :)
[08:33] <Mirv> :)
[08:37] <Chipaca> elopio: i am online now
[08:38] <Chipaca> elopio: you are supposed to, but you need to set it up (last time i checked the gmail webapp wasn't using online accounts, so you needed to create an online account for the notifications)
[08:44] <brendand> Chipaca, elopio went offline, if it's about a bug you can follow up with me or jibel
[08:45] <Chipaca> brendand: all i have is a question from him
[08:45] <brendand> Chipaca, what was it?
[08:45] <Chipaca> elopio> 08:38:09> Chipaca: are you online? are we supposed to get notifications when the gmail account receives a message?
[08:46] <brendand> Chipaca, right - and the answer is 'yes' if you enabled it
[08:47] <Chipaca> brendand: only if the UOA-enabled gmail webapp didn't land
[08:47] <popey> ogra_: just OTA'ed my n7 and n4 and they're both sat at the Google logo
[08:47] <Chipaca> brendand: if it did, then you needn't enable it any more
[08:48] <tvoss> sil2100, do you have rtm 23 under consideration still?
[08:48] <brendand> Chipaca, well you need to allow the app to access the account
[08:49] <Chipaca> brendand: yes
[08:49] <brendand> Chipaca, i tested that landing so i know how it works - i wonder what issue he was having with that
[08:49] <Chipaca> i guess we'll never know :)
[08:49] <Saviq> sil2100, I'm on it
[08:50] <Saviq> FWIW that bug was not marked for landing 10/16... that's the only reason it didn't land in rtm...
[08:51] <popey> ogra_: I can't adb shell in... it doesn't show up in adb devices...
[08:52] <Chipaca> brendand: maybe we should all go visit elopio after washington.
[08:52] <ogra_> john-mcaleely, i only use about 5 apps constantly ... but if one is dekko and the other is the browser you get it quite a lot
[08:52] <ogra_> popey, works here, is developer mode enabled ?
[08:53] <popey> ogra_: dunno, but I can't tell now can I, stuck at the google logo
[08:53] <popey> might be apparmoring
[08:53] <popey> but it's been a while
[08:53] <ogra_> popey, well, then you cant get into adb
[08:53] <popey> more than 30 mins
[08:53] <popey> no, i mean it _might_ be enabled, but I can't tell
[08:53] <ogra_> popey, in the next iteration adb is supposed to check the screen state before letting you in ... thats why it is required to wait til the session has started
[08:53] <Saviq> trainguards, reconfigure rtm silo 12 please
[08:54] <Saviq> added the qtmir-gles sync MP
[08:54] <Mirv> Saviq: ok
[08:54] <john-mcaleely> ogra_, yeah. telegram is my main 'app', and that's still not huge usage yet
[08:54] <john-mcaleely> (time-wise on the phone)
[08:55] <ogra_> yeah, definitely
[08:55] <Mirv> Saviq: done
[08:56] <ogra_> popey, in case you want to debug: http://paste.ubuntu.com/8538169/
[09:02] <sil2100> Saviq: thanks! :)
[09:03] <sil2100> You're the man! Saviq we still don't know if this is a blocker or not, but if we prepare it we'll at least be ready for this eventuality
[09:04] <tvoss> sil2100, nagging ping for rtm 23?
[09:04] <Saviq> sil2100, truth be told I should've included it in the landing yesterday, just got  too clingy to the 10/16 list probably...
[09:04] <ogra_> if it wouldnt be so visible when you actually use the phone i would say lets whitelist it and quickly push for an OTA image with the fix
[09:04] <popey> ogra_: /sbin/sh: can't create /cache/system/etc/init/android-tools-adbd.override: nonexistent directory
[09:04] <ogra_> popey, err, did you mount it ?
[09:04] <sil2100> Saviq: yeah, I guess it was also our mistake we forgot about to tell about it to Victor and Olli
[09:04] <popey> ogra_: http://paste.ubuntu.com/8572954/
[09:05] <sil2100> Saviq: since then it would get bumped to critical rtm14 for sure
[09:05] <Saviq> sil2100, not sure if that's known: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1381871/comments/3
[09:05] <sil2100> tvoss: hey! We're still on hold sadly, waiting for all testers to finish
[09:05] <ogra_> popey, well, it doesnt appear to be mounted ... weird, i tested these instructions
[09:05] <sil2100> Saviq: yes, it's one of the possible blockers as per the list olli sent
[09:06] <Saviq> sil2100, yeah I just added a finding, it seems it's indeed the wizard triggering volume changes
[09:06] <ogra_> Saviq, you mean you can fill your screen with the bubbles ?
[09:06] <Saviq> ogra_, no, there's only ever one
[09:06] <sil2100> seb128: ^
[09:06] <Saviq> ogra_, but triggered multiple times
[09:07] <ogra_> ah
[09:07] <ogra_> sounded like you add one with every back/forth
[09:07] <popey> /dev/block/loop0 on /cache/system type ext2 (rw,relatime,errors=continue)
[09:07] <popey> already mounted?
[09:07] <ogra_> popey, well, then you shoudl see any content in there
[09:08] <popey> surely I can't be the only one like this?
[09:08] <ogra_> unless your rootfs image is completely empty
[09:08] <popey> (I have two devices that did this)
[09:08] <ogra_> df -h
[09:08] <ogra_> ?
[09:08] <popey> /dev/block/loop0          1.9G      4.0K      1.8G   0% /cache/system
[09:08] <ogra_> bah
[09:08] <ogra_> that looks broken indeed
[09:08] <popey> ☹ it was cleanly flashed / wiped only 2 days ago
[09:09] <ogra_> was that rtm or utopic ?
[09:09] <jibel> ogra_, which scopes did you enable and which apps are running when you get bug 1379296 ?
[09:09] <ogra_> (its a mako, right ? )
[09:09] <popey> ogra_: rtm
[09:10] <ogra_> jibel, well, typically i have the browser, two or three webapps, dekko and G+ open ... open a graphics intense page in the breowser or a news webapp with videos on it that you play and it starts
[09:10] <ogra_> from then on it will happen regulary
[09:11] <ogra_> jibel, you see when the app lifecycle management kicks in if the app previews in the right swipe look a bit blurry
[09:12] <jibel> ogra_, okay. I hit it very frequently on earlier builds with only a few apps open but the situation is much better now. I'll try with more apps and more resource consuming webpages
[09:12] <ogra_> jibel, just starting many apps and switching between them should trigger it too ... you just need to get the memory pressure high enough (which happens by duration or by mass)
[09:12] <jibel> ogra_, yeah, I know the symptoms
[09:14] <seb128> sil2100, yes?
[09:14] <ogra_> jibel, i guess adding a bunch of scopes will also triger it ... and i can imagine that presenting scopes is one major part here
[09:14] <ogra_> (for this image i mean)
[09:14] <jibel> ogra_, right I could reproduce with the photo scope and 50 photos in it. But cannot anymore
[09:15] <ogra_> inetersting ...
[09:15] <ogra_> i only have dekko G+ and a news app open (well, since 2h ) and switching between apps triggers it easily for me
[09:15] <jibel> ogra_, also just opening Euronews was enough to kill the device
[09:15] <ogra_> wow
[09:17] <sil2100> Sounds like a blocker to me
[09:18] <ogra_> sil2100, i think jibel meant "before"
[09:18] <sil2100> Ah
[09:18] <sil2100> hm
[09:18]  * sil2100 needs some coffee for his lack of sleep
[09:18] <ogra_> haha
[09:18] <ogra_> yeah, good idea
[09:18] <jibel> brendand, did you get memory issues recently?
[09:19] <jibel> brendand, well, no you, but you device
[09:19] <jibel> not
[09:19] <jibel> +r
[09:19] <ogra_> jibel, its not a memory issue, it is wanted behavior ;)
[09:19] <ogra_> (just not for the dash)
[09:19] <popey> ogra_: so basically i need to flash clean?
[09:19] <brendand> jibel, i haven't been doing such intensive use
[09:20] <ogra_> popey, i fear so ...
[09:20] <popey> ok
[09:20] <popey> ta
[09:20] <ogra_> popey, but i guess you should be fine just flashing without wiping
[09:20] <popey> jibel: i had very few apps open yesterday and had scopes restart multiple times
[09:20] <popey> sure..
[09:20] <ogra_> yeah, the usage duration definitely counts too here
[09:21] <popey> i used my phone as my main device all day yesterday as I was away from my pc at a conf
[09:21] <ogra_> i rarely get it during the first hour after a reboot if i only have two/three apps open
[09:21] <popey> found it pretty painful at times.
[09:21] <ogra_> but once it starts it stays around very contantly
[09:21] <Chipaca> popey: you get to have all the fun
[09:22] <popey> it also got to a state where I couldn't start new apps
[09:22] <jibel> popey, ogra_ how many tabs open in your browseR?
[09:22] <popey> had to reboot a few times
[09:22] <popey> jibel: none
[09:22] <popey> i had a few webapps apps open
[09:22] <ogra_> my browser carries 3 around that i was to lazy to bookmark yet
[09:25] <jibel> ogra_, popey okay, just got it
[09:25] <jibel> Oct 16 11:24:37 ubuntu-phablet kernel: [ 3409.726955]select 'unity8-dash' (2647), adj 802, size 50064, to kill
[09:25] <jibel> Oct 16 11:24:37 ubuntu-phablet kernel: [ 3409.727019]Killing 'unity8-dash' (2647), adj 802,
[09:25] <jibel> sil2100, ^
[09:26] <jibel> relatively easy with a somewhat normal usage of the webbrowser
[09:26] <popey> _1
[09:26] <popey> +1 even
[09:27] <sil2100> uh
[09:27] <jibel> it takes more time than before because there is more free memory after boot but the problem is still there
[09:27] <ogra_> yeah
[09:27] <ogra_> the question is if we need to consider it a blocker ... what do we expect to be done with this image
[09:28] <ogra_> if it is only used to short presentations and freshly booted all the time i wouldnt consider it a blocker and just acre to quickly get a fix out via OTA
[09:28] <ogra_> *care
[09:29] <ogra_> if someone will actually use the device i would block
[09:29] <ogra_> (i mean constanly as main device)
[09:32] <sil2100> ogra_: I sent out a direct question to Victor regarding this and the other blockers
[09:32] <ogra_> thanks !
[09:32] <sil2100> But I somehow feel we won't block on any of those - just a feeling
[09:32] <ogra_> sil2100, btw, do we have an actual dealine ?
[09:33] <ogra_> *deadline
[09:33] <ogra_> i.e. did anyone mention an hour
[09:33] <sil2100> ogra_: I did not hear anything about that
[09:43] <jibel> ogra_, sil2100 the problem is that the dash is systematically killed when there are memory conditions and not the backgrounded apps, which completely defeat the purpose of the app lifecycle
[09:44] <ogra_> jibel, yep
[09:47] <popey> indeed... my day yesterday.. http://paste.ubuntu.com/8573082/
[09:48] <ogra_> yeah
[09:49] <jibel> popey, you see, it always starts by the dash because it is the top consumer and has the same oom_score than other apps then kills the webbrowser if it is not enough
[09:50] <popey> yeah
[09:52] <sil2100> Ok everyone, I need to jump out for ~1h, need to prepare insurance and everything for the sprint
[09:52] <sil2100> If anything, muup
[09:52] <sil2100> muuup
[09:52] <sil2100> mup mup
[09:53] <sil2100> But I guess Mirv is here so everything should be good (tm)
[09:54] <ogra_> as long as his cats are here too at least :)
[09:59] <Wellark> any problems found with i-network ?
[09:59] <ogra_> yeah, it always shows the wifi icon when i'm on wifi !
[09:59] <ogra_> crazy thing that
[09:59] <john-mcaleely> ogra_, I wonder if my perception is 'various things are broken', rather than 'memory shortage causes various problems'
[10:00] <ogra_> john-mcaleely, well, if you dont know the technology the former is surely true ...
[10:01] <john-mcaleely> (just had an online account fail to login in as it transitioned to the web browser). Reboot and it works
[10:01] <ogra_> (and i doubt they actually care about the technology)
[10:01] <Wellark> ogra_: oh, damn.. OK. let me file a Critical Ubuntu UX bug. I've noticed the same and I'm not happy with it!
[10:01] <john-mcaleely> I'm trying to maintain a users view ;-)
[10:01] <Wellark> ogra_: <3
[10:01] <popey> ok, just fresh flashed my n4 and n7 and now the dash is completely empty of icons
[10:01] <ogra_> Wellark, i havent heard about any issues yet :)
[10:02] <ogra_> john-mcaleely, right, thats why i raised the issue ... it is so user visible
[10:02] <Wellark> ogra_: ok. good. I actually had like  6h sleep (how crazy is that!) and was worried everything broke in me mean time
[10:02] <Mirv> o/
[10:02] <Mirv> lunching but here
[10:03] <popey> http://imgur.com/xMsFRMx,jriuX6G
[10:03] <popey> nobody else seeing that?
[10:03] <john-mcaleely> ogra_, sure. I agree its a serious problem, even if I'm not aware I'm seeing it :-)
[10:04] <Wellark> popey: sometimes
[10:04] <Wellark> popey: could that be the "dash needs to be removed from app lifecycle" ?
[10:05] <popey> its a clean boot
[10:05] <popey> i literally just flashed it and booted, no apps running
[10:05] <Wellark> Saviq: ^
[10:05] <cwayne-afk> morning guys
[10:06] <Saviq> popey, I believe seb128 did, talking with pstolowski about crashing scopes
[10:06] <Saviq> popey, what if you pull to refresh?
[10:06] <popey> Saviq: icons appear
[10:07] <Saviq> popey, yeah, sounds like what seb128 saw
[10:07] <popey> do we need a bug for this?
[10:07] <Saviq> seb128, pstolowski, do we have a bug for empty apps yet?
[10:15] <popey> ogra_: just OTA'ed my bq and that too is sat at the BQ screen for ages now, with no adb
[10:16] <popey> it shows as "offline" in adb...
[10:17] <jibel> popey, disconnect/Reconnect usb cable?
[10:18] <popey> same
[10:18] <popey> its stuck at the bq screen.
[10:18] <pstolowski> Saviq, yeah, 1 sec
[10:19] <popey> ... time passes and now it boots..
[10:19] <pstolowski> popey, Saviq https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1381970
[10:20] <popey> ooh, new indicators
[10:21] <ogra_> popey, as i said, adb only after session is up
[10:29] <ogra_> jibel, in the photos scope, if you disable the online sources in the config, does that take effect for you without having to restart the scope ?
[10:29] <ogra_> (from the preview i mean ... it uses the changed settings the next time i open it)
[10:29] <jibel> ogra_, yes, you need to pull down to refresh
[10:30] <jibel> ogra_, same when you re-enable remote content you must refresh the scope manually
[10:30] <ogra_> jibel, that still keeps the facebook and flicker categories around even though i disabled them
[10:30] <ogra_> they only go away if i go back to the preview page and open the scope again
[10:32] <jibel> brendand, search remote contents on the photos scope works for you?
[10:32] <cwayne> ogra_: there's an open bug that changing settings should refresh a scope
[10:33] <ogra_> cwayne, ah, good
[10:34] <Saviq> sil2100, qtmir ACK
[10:34] <brendand> jibel, i'll check
[10:34] <brendand> sil2100, landing gates are still closed right?
[10:34] <ogra_> brendand, yes
[10:34] <ogra_> until we promoted
[10:35] <ogra_> (or at least until we know we'll promote)
[10:36] <Mirv> or until we know what's decided to be landed
[10:37] <Mirv> fun. 4G connection is twice as fast as what I get over wifi with my poor wifi chipset.
[10:38] <Mirv> 4G-over-USB-tethering, that is
[10:38] <Saviq> brendand, actually bug #1377809 looks like a dupe of bug #1380736, at least from the trace, incomplete as it is
[10:53] <ogra_> dpm, so you didnt push the new reminders out which means it didnt make it onto the image :(
[10:55] <ogra_> Mirv, oh, cool, i havent tested tethering for quite a while ... good to know it still works (i still dont know why it doesnt on mako thoigh)
[11:16] <ogra_> damn
[11:16] <ogra_> my device hags hard
[11:16] <ogra_> *hangs
[11:17] <brendand> sil2100, can you add jibel to the attendees for the landing meeting?
[11:17] <ogra_> i did a right swipe, swiped away an app and it hangs ... no response at all
[11:17] <ogra_> ah, now it recovered
[11:18] <ogra_> that was definitely not apport ... looks like mir hung for a moment
[11:18] <ogra_> (it is normally responsive now)
[11:23] <ogra_> oh
[11:23] <ogra_> seems slangasek disabled the system-image side of the image builds, but not the rootfs build
[11:23]  * ogra_ notes that we have a rootfs for 110 but it was never imported
[11:24] <ogra_> sil2100, ^^ FYI
[11:32] <olli> elopio, still around?
[11:35] <ogra_> olli, testing was handed over to jibel nad brendand a few hours ago
[11:35] <ogra_> *and
[11:35] <brendand> olli, got questions?
[11:35] <olli> brendand, got bugs? :)
[11:35] <brendand> olli, probably as many as you have questions :)
[11:35] <olli> so 1?
[11:35] <olli> ;)
[11:36] <tvoss> olli, :)
[11:36] <brendand> olli, well it depends how important you want them to be
[11:38]  * Mirv afk for doctor, back in 1h
[11:39] <olli> brendand, jibel, do you have an eta or some indication how far you are?
[11:40] <brendand> olli, we are done with all the formal testing at least
[11:40] <brendand> olli, actually that's wrong - almost done
[11:40] <olli> great, all bugs filed and such? what's left
[11:40] <olli> :)
[11:41] <jibel> olli, what's left: dashboard scope, HERE, tasks
[11:41] <jibel> these are untested
[11:42] <sil2100> brendand: sure
[11:42] <sil2100> brendand: to both, or just the morning one?
[11:43] <ogra_> sil2100, oh, btw, what happened to the evening one ? i got canellation mails for today and tomorrow from kgunn
[11:43] <sil2100> ogra_: I think it was just kgunn cancelling his attendence
[11:44] <ogra_> ok
[11:44] <ogra_> i assumed it was by accident but it looked like the whole event was cancelled
[11:44] <ogra_> probably just gcal being weird though
[11:46] <ogra_> oh look !
[11:46] <ogra_> we have a full test run of 109
[11:47] <ogra_> http://dashboard.ubuntu-ci:8080/smokeng/utopic/touch_stable/krillin/109:20141016:20141014-acf0142/583/
[11:47] <ogra_> psivaa, awesome !
[11:47] <ogra_> wow, UITK looks really bad in that
[11:47] <ogra_> (as does calculator)
[11:49] <psivaa> ogra_: lots of apparmor denials in the uitk ones
[11:49] <ogra_> oh
[11:49] <ogra_> bzoltan, are you aware of that ?
[11:51] <ogra_> hmm, these denials seems to be scopes related though
[11:54] <ogra_> oh, i see a lot of denials in my own syslog too ... though different ones (appy trying to access the QML cache)
[11:54] <jdstrand> what are the denials
[11:54] <ogra_> jdstrand, my own webapps trying to access ~/.cache/QML/
[11:55] <jdstrand> I imagine they are the known bugs for scopes. there are MPs but I don't think they've landed in rtm
[11:55] <jdstrand> ah
[11:55] <jdstrand> that is harmless
[11:55] <ogra_> Oct 16 13:06:04 ubuntu-phablet kernel: [ 3911.060389]type=1400 audit(1413457564.510:177): apparmor="DENIED" operation="open" profile="com.ubuntu.developer.ogra.golem-de_golem-de_0.3" name="/home/phablet/.cache/QML/Apps/" pid=27015 comm="webapp-containe" requested_mask="r" denied_mask="r" fsuid=32011 ouid=32011
[11:55] <jdstrand> bug #1381620
[11:55] <sil2100> brendand_, jibel: hey, so... regarding bug #1379296 again
[11:56] <sil2100> brendand_, jibel: how you would personally assess this? Is it a definite blocker in your opinion? How hard is it to reproduce?
[11:56] <ogra_> jdstrand, ah, thanks i thought i'm missing some new framework definition :)
[11:56] <ogra_> the apps need updating anyway
[11:56]  * jdstrand nods
[11:56] <brendand_> sil2100, did you add jibel to the meeting?
[11:57] <sil2100> Saviq: re the fix for the bug above ^ I saw the code and it seems uninvasive - do you think it can be regression-prone?
[11:57] <jdstrand> ric mm said that it is just a noisy harmless denial with the way that qtdeclarative-opensource-src is looking around for stuff. it handles the failure and moves on without problem
[11:57] <Saviq> sil2100, no, it's safe
[11:58] <sil2100> ogra_: btw. someone indeed cancelled todays meeting, hmmm
[11:58] <sil2100> brendand_: added to all evening ones
[11:58] <jibel> sil2100, I asked rhuddie to find test cases and the conditions to reproduce this issue and have data to decide if it's a blocker or not.
[11:58] <ogra_> sil2100, ah, so gcal wasnt lying
[11:59] <sil2100> jibel: ok, great, since if this is a blocking issue then as per what Victor said we might release silo 12, kick 110 and then only test the delta for this image
[11:59] <brendand_> sil2100, cancelled?
[11:59] <ogra_> sil2100, did you notice above ... we have a rootfs for 110 (but no system image) ... if we'd do a rebuild we'd need to let 110 out too
[11:59] <sil2100> brendand_: not sure who, it's not on my calendar for today
[11:59] <sil2100> ogra_: hm... what does that rootfs for 110 have btw.?
[11:59] <ogra_> let me check
[11:59] <ogra_> shouldnt have anything
[12:00] <sil2100> Ghost images
[12:00] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/rtm/20141016.1.changes
[12:00] <ogra_> same as 109 :)
[12:28]  * Mirv back
[12:28] <sil2100> Mirv: o/
[12:34] <sil2100> brendand_, jibel: could you guys check bug LP: #1381857 and see if you agree with the rationale in the comments there?
[12:35] <brendand_> sil2100, ah so this ties in with a similar issue i found
[12:36] <brendand_> sil2100, which is that if you have no account and no connection then the apps close after a bit if you try to open them
[12:36] <brendand_> sil2100, which is dumb
[12:36] <brendand_> sil2100, no feedback to the user or anything
[12:44] <dpm> ogra_, sorry for the delay. On Reminders: so what happened is that last Friday the version containing the account plugin changes was already pushed to the store by mistake. Which means that unfortunately for a few days it was broken (but only for newly created accounts, which is probably why no one noticed it), but it also means that we didn't need to push a version to the store yesterday, so we decided not to do it
[12:44] <dpm> ogra_, in summary, it should be all good now
[12:45] <ogra_> ah, awesome
[12:45]  * ogra_ doesnt care about the past :)
[12:45] <ogra_> i only noticed that there was no click update in any image we had
[13:08] <sil2100> Saviq: so bug #1381871 is not triggered from the system-settings?
[13:09] <Saviq> sil2100, see ubuntu-unity, there's a fix comin'
[13:17] <cjwatson> Passing on from another channel: how terrible would it be if there were ppa.launchpad.net downtime this weekend?  Or next?
[13:17] <cjwatson> It's weeks away from running out of disk space
[13:17] <ogra_> assuming we'll all travel ...
[13:17] <ogra_> or most of us at least
[13:20] <sil2100> I think this weekend or the next seem ok, since as ogra_ mentioned most of us will be in travel, so at least from our side we should be safe
[13:20] <sil2100> Just we don't want to be left without PPA's during the sprint ;)
[13:20] <ogra_> better this than next ... seems easier to  communicate issues we may find afterwards when we're face to face
[13:21] <cjwatson> I don't think that will be an issue either way really, it's just a disk expansion
[13:21] <cjwatson> And yeah, it definitely won't be during the working week
[13:22] <sil2100> tvoss, lool: hey guys, wanted to poke about the status of silo 004 - were you able to get that fixed?
[13:23] <tvoss> sil2100, nope, not reliably
[13:23] <tvoss> sil2100, would be great to keep the silo, though
[13:23] <ogra_> sil2100, we might think about 23 though
[13:25] <ogra_> (interesting that this didnt come up in testing either)
[13:26] <ogra_> hey
[13:26] <ogra_> there we go
[13:26] <ogra_> https://code.launchpad.net/~larsu/indicator-sound/lp1381871/+merge/238555
[13:26] <ogra_> thats what i call quick :)
[13:26] <sil2100> Yep :)
[13:27] <sil2100> We saw that coming in -unity
[13:27] <ogra_> ah
[13:27] <ogra_> yeah, i got to many channels already :)
[13:33] <popey> bzoltan: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-013 - the qtorganizer5-eds fix for bug 1311165 - any idea when it will land?
[13:34] <ogra_> after the milestone :)
[13:34] <bzoltan> popey:  that is next in the queue i assume.
[13:34] <bzoltan> ogra_: popey: after the amnesty
[13:34] <popey> so tomorrow?
[13:35] <ogra_> perhaps
[13:35] <popey> ok, thanks
[13:35] <ogra_> perhaps even later this evening ... really depends how long the milestone still takes
[13:35] <bzoltan> popey: I just updated the laning branch, it builds now. i will start the testing process in few hours and if we are lucky it will be ready in 12 hours.
[13:35]  * popey would really love to see it land
[13:35] <popey> you know, calendars are pesky things! silly timezones
[13:35] <popey> everyone should just move to UTC
[13:35] <bzoltan> popey: you are not the only one
[13:36] <cjwatson> it seems that we forgot to turn import-images back on last night
[13:36] <cjwatson> any reason we shouldn't do so?
[13:36] <ogra_> cjwatson, we have some rootfs that wasnt published yet
[13:36] <ogra_> cjwatson, we possibly have to build another image soon so i didnnt bother to turn it back on yet
[13:36] <ogra_> (i'm aware it is off but doesnt do harm either)
[13:37] <bzoltan> popey:  look at the changelog of that UITK release candidate -> http://pastebin.ubuntu.com/8573976/ 13 bug fixes... most of them critical and rtm14
[13:37] <popey> \o/
[13:37] <popey> thanks bzoltan
[13:38] <bzoltan> popey:  no probs ... fingers crossed :)
[13:39] <cjwatson> ogra_: yes it does, it's blocking ubuntu-core images
[13:39] <cjwatson> you guys aren't the only user :)
[13:39] <ogra_> right, just saw the other channel
[13:39] <ogra_> yeah, forgot about that
[13:39] <ogra_> turn it back on then
[13:39] <ogra_> sil2100, ignore 110 :)
[13:39] <cjwatson> reenabled, thanks
[13:39] <ogra_> (teh bot will soon annouonce it)
[13:40] <brendand_> sil2100, so are we having the landing meeting?
[13:40] <sil2100> brendand_: yeah, just need to re-add that somehow, but now in meetings
[13:41] <ogra_> brendand_, kgunn was a bit optimistic and removed it for all of us :)
[13:45] <ogra_> brendand_, is anyone QAing silo 012 already ?
[13:45] <ogra_> might be good to have ready what we can
[13:48] <sil2100> ogra_: I think brendand_ is still doing promotion testing
[13:48] <ogra_> oh
[13:48] <sil2100> brendand_, jibel: how far are you in promotion testing?
[13:48] <jibel> ogra_, we are finishing a test case to reproduce it and rhuddie will start testing silo12
[13:48] <ogra_> cool
[13:48] <sil2100> \o/
[13:48] <jibel> just in case
[13:48]  * ogra_ taps foot watching silo 15 ...
[13:48]  * sil2100 goes fix the calendar
[13:49] <ogra_> how can such a small indicator build so long !
[13:49] <sil2100> ;)
[13:52] <sil2100> ogra_, brendand_: ok, added it to the calendar back
[13:52] <cyphermox> jibel: can you tell me more about the issue with wifi not coming back up after flight mode?
[13:52] <ogra_> sil2100, great !
[13:52] <ogra_> sil2100, so whats the final plan ? we land the two silos and re-spin ... ? i assume iif we do that we dont wait for a full test run then ?
[13:53] <brendand_> ogra_, we want to land 15?
[13:54] <ogra_> brendand_, thats what i understood
[13:54] <brendand_> ogra_, ah that's the wizard issue right?
[13:54] <ogra_> yeah
[13:54] <ogra_> three line change
[13:55] <jibel> cyphermox, turn flightmode on, wait until you've no signal on cellular and wifi, turn it back off. Sometimes Wifi doesn't come back (list of AP is empty)
[13:55] <brendand_> ogra_, ok whenever it's ready
[13:55] <kgunn> ogra_: sorry
[13:55] <cyphermox> jibel: how long have you waited to reproduce the bug for things to maybe show up?
[13:56] <ogra_> kgunn, np :)
[13:56] <kgunn> ogra_: i'll get msm to add it back
[13:56] <ogra_> kgunn, sil2100 did already
[13:56] <kgunn> ah...
[13:56] <cyphermox> jibel: I'll do some more testing, I believe you, I just want to make really sure it's not "normal" delays for scanning time
[13:56] <jibel> cyphermox, precisely I don't know, maybe 1 minute
[13:58] <cyphermox> jibel: alright
[13:58] <cyphermox> thanks!
[13:59] <jibel> cyphermox, 2 min and the list is still empty
[13:59] <cyphermox> great
[13:59]  * ogra_ sneds some wifi waves fance-wards
[13:59] <ogra_> *france
[13:59] <cyphermox> jibel, if you currently have it reproduced, could you login with adb and run 'nmcli dev wifi list' ?
[14:00] <cyphermox> jibel: could it be because you haven't set your phone to french as we all should?
[14:00] <cyphermox> :D
[14:01] <ogra_> azerty
[14:01] <ogra_> ...
[14:01] <jibel> cyphermox, nmcli shows the list of AP
[14:01] <cyphermox> wonderful :)
[14:01] <cyphermox> jibel: did you file a bug already about this?
[14:01] <jibel> cyphermox, but the list is still empty on the indicator
[14:01] <jibel> cyphermox, not yet
[14:01] <cyphermox> ok
[14:03] <john-mcaleely> incoming email from olli
[14:03] <john-mcaleely> I see that I now need to make sure device tarball for silo5 lands
[14:05] <ogra_> john-mcaleely, err ?
[14:05] <ogra_> i thought we were limited to the two fixes
[14:05] <ogra_> device tarball souand like a lot more re-testing work
[14:05] <ogra_> *sounds
[14:05] <john-mcaleely> ogra_, that's not my reading of the mail. Happy to be corrected :-)
[14:05] <john-mcaleely> (I agree it's lots more testing)
[14:06] <ogra_> well, i dotn have that mail because our management likes to bkeep everything secret :P
[14:06] <ogra_> (or my mail is broken :p )
[14:07] <ogra_> this constant lack of information is really annoying
[14:07] <sil2100> ogra_: soooo
[14:07] <sil2100> ogra_: the plan is, we add the 2 silos for sure
[14:08] <ogra_> ok
[14:08] <ogra_> sil2100, 005 sounds scary though
[14:08] <sil2100> Then, as I have been asked about that, we'll try to squeeze in a few other silos that management thinks are important but didn't make it
[14:08] <ogra_> who decides the importance ?
[14:08] <sil2100> And if we able to achieve that, we kick a new image and then hand over to QA
[14:09] <ogra_> also that means we'll have to stay frozen for another night
[14:09] <sil2100> ogra_: basically pmcgowan, victorp and olli - but the silos they proposed seem sane
[14:09] <john-mcaleely> ogra_, phablet@
[14:09] <ogra_> sil2100, well, i know that my team is eager to get their already tested silos landed (005 is in that list too)
[14:09] <olli> ogra_, do you want me to call you and read it ;)
[14:09] <sil2100> Yeah, the recommendation is to stay frozen till we get an assesment from QA on the new image ;/
[14:09] <sil2100> ogra_: sure, that's on the list ;)
[14:10] <olli> or are you no on @Phablet
[14:10] <ogra_> olli, no, sorry
[14:10] <ogra_> my mail seems to be slow
[14:10]  * olli hasn't heard any comments about communication then
[14:10] <olli> ;)
[14:10] <ogra_> and sorry for being so grumpy ... lack of sleep and all :)
[14:10] <john-mcaleely> sil2100, one twist on landing silo 5. I'm in the air tomorrow.
[14:11] <john-mcaleely> sil2100, back online, in the US timezone 5pm.
[14:11] <john-mcaleely> sil2100, so I think silo5 is today or not at all
[14:11] <sil2100> john-mcaleely: ah, right, since it requires a device tarball, right?
[14:11] <john-mcaleely> sil2100, it does. You do already have the tarball, tested on #106 if I remember
[14:11] <pmcgowan> sil2100, john-mcaleely  if silo 5 is too risky then lets drop it
[14:12] <ogra_> ChickenCutlass, ^^^^ so if you want stuff landed (since we will likely still stay frozen til tommorrow) you need to get approval from pat, olli or victor
[14:12] <ogra_> i know you have high interest to get more in
[14:12] <ChickenCutlass> ogra_: yeah I spoke with pmcgowan
[14:12] <ogra_> ah, perfect
[14:12] <john-mcaleely> pmcgowan, not so much risky, as needing qa time & care in landing
[14:12] <ogra_> :)
[14:12] <sil2100> ogra_: check the e-mail for the silos that we proposed
[14:12] <ogra_> sil2100, if it only would hit my inbox, damned
[14:12] <john-mcaleely> (needs dual rootfs & device tarball at the same time, otherwise, regressions)
[14:12] <sil2100> Well, anyway first priority have the two blockerz
[14:13] <john-mcaleely> (the code isn't risky, I guess the landing might be)
[14:13] <ogra_> yeah
[14:13] <john-mcaleely> sil2100, I'm here all night, as they say :-)
[14:13] <john-mcaleely> agree, blockerz first
[14:13] <ogra_> ha, got it
[14:13] <jibel> cyphermox, bug 1382071
[14:15] <cyphermox> jibel: thanks!
[14:19] <rsalveti> ogra_: ChickenCutlass: did we evaluate landing rtm 6?
[14:19] <rsalveti> the fix is minimal, and fix an important issue
[14:20] <rsalveti> rtm 5 is not risky, but yeah, needs coordination
[14:21] <rsalveti> sil2100: guess question for you as well ^
[14:22] <sil2100> So I would first land the two blocker fixes, then try the ones that are less risky - so 5 and I also got informed that 8, even though touching a lot of components, in the end is safe
[14:22] <ChickenCutlass> rsalveti: yes 6 is on the list
[14:23] <rsalveti> great
[14:23] <ChickenCutlass> rsalveti: so 6, 5 and 16 on the list
[14:23] <rsalveti> I know 5 and 6 are both safe
[14:23] <rsalveti> 16 not so safe, but desired as well
[14:24] <rsalveti> just because of the amount of components that 16 got
[14:24] <cwayne> does 5 still need to coordinate with a device tarball landing?
[14:24] <rsalveti> cwayne: yes
[14:24] <sil2100> Ok, so 5 is safish - could you overview again how we need this coordinated? We need a device tarball AFTER publishing the silo?
[14:26] <rsalveti> sil2100: yes
[14:29] <ogra_> rsalveti, 5 might not be risky but device tarball QAing takes extra time
[14:29] <ogra_> sil2100, we can drive the image builder in a way that we land device at the same time
[14:30] <sil2100> ogra_: ah, right - the thing you wanted to do last night righ?
[14:30] <ogra_> yeah
[14:30] <ogra_> well, for now i'm waiting for 110 to pop out of the importer :P
[14:31] <sil2100> That takes a while!
[14:31] <ogra_> well it is 30min in ...
[14:31] <ogra_> should be 15min more in max ... (though it does ubuntu-core too currently)
[14:33] <plars> sil2100: ogra_: not going to be able to make the landing call today, have a doctor appointment. If you need anything though let me know and I'll be back about an hour after
[14:33] <sil2100> plars: hey! So, did anyone poke you about removing the terminal and filemanager tests from krillin ubuntu-rtm smoktesting?
[14:33] <ogra_> good luck then
[14:34] <slangasek> ogra_: hmm, no one had mentioned to me that rootfs builds should be turned off
[14:34] <ogra_> slangasek, well, importer was off ... i would always turn off both ... no issue though
[14:35] <plars> sil2100: psivaa mentioned they were coming out of the image, but I don't know when
[14:35] <plars> sil2100: just rtm or utopic also?
[14:35] <ogra_> plars, they are gon since 109
[14:35] <ogra_> plars, only on krillin rtm
[14:36] <plars> oh, that might be trickier to remove it just on rtm and just on krillin... I'll have to take a look in a bit
[14:36] <ogra_> :)
[14:37] <ogra_> plars, they are just failing gracefully atm ... (and taint the statistics a bit ... )  no hurry i guess ... it isnt like they block anything
[14:45] <sil2100> Grrr, stupid spreadsheet
[14:49] <sil2100> brendand_, jibel: is the QA promotion testing over?
[14:49] <sil2100> i.e. can we poke you about silo 12 and silo 15?
[14:50] <jibel> sil2100, yes, we moved to silo testing
[14:50] <sil2100> jibel: excellent - I just re-tested silo 15 as well so it's also ready for QA
[14:50] <sil2100> Thanks guys :)
[14:51] <brendand_> sil2100, i'm ready for 15 now
[14:51] <sil2100> ogra_: what do you think about us building a new image after just landing silo 15 and 12, then trying to land some of the additional silos and kicking the final one?
[14:51] <sil2100> ogra_: as asac also mentioned, this way we'll be super safe, with as safe fail-back
[14:51] <ogra_> sil2100, sounds perfect
[14:51] <sil2100> And I don't think we'll loose that much time as silo testing anyway takes time
[14:52] <sil2100> So we don't leave system image idle ;p
[14:53] <pmcgowan> sil2100, +1
[14:53] <ogra_> sil2100, that will make slangasek happy :D
[14:54] <rhuddie> sil2100, jibel, on silo 12, I am still seeing unity8-dash being killed in /var/log/syslog: http://pastebin.ubuntu.com/8574310/
[14:54] <slangasek> yesyesyes
[14:55] <ogra_> rhuddie, thats not killing, it says "selected to kill" but at the same second it also selected other bits with an 802 score
[14:56] <ogra_> rhuddie, do you see it being killed *on the screen* ?
[14:56] <rhuddie> ogra_, ah ok, I've not seen it on the screen, no
[14:56] <ogra_> then we are fine
[14:57] <rhuddie> ogra_ I'll carry on with testing :)
[14:57] <ogra_> it should kill the dash eventually ... if there is really no other chance ... thats what the 500 score achieves (still leaves the system alone even if you overrun the memory havily)
[14:58] <ogra_> in 99.9% of cases there will be other stuff with 800 score to kill first though
[14:58] <ogra_> ricmm, is there something we could do about the message so people dont think things that are selected are really killed ?
[15:00] <ricmm> ogra_: I dont think users will be looking at the syslog all the time
[15:00] <ricmm> and those who will should know that the message is iterting over the candidates to select
[15:00] <ogra_> ricmm, right
[15:00] <ogra_> k
[15:00] <ricmm> I mean if its just an issue with the QA team, its not worth hiding
[15:01] <ricmm> because we might need it when its a real issue :)
[15:04] <sil2100> rhuddie: thanks :)
[15:04] <bregma> trainguards, I could use a priority silo assignment for line 87 so I can meet Ubuntu final freeze with some last-minute bugfixes in desktop Unity, if you please....
[15:05] <sil2100> bregma: ACK!
[15:05] <sil2100> Let me take a look at that quickly
[15:06] <sil2100> bregma: ok, assigning a silo
[15:07] <sil2100> bregma: silo 001 for you it seems!
[15:07] <ogra_> so i just got a notification for 110
[15:07]  * bregma parties like he's silo #1
[15:07] <ogra_> oh, the bot is gone !
[15:10] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/rtm/110.changes
[15:10] <ogra_> (empty anyway)
[15:11]  * sil2100 chokes the bot
[15:11] <sil2100> bregma: in case we miss it getting set to ready to release, feel free to pinging me directly and I'll publish
[15:11] <ogra_> yeah, it thought it was online so sent the announcement to ether ...
[15:11] <sil2100> Since I guess it's important :)
[15:13] <bregma> sil2100, do you plan to sleep at all in the next 72 hours?
[15:13] <sil2100> Sleep? What's that?
[15:13] <sil2100> The only sleep I know is sleep(number);
[15:14] <ogra_> bregma, landing team members dont do that sleep thing
[15:15] <ogra_> sleep is evil ... we use upstart !
[15:15] <sil2100> brendand_, rhuddie: thanks for picking up the important silos guys :)
[15:15] <ogra_> ++
[15:16] <sil2100> ogra_: ;p
[15:39] <brendand_> sil2100, 15 signed off
[15:40] <sil2100> \o/
[15:40] <sil2100> !!
[15:40] <sil2100> brendand_: thanks
[15:40] <sil2100> Ok, first one off the list
[15:44] <sil2100> brendand_: can you pick up now one of the safe silos from the list? Maybe silo 6, as I heard it's safe
[15:44] <sil2100> (and touches only one component)
[15:45] <sil2100> brendand_: even it it gets signed off, I won't publish it until we get an image built with the blocker fixes only
[15:45] <brendand_> sil2100, right maybe start with that
[15:45] <sil2100> brendand_: but no haste, maybe relax a bit before that, get some tea/coffee/food
[15:46] <bregma> bah, my amd64 build failed with a bad-block error trying to write from all threads, any chance someone with magic powers could restart it? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-001/+build/6466311
[15:46] <brendand_> sil2100, i'll get one more under my belt then i kind of need to EOD
[15:46] <sil2100> bregma: doing!
[15:46] <brendand_> after the landing meeting
[15:46] <sil2100> brendand_: ACK!
[15:46] <ogra_> wohooo
[15:52] <ogra_> yay
[16:04] <ogra_> hmm, did i drop ?
[16:13] <bzoltan> ogra_:  out of curiosity :) have you changed anything in the image what could break my testing script?
[16:13] <ogra_> bzoltan, nope
[16:13] <ogra_> bzoltan, but i noticed that we had 67 failures in UITK tzesting today on rtm
[16:13] <bzoltan> ogra_:  OK, in that case it is just a normal failure... I try again
[16:14] <bzoltan> ogra_: all false
[16:14] <ogra_> :)
[16:14] <bzoltan> ogra_: http://people.canonical.com/~bzoltan/ap-2014_10_15-RTM-SILO15-KRILLIN/MAIN-ap-2014_10_15-SILO15-KRILLIN
[16:22] <bzoltan> ogra_:  but true, that the AP tests become super unreliable since last Friday
[16:23] <sil2100> \o/
[16:23] <ogra_> bzoltan, well, changelogs are at http://people.canonical.com/~ogra/touch-image-stats/rtm/
[16:23]  * sil2100 m&c in the meantime
[16:23] <bzoltan> ogra_:  elopio: actually it was last Thursday when the least healthy autolanding happened on our staging .. since then the AP tests went crazy
[16:23] <ogra_> bzoltan, friday should be ~80
[16:23] <elopio> jibel or brendand_: can you please sort the trello cards in order of importance ?
[16:23] <sil2100> Mirv: you go to sleep now, save your strength for tomorrow
[16:23] <ogra_> ++
[16:24] <elopio> bzoltan: I haven't been able to look at the videos to see what might be going on.
[16:24] <brendand_> elopio, done
[16:24] <elopio> thanks
[16:24] <Mirv> sil2100: sure, I just wanted to know how are things :)
[16:24] <brendand_> elopio, we might do 5 before 8 though
[16:24] <bzoltan> elopio:  nothing with the UITK, that is for sure
[16:24] <sil2100> Mirv: thanks :)
[16:25] <elopio> brendand_: I was about to take 5.
[16:25] <brendand_> elopio, i think we should do 8 first actually
[16:25] <brendand_> jibel, what do you think?
[16:25] <sil2100> Yeah, I would say first 6 and 8, since 6 has been done let's move on to 8 first
[16:26] <sil2100> Let me bring it up with the product team
[16:27] <elopio> taking #8 then
[16:28] <sil2100> elopio: thank you :)
[16:28] <bzoltan> ogra_: elopio: but for long time I do not use the CI dash as validation reference... because I am tasting against the latest image and that never has ready tests. So I first run the test plan on stock image and compare to it the silo results.
[16:29] <imgbot> [16:29] <ogra_> there
[16:30] <ogra_> :)
[16:45] <jibel> elopio, 8 then 5
[16:49] <elopio> jibel: ack.
[16:49] <elopio> who works on media hub? Is that jhodapp ?
[16:49] <jhodapp> elopio, yes
[16:49] <elopio> I would like somebody to lock at this one: https://bugs.launchpad.net/media-hub/+bug/1381893
[16:50] <jhodapp> elopio, yeah that's probably my next thing to look at
[16:50] <elopio> jhodapp: I'm not sure how to reproduce it or where to keep an eye during testing. Maybe you have some clues.
[16:50] <jhodapp> elopio, can you reproduce it with this? https://bugs.launchpad.net/media-hub/+bug/1380848
[16:52] <elopio> jhodapp: will try after finishing my current silo.
[16:53] <jhodapp> elopio, cool thanks
[17:13] <ogra_> sil2100, FYI 111 rootfs is done (in case you want to release any silos, it is safe now)
[17:14] <sil2100> ogra_: thanks!
[17:14] <sil2100> Let me move the machinery then
[17:14]  * ogra_ makes a note to add a notification for that to the bot some day
[17:17] <sil2100> Could be a feature, although not critical as I guess we require this rarely :)
[17:18] <ogra_> well, looking how noisy other bots in this channel are i feel like my bot lacks a bit :)
[17:19] <sil2100> ogra_, elopio, ToyKeeper: so, I would recommend that after the silo 8 gets finished testing, let's simply move on to silo 5 and the device tarball
[17:19] <sil2100> And basically (sadly) skip silo 16
[17:20] <sil2100> It's an important silo but it's not ready yet, so I would be less confident in landing that for such an important image
[17:20] <sil2100> ogra_: hah ;)
[17:20] <ogra_> :)
[17:20] <ogra_> yeah, sounds sane
[17:28] <bzoltan> ogra_:  but actually the problem with the UITK tests came very recently http://people.canonical.com/~bzoltan/ap-2014_10_15-RTM-SILO15-KRILLIN/ap-2014_10_14-20_47_54-ubuntuuitoolkit-2-archive.tests
[17:29] <bzoltan> ogra_:  so about 48 hours ago on the latest available stock image by then I got consistent clear UITK tests
[17:29] <bzoltan> elopio: ^
[17:30] <ogra_> bzoltan, well, then it mist be a change between 104 and 111
[17:31] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/rtm/
[17:31] <ogra_> *must
[17:31] <bzoltan> ogra_:  yes
[17:31] <bzoltan> ogra_:  I will do the UITK tests on those images
[17:31] <ogra_> ++
[17:32] <ogra_> 105 had new mir
[17:33] <slangasek> barry: ping
[17:34] <barry> slangasek: pong
[17:34] <imgbot> [17:34] <slangasek> barry: hi, so we noticed yesterday that bdmurray has some changes on lxc-android-config in utopic that should be included in 14.09
[17:34] <imgbot> [17:35] <slangasek> barry: the package can't be a sync, there are other changes on there that are tied up with an lxc update
[17:35] <ogra_> sweeet !!
[17:35] <ogra_> sil2100, ^^
[17:35] <ogra_> 111 DONE !
[17:35]  * ogra_ loves changelogs like this
[17:35] <sil2100> Yay :)
[17:36] <slangasek> barry: bdmurray is not a lander currently - could you help him with the landing process?  He'll need to prep a source package and get it in as a line in the spreadsheet targeted to rtm
[17:36] <barry> slangasek, bdmurray for sure.  i'm going to take a short break for lunch, but bdmurray just ping me when you have a merge proposal ready
[17:36] <slangasek> barry: (since lxc-android-config doesn't do branch landings; I guess it usually is direct archive uploads, but that doesn't work here because rtm is still in landing freeze)
[17:37] <ogra_> wow, the delta from 110 to 111 is actually 3MB
[17:37] <slangasek> barry: not an MP, a source package
[17:37] <slangasek> 3MB in which direction?
[17:37] <ogra_> download shown on my phone
[17:37] <barry> slangasek: hmm, okay.  i'm not totally up on that procedure, but i'll try to help figure it out
[17:37] <slangasek> ogra_: oh :)
[17:37] <ogra_> :)
[17:37] <ogra_> well, that matches the three packages in the changelog
[17:37] <slangasek> barry: column F left blank, fill in column G, upload directly to the silo once assigned
[17:38] <sergiusens> slangasek: barry it would also need a version 'branching'
[17:39] <ogra_> sergiusens, not really
[17:39] <ogra_> we cant use lxc-android-config from utopic anymore anyway
[17:39] <sergiusens> ogra_: won't it conflict with utopic in the long run as they are not par on par
[17:39] <ogra_> important is oonly that the source package gets pulled from rtm when changing it
[17:39] <slangasek> it does need a unique version number
[17:39] <ogra_> sergiusens, we wont be able to sync them
[17:40] <sergiusens> ogra_: exactly; PES practices are to "version" branch when differing from what's in the archive to make it easy to spot in the future
[17:40] <ogra_> slangasek, why ? its a distinct archive and completely differnt distro
[17:40] <slangasek> bdmurray, barry: oh, please note that there's already a version of lxc-android-config pending landing, with lool's change; so the next version should be stacked on this: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=lxc
[17:41] <slangasek> ogra_: because it's *not* a completely different distro, it's a derived distro, and just like we use ubuntu suffixes to be able to talk about Debian vs. Ubuntu packages without confusion, we should use rtm suffixes to avoid ubuntu vs. ubuntu-rtm confusion
[17:41] <ogra_> except for human readability (and the ability to distinguish between the packages) there shouldnt be any need to match or non match the versions
[17:41] <slangasek> yes, and human readability is *very important* :)
[17:41] <ogra_> ok
[17:41] <ogra_> that i understand :)
[17:41] <lool> bdmurray, barry, slangasek: note that you can't land hte change from silo 4 without the other changes, so if you can land before silo 4, you want to ping us and we would have to merge your change in our silo
[17:41]  * ogra_ thought there was a technical reason
[17:42] <lool> current status is that some fixes are ready and another large change should help with stability some more and hopefully fix remaining issues
[17:42]  * ogra_ hugs image 111 ... non crashing dash :)
[17:42] <slangasek> lool: ok, so your silo 004 isn't ready to land yet?
[17:42] <ogra_> slangasek, yep
[17:42] <slangasek> lool: I don't think there's any hurry on this particular lxc-android-config change ... it may be simpler if we wait
[17:42] <lool> slangasek: it's not
[17:43] <bdmurray> slangasek: my lxc-android-config change is only necessary for the new version of whoopsie which isn't in ubuntu-rtm yet
[17:43] <slangasek> bdmurray: right
[17:43] <ogra_> welll
[17:43] <slangasek> bdmurray: which, well, also means that we probably want to land whoopsie+lxc-android-config together
[17:43] <ogra_> you could probably prepare a silo with both then :)
[17:43] <barry> slangasek, bdmurray why not try to fold your changes into lool's branch and reconfigure silo 4
[17:43] <barry> ?
[17:44] <slangasek> because they're unrelated and folding unrelated changes into a single silo causes a geometric increase in the time it takes to land? :)
[17:44] <lool> barry: well, if it's needed in rtm, then you dont want to block on another fix/feature (silo 4); otherwise silo 4 will become the black hole of all changes, absorbing each proposed upload  ;-)
[17:45] <ogra_> lool, well, you have to fix your stuff at some point too i guess :)
[17:45] <slangasek> lool: it's a soft requirement to have this in rtm... it's not product milestone driven
[17:45] <ogra_> so that it will land
[17:45] <barry> ok, you guys know best
[17:46] <sil2100> Well, I would leave silo 4 for now
[17:47] <ogra_> sil2100, right ... the question was if we want to stack new lxc-android-config on top or just land the fix and lool has to re-merge lxc-android-config
[17:50] <rsalveti> sil2100: trying to create a silo for line 83 but it failed
[17:51] <sil2100> rsalveti: hm, let me look
[17:51] <rsalveti> I tried first without specifying any distro, which of course failed
[17:51] <rsalveti> but now it seems I can't request it anymore
[17:52] <sil2100> rsalveti: you need to remove the UID
[17:52] <sil2100> (column number M)
[17:52] <rsalveti> sil2100: just delete?
[17:52] <sil2100> rsalveti: yeah, and try re-assigning - it normally gets cleaned up automatically in around 5 minutes, but you can just remove and reassign
[17:52] <lool> ogra_: right now silo 4 is still a bunch of hours away from landing, so if you need a lxc-android-config update, it's probably best to land it separately and I'd rebase silo 4
[17:53] <lool> the changes are fairly easy to move around
[17:53] <sil2100> Otherwise it thinks the silo is assigned
[17:53] <sil2100> (at least the assignment script)
[17:53] <rsalveti> sil2100: makes sense, lemme try
[17:54]  * Ursinha is glad the hideous request_id thing is going away soon :)
[17:57] <sergiusens> Ursinha: how soon?
[18:05] <Ursinha> sergiusens: as soon as the spreadsheet replacement is in place, I'd guess 1 to 4 weeks from now
[18:06] <bregma> sil2100, my silo #1 has passed its tests, ready to publish, hopefully under the final freeze wire
[18:10] <ogra_> Ursinha, spreasheet replacement ? crazy talk ... how would the world work without spreadsheets !!!
[18:11] <sil2100> bregma: \o/
[18:11] <sil2100> Ursinha: :D \o/
[18:11] <Ursinha> ogra_: lol
[18:11] <Ursinha> ogra_: citrain can do without that at least :P
[18:12]  * ogra_ hugs Ursinha
[18:40] <elopio> sil2100: ogra_, rsalveti: silo 5 + the tarball tested.
[18:41] <elopio> taking #8
[18:41] <ogra_> whee !
[18:52] <ogra_> bah, sigh
[18:52]  * ogra_ better waits for sil2100 to return  then ...
[18:53] <sil2100> !
[18:53] <sil2100> \o/
[18:53] <elopio> bfiller: sergiusens: so, unzip will now come preinstalled?
[18:54] <ogra_> sil2100, well, it waits for packaging ack ... and it struck me that we need john for th device tarball
[18:54] <sil2100> ogra_: so, if you lock everything in place, we can sms john-mcaleely's cell to get the device tarball out
[18:54] <ogra_> right
[18:55] <sil2100> ogra_: well, anyway, I guess we can publish 5 anyway now, right?
[18:55] <bzoltan> ogra_:  the #104 has only three failures on the first run... I did not wait for the second run when it is usually gets zero.
[18:56] <ogra_> sil2100, yeah ... the packaging is fie brw
[18:56] <sil2100> ogra_: it's publishing :)
[18:56] <ogra_> yay
[18:57] <rsalveti> so we need to publish it together with the device tarball
[18:57] <rsalveti> ogra_: are you taking care of that?
[18:57] <rsalveti> or do we need help from john-mcaleely
[18:57] <ogra_> rsalveti, we do, but he left his phone number for SMS
[18:57] <sil2100> ogra_, rsalveti: let's call him once we get 8 released
[18:57] <ogra_> right
[18:57] <rsalveti> great
[19:01] <elopio> sil2100: ogra_: can you give me a quick summary of why #8 is so important today?
[19:01] <elopio> from the spreadsheet, I see I should only try a compressed download, but I might be missing the important part.
[19:01] <ogra_> it was on the critical rtm14 list and tagged for 16th i understood
[19:02] <sil2100> elopio: it was said to be 'low risk', and it fixes a critical issue from our list
[19:02] <elopio> ok, I guess.
[19:03] <elopio> ogra_: sil2100: do you know how unzip will get installed?
[19:03] <sil2100> elopio: is it risky? I guess sergiusens can provide additional context if needed
[19:03] <ogra_> elopio, i would expect via a dependency
[19:04] <ogra_> right. sergiusens prepared that landing ... though it is a mandel  change i think
[19:04] <elopio> sil2100: doesn't seem risky.
[19:08] <elopio> mmm, I see. If I try to download a zip file it will say that no app can open it.
[19:08] <sergiusens> elopio: what's up
[19:08] <john-mcaleely> rsalveti, ogra_ not sure. do you need help?
[19:08] <sergiusens> elopio: only 7digital works
[19:08] <sergiusens> elopio: look at the webbrowser testplan
[19:08] <john-mcaleely> :-)
[19:09] <ogra_> john-mcaleely, we're waiting for silo 8 ... then we wanted to build an image
[19:09] <ogra_> how long did you plan to be around ?
[19:09] <john-mcaleely> ogra_, cool. I can come back on demand
[19:09] <sergiusens> elopio: unzip will get installed as udm depends on it, the citrain tool will not work correctly as it disables all repos
[19:09] <john-mcaleely> I'm about to eat, so will be awol for a bit.
[19:10] <john-mcaleely> is there an eta for silo8?
[19:10] <elopio> sergiusens: do you have a test account with purchased music?
[19:10] <sergiusens> elopio: https://wiki.ubuntu.com/Process/Merges/TestPlan/webbrowser-app  ("7 digital album downloads (if you don't have any albums you'll need to purchase one first")
[19:10] <ogra_> john-mcaleely, well, push away, i disabled the importer
[19:10] <sergiusens> elopio: no I don't have a test account
[19:10] <john-mcaleely> ogra_, ack
[19:10] <john-mcaleely> ogra_, firing up ssh now :-)
[19:10] <ogra_> :)
[19:11] <elopio> I will make one and update the test plan.
[19:11] <sergiusens> elopio: well, the reason there is no test account is because you need to make a purchase
[19:12] <sergiusens> elopio: so it needs credit/paypal or something
[19:12] <john-mcaleely> ogra_, sil2100 pushed/published/revealed/etc
[19:12] <sergiusens> elopio: I think charles has an account
[19:12] <ogra_> wheee
[19:15] <john-mcaleely> ok, I'll be along later to see it all landed safely. ping me if you need me (sms)
[19:15] <sil2100> \o/
[19:15] <sil2100> So now just 8 and we can kick the final image (tm)
[19:16] <john-mcaleely> heh
[19:17] <ogra_> ++
[19:25] <elopio> sergiusens: the download on the transfer indicator ssays "Unknown Download"
[19:26] <sergiusens> elopio: that's fine
[19:26] <sergiusens> elopio: can you talk to bfiller... I'm packing
[19:27] <elopio> sergiusens: I can. Have a good trip.
[19:29] <sil2100> elopio: is that some visual problem?
[19:29] <elopio> sil2100: well, it should display the name of the zip being downloaded.
[19:29] <elopio> but it's probably not introduced by this silo. I'm flashing my mako to see what happens there.
[19:30] <sil2100> elopio: ok
[19:30] <elopio> this successfully opens the music player, and plays the songs. Which is awesome.
[19:38] <ToyKeeper> Okay, one silo in progress, start building a "final" image, and then ... restart the massive test-everything plan?
[19:38] <sil2100> ToyKeeper: yes... but olli recommended to only try and test the delta, if possible
[19:39] <ToyKeeper> I'm going to need to find a lot more info about what changed since 109.
[19:39] <olli> oh, I think I said, it's QA's call
[19:39] <ToyKeeper> It seems a lot happened while I was asleep.
[19:39] <olli> but if it was me...
[19:39] <sil2100> Well, I would also prefer testing only the delta, but in this case the delta will be big anyways
[19:40] <ToyKeeper> "Just delta" is good though...  it seems that test plan takes like 12 to 16 hours otherwise.
[19:40] <sil2100> Since if something lands that is a low-level component, I think we need testing the components that are using it
[19:40] <sil2100> Oh my
[19:40] <sil2100> ToyKeeper: so, normally when davmor2 does promotion testing he does it in 4-6h, does he only do a subset every time?
[19:41] <ToyKeeper> I'm not sure now, but it must either be a subset or a different plan.
[19:41] <sil2100> I think he has a spreadsheet according to which he performs the testing
[19:41] <elopio> sil2100: we changed to this huge spreadsheet that jibel and rhuddie prepared.
[19:42] <elopio> we don't need to run all the tests everytime. Well, we can't anyway.
[19:42] <elopio> we will just update the results of the more important parts for each release. It will show how much we have tested and on which versions, so somebody can make a good decision about what to do with the latest release.
[19:43] <elopio> as this release is important, I guess ToyKeeper and myself will be testing everything we can until we hit the deadline.
[19:43] <elopio> olli: does it sound right?
[19:45] <sil2100> elopio: let's wait for olli to comment :)
[19:45] <sil2100> elopio: but anyway, and doubts regading silo 8?
[19:48] <olli> elopio, are you saying, incremental tests?
[19:48] <olli> jfunk, I think that should be your call
[19:49]  * sil2100 would be happy enough if we get our candidate image today
[19:49] <olli> yeah
[19:49] <ogra_> define today :)
[19:49] <jfunk> olli: that's what I told them to do :)
[19:49] <olli> in any case, I think incremental testing on an image tha was tightly controlled / managed is feasible
[19:49] <ogra_> today.eu ... today.us ?
[19:49] <jfunk> ust test the delta
[19:49] <ogra_> :)
[19:50] <olli> elopio, sil2100 ^
[19:50] <olli> jfunk and I are in agreement
[19:50] <sil2100> \o/
[19:50] <ogra_> so we just need silo 8 now :)
[19:50] <sil2100> Righto, so excited
[19:51] <ToyKeeper> I see bugs for silos 6, 12, and 15...  Bug #1379296, Bug #1381871, Bug #1376467.  What are the others?
[19:51] <elopio> sil2100: I was trying to download a big photo to see what happens.
[19:51] <elopio> it seems the unknown download is not specific to it. And the blinking on the bar happens only for the zip files.
[19:51] <elopio> so it has bugs, but probably nothing that should delay us even more.
[19:51] <sil2100> elopio: so it's not introduced by the silo then?
[19:54] <elopio> sil2100: the blinking it's introduced by the silo, as without the silo it's not possible to download the zip
[19:54] <sil2100> Anyway, just waiting for the final verdict
[19:54] <sil2100> Ah, the blinking - yes, but not the 'unknown download', right?
[19:55] <elopio> sil2100: no, that seems a different old issue, because I see it also with photos and without the silo.
[19:55]  * sil2100 just checked the unzip dependency seems to be added to u-d-m
[19:55] <sil2100> Good to know
[19:55] <elopio> I will report both. And will approve the silo.
[19:56] <sil2100> Oh! :)
[19:56] <sil2100> Does it mean I can press publish?
[19:57] <ogra_> soo impatient :)
[19:58] <sil2100> Would love the build to start, and besides - my girlfriend needs to snatch me for some hours
[19:58] <sil2100> elopio: \o/
[19:58] <sil2100> elopio: really big thanks for the testing-under-pressure
[19:59] <ogra_> yay
[19:59] <ogra_> yeah, QA rocks !
[19:59] <sil2100> kenvandine: can you approve https://code.launchpad.net/~michael-sheldon/content-hub/download-zip-integration/+merge/237764 ?
[19:59] <sil2100> kenvandine: top-approve that is
[19:59] <sil2100> As I see it's reviewed
[20:02]  * sil2100 reviews the packaging diff
[20:02] <kenvandine> sil2100, sure!
[20:02] <sil2100> ogra_: if you want to double check, it's here: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-008-2-publish/34/artifact/packaging_changes_ubuntu-download-manager_0.9+14.10.20141014.1-0ubuntu1.diff
[20:02] <ogra_> looks fine
[20:02] <sil2100> ogra_: the only worrying thing are the removed silos, but I think those are some bs symbols anyway
[20:03] <sil2100> Like, redundant
[20:03] <ogra_> yep
[20:03] <sil2100> kenvandine: thanks!
[20:03] <ogra_> sil2100, removed silos ?
[20:03] <sil2100> ...symbols
[20:03] <ogra_> you mean symbols, right ? :)
[20:03] <sil2100> ...
[20:03] <sil2100> ;)
[20:03]  * sil2100 waits for top-approval
[20:04] <kenvandine> sil2100, done
[20:05] <sergiusens> ah, I knew we would miss one
[20:05] <sergiusens> cheers
[20:05] <kenvandine> woot
[20:05] <ogra_> yay
[20:06] <sil2100> \o/
[20:07] <sil2100> ogra_, olli, slangasek: ok, I go AFK for ~2h now, but I'll be back afterwards to check what's up
[20:07] <olli> sil2100, thx
[20:07] <olli> sil2100, I wasn't following 1 line status summary
[20:07] <sil2100> ogra_: if you could check rmadison and kicketh teh image once that happens, would be excellent
[20:07] <ogra_> sil2100, ok, i'll watch rmadison, kick a rootfs and later unleash system-image
[20:07] <ogra_> *snap* :)
[20:08] <sil2100> olli: I sent out a quick summary of the situation
[20:08] <sil2100> olli: and now I AFK for some time
[20:08] <ogra_> olli, its all waiting now ...
[20:08] <sil2100> All in all, we look good it seems, good for QA
[20:08] <ogra_> (and two commands from me at the right time)
[20:08] <sil2100> (once the image finishes)
[20:10] <pmcgowan> sil2100, ogra_ how much landed?
[20:10]  * pmcgowan checks email
[20:10] <ogra_> nearly everything that was planned for 1016
[20:10] <pmcgowan> wow awesome
[20:11] <olli> sil2100, everybody: well done!
[20:12] <olli> ogra_, this is a service announcement... ... "An important message will be sent to @phablet in a few minutes, please sharpen your email clients"
[20:12] <olli> scnr, thought this was funny
[20:12] <ogra_> LOL
[20:12]  * ogra_ hugs olli
[20:21] <elopio> olli: bug #1382216 and bug #1382218
[20:22] <olli> pmcgowan, ^
[20:24] <pmcgowan> while I am looking sergiusens  ^^^
[20:25] <sergiusens> pmcgowan: read, but need to go... I'll do a -> charles ^^
[20:25] <sergiusens> as it's indicator
[20:25] <ogra_> thats becoming a flowchart !
[20:26] <elopio> I'll go have lunch before it completes the circle :)
[20:26] <ogra_> heh
[20:27] <brendand> ogra_, when's the new image out?
[20:28] <ogra_> brendand, 008 needs to completely land ...
[20:28] <brendand> ogra_, so not for a few more hours?
[20:28] <ogra_> then i'll trigger a build (and will have to kick th system-image manually so it lands with the device tarballs
[20:28] <ogra_> yeah
[20:28] <ogra_> 2h at least i'd say
[20:34] <ogra_> build started :)
[20:39] <imgbot> [20:58] <charles> sergiusens, :-)
[21:08] <Elleo> charles: with respect to the "Unknown Download" label one we're now setting the filename as the title on the download's metadata in the webbrowser (as of the 7digital stuff landing), so that might help there
[21:19] <charles> Elleo, Cool. I should be able to do a patch tonight... I'm flying out tomorrow morning and need to run a couple of errands during business hours
[21:21] <Elleo> charles: sure, no rush from my side, just thought I'd let you know about it :)
[21:21] <charles> Elleo, *nod*
[21:22] <Elleo> charles: I think at the moment we might only do it in the webbrowser if we explicitly get given a filename, so I might need to improve that a bit for cases where we need to parse the URL for a filename instead; but that shouldn't impact you (other than it not working absolutely everywhere)
[21:30] <olli> sil2100, ogra_, brendand, elopio, ToyKeeper, eod'ing call my cell if you need something
[21:31] <ogra_> olli, enjoy ...
[21:31] <ToyKeeper> olli: Have a good evening.  :)
[21:54] <imgbot> [21:54] <imgbot> [21:54] <ogra_> \o/
[21:55] <ogra_> and on that note ... i'm off to bed
[22:01] <rsalveti> nice
[22:01] <rsalveti> enjoy :-)
[22:09] <ToyKeeper> Wait, what?  That was a fast build...
[22:09] <ToyKeeper> Oh, I guess not.  Time doesn't usually fly when I'm waiting for a pot to boil.
[22:36] <sil2100> \o/
[22:43] <sil2100> Thanks everyone, I guess it's all in ToyKeeper's and elopio's hands now!
[22:51] <ToyKeeper> sil2100: Bad news.  Another first-minute feature is broken.
[22:51] <ToyKeeper> The edge tutorial fails when pulling down the top edge.  :(
[23:07] <ToyKeeper> Bug #1382267
[23:14] <sil2100> ToyKeeper: ouch, was that working on 109?
[23:14] <ToyKeeper> Yes, worked fine in 109.
[23:15] <sil2100> Crap
[23:15] <sil2100> I wonder which landing broke it, hmm
[23:15] <sil2100> ToyKeeper: is it reproducible?
[23:15] <ToyKeeper> sil2100: Yes, it is.
[23:16] <sil2100> After a reboot I assume? Damn, maybe kgunn can find someone to take a quick look
[23:17] <kgunn> sil2100: ToyKeeper what landed in the meantime ?
[23:17] <kgunn> that's a unity thing....and a _lot_ of folks are traveling
[23:17] <kgunn> already
[23:17] <ToyKeeper> I'm not sure if it failed on 111...  but it worked in 109.
[23:17] <sil2100> kgunn: so its this:
[23:17] <sil2100> http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/111.commitlog
[23:18] <sil2100> and
[23:18] <sil2100> http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/112.commitlog
[23:18] <ToyKeeper> Yow, huge change set in 112.
[23:18] <sil2100> Damn, commitlogs broken again
[23:18] <sil2100> ToyKeeper: it was just 3 landings, but one of them was big
[23:19] <sil2100> ToyKeeper: hm, could you give me the steps to reproduce?
[23:19] <sil2100> I'll flash 111 and check if it's b0rken there
[23:19] <ToyKeeper> sil2100: I'm already flashing 111.
[23:20] <sil2100> Ah, ACK :)
[23:20] <ToyKeeper> sil2100: The steps are really simple though...  just do what the edge tutorial says to do, and it fails after the step about pulling down from the top.
[23:20] <kgunn> ToyKeeper: sil2100 ....if i'm just guessing, i'd finger 111, it only landed qtmir...i'll be interested to hear your findings ToyKeeper
[23:20] <ToyKeeper> sil2100: Could you perhaps check 110?
[23:21] <sil2100> ToyKeeper: 110 has no changes in it
[23:21] <ToyKeeper> Oh, hmm.
[23:21] <sil2100> ToyKeeper: it was a build triggered automatically by accident ;)
[23:21] <sil2100> Due to not all system-image bits being disabled
[23:22] <sil2100> kgunn: yeah, 111 is only qtmir and indicator-sound
[23:24] <kgunn> racarr: hey you on?
[23:25] <kgunn> so we're highly suspicious of qtmir landing in image 111....seems to break the "Edge demo" tutorial in thebeginning
[23:25] <kgunn> i see only 4 commits to qtmir for 10/13
[23:25] <kgunn> i'm guessing that's what landed here
[23:25] <kgunn> sil2100: ^ would that be correct....prolly landed on utopic 10/13 then took that long to land in rtm
[23:26] <popey> ubuntu-touch/ubuntu-rtm/14.09-proposed #94 - unity8 crash on start
[23:26] <popey> on mako
[23:26]  * kgunn remembers now camako said Saviq forked qtmir briefly...
[23:26] <popey> wheee, 3 apports on my mako
[23:26] <sil2100> kgunn: damn... if that'll be true, then we have no choice but to fix that
[23:26] <popey> unity8 media-hub and maliit
[23:27] <sil2100> A revert would mean we bring back a blocker
[23:27] <sil2100> popey: ouch...
[23:27] <ToyKeeper> Okay, broken in 111 too.
[23:29]  * sil2100 sighs
[23:29] <sil2100> Saviq: ^
[23:29] <sil2100> kgunn: Saviq is in travel now?
[23:29] <Saviq> sil2100, not yet
[23:29] <kgunn> yes
[23:29] <kgunn> oh..maybe not
[23:29] <sil2100> uh, heeey
[23:29] <sil2100> I didn't WANT you to answer ;p
[23:29] <popey> same on my nexus 7
[23:29] <kgunn> Saviq: i'm thinking it's racarr's commit that prolly needs revert
[23:29] <sil2100> Just wanted to know if you're around tomorrow
[23:29] <Saviq> sil2100, kgunn, I'm thinking the edge demo did not get updated for the new indicators
[23:30]  * Saviq tries
[23:30] <ToyKeeper> Saviq: It worked in 109, and 109 had the new-style indicators.
[23:30] <kgunn> dude it's seriously late
[23:30] <Saviq> oh
[23:30] <Saviq> kgunn, it's *early*
[23:30] <kgunn> lol
[23:30] <kgunn> one way to look at it
[23:30] <sil2100> Saviq: really, no use in you working so late
[23:30] <popey> well, my crash was uploaded apparently
[23:31] <sil2100> We appreciate, but we don't want a half-asleep Saviq in the morning
[23:31] <sil2100> popey: hm, was that like the latest ubuntu-rtm for mako/flo ?
[23:31] <Saviq> sil2100, I'll be half-asleep no problem, flying in 4h
[23:32] <ToyKeeper> Regardless, I'm going to check for anything else we might care about.
[23:32] <ToyKeeper> ... as soon as the reflash is done.
[23:32] <Saviq> sil2100, kgunn, there's only two qtmir commits that went in... I don't see how they can be related
[23:33] <ToyKeeper> If we can make a 113 with the tutorial fixed, awesome.
[23:33] <sil2100> The indicator-sound upload shouldn't matter
[23:33] <sil2100> Saviq: oh, so early?
[23:33] <Saviq> sil2100, yeah
[23:34] <ToyKeeper> I don't leave for another 48 hours or so...  but then, I'm also showing up last-minute.
[23:34] <sil2100> I'm flying on Sunday
[23:35] <ToyKeeper> s/48 hours/72 hours/  ... I can count, really.
[23:36] <Saviq> sil2100, I'm trying to cram up some sightseeing on the weekend
[23:36] <Saviq> sil2100, the weekend after I'm in BOS so that's the only chance
[23:37] <sil2100> Ah, ok, makes sense :)
[23:38] <sil2100> ToyKeeper: so, please continue for now, let's just report all findings to olli and all the others in the end
[23:38] <sil2100> kgunn, Saviq: thanks for the fast reaction
[23:38] <Saviq> sil2100, just flashed 109 to check
[23:39] <sil2100> But I think I need to go to sleep now, staying late twice in a row is bad
[23:39] <sil2100> And my girl will certainly kill me
[23:39] <popey> sil2100: it worked previously
[23:39] <popey> sil2100: just updated to latest (94) and it broke.
[23:39] <popey> sil2100: i can flash back to #93 to prove that if you want
[23:39] <Saviq> ToyKeeper, just flashed 109, after pulling indicators down I don't get the next step
[23:40] <Saviq> the only explanation is the new indicators, really
[23:40] <sil2100> popey: if you could double-confirm then it would be great, we'll have to sort this out once we get through with krillin for this week
[23:40] <popey> sure thing
[23:40] <popey> doing now
[23:40] <ToyKeeper> Great.  Then I wonder how long it has been failing, or if there's a race condition.
[23:40] <sil2100> Saviq: oh
[23:40] <sil2100> Ok, since I thought it was working fine on 109
[23:41] <sil2100> Anyway, I suppose it might not be considered as a total blocker... but let's leave it up to the product managers to decide
[23:41] <sil2100> Good night everyone!
[23:41] <popey> nn
[23:50] <Saviq> ToyKeeper, http://paste.ubuntu.com/8576500/
[23:50] <Saviq> kgunn, ↓
[23:50] <Saviq> ↑↑ even
[23:50] <kgunn> hehe
[23:51] <kgunn> Saviq: should i just mp it on qtmir rtm
[23:51] <ToyKeeper> Saviq: That's surprisingly short.
[23:52] <kgunn> or sorry unity8 rtm
[23:52] <Saviq> kgunn, it's a very naive fix, but seems to work
[23:52] <Saviq> ToyKeeper, yeah, the whole problem was that you just couldn't see the step, because it tried to anchor to a non-existing (any more) object
[23:55] <racarr> kgunn: Hey!
[23:55] <racarr> kgunn: Sorry wasnt watching this channel
[23:55] <kgunn> racarr: np, you're cool....
[23:55] <Saviq> kgunn, from a 2am look at the thing, it should Just Work, so MP it against lp:unity8/rtm-14.09 and it'll get tested, whether same silo, your call
[23:55] <kgunn> ended up being a small chagne in edge demo code
[23:55]  * Saviq needs to finish up packing and get some sleep
[23:56] <racarr> kgunn: Ok great :)
[23:56] <kgunn> Saviq: ack...will do the needful
[23:56] <Saviq> see you all there! o/
[23:56] <kgunn> o/
[23:56] <racarr> Cya!