[07:54] <didrocks> ev: ok, I think I'll need your help for this rsync issue. I have some progress but it seems to be related to private/public IP
[07:59] <didrocks> brb
[08:34] <Mirv> sil2100: I'm creating a recipe build for lp:appmenu-qt5 into the PPA
[08:35] <Mirv> sil2100: should you then somehow modify lp:appmenu-qt to not build appmenu-qt5 binary package?
[08:38] <sil2100> Mirv: sure, let me do that
[08:38] <sil2100> hm, I didn't handle the case of deprecating the old appmenu-qt5 yet, but I'll take care of it today
[08:38] <sil2100> Mirv: thanks for reminding :)
[08:42] <didrocks> sil2100: hey! before the meeting, do you mind running the webbrowser-app tests on mako on the latest image?
[08:42] <didrocks> just to ensure that's a flaky result
[08:45] <sil2100> didrocks: webbrowser-app from daily-build or from the image?
[08:45] <didrocks> sil2100: from the image
[08:45] <didrocks> as some tests are failing, but I guess it's a random failure
[08:45] <sil2100> didrocks: ACK, upgrading to latest image right now, testing once that's done
[08:46] <didrocks> thanks
[09:08] <sil2100> hmm... first run of webbrowser-app AP tests resulted in unity8 hanging, no reaction to touch
[09:08] <sil2100> Retrying
[09:12] <sil2100> cihelp: can anyone with access to q-jenkins help us out?
[09:12] <sil2100> psivaa_: hello!
[09:12] <psivaa_> sil2100: hi
[09:13] <sil2100> psivaa_: it seems cu2d cannot run all the stacks automatically because of a sometimes-happening-bug
[09:13] <sil2100> psivaa: cu2d thinks that the unity stack is still running
[09:13] <psivaa> sil2100: ok, link please?
[09:14] <sil2100> psivaa: we would need someone to log into q-jenkins, go to the cu2d work directory (in /var) and remove the stack.building (or something like that) from the unity stack directory
[09:14] <psivaa> sil2100: ack, will do that
[09:14] <sil2100> psivaa: since there seems to be a leftover file there
[09:14] <sil2100> psivaa: don't remember the exact naming, but you'll know when you'll be in the unity directory :)
[09:14] <sil2100> psivaa: thanks!
[09:18] <psivaa> sil2100: done
[09:19] <sil2100> psivaa: thanks again ;)
[09:19] <psivaa> sil2100: yw
[09:19]  * sil2100 tries to re run all the stacks now
[09:19] <sil2100> \o/ it works
[09:23] <Mirv> yeah I'm getting an upload error with appmenu-qt5 until appmenu-qt itself is patched. but the recipe is there, so builds will happen automatically.
[09:25] <sil2100> Mirv: thank you!
[09:32] <didrocks> ogra_: coming?
[09:38] <Mirv> sil2100: oh did you deploy the libhud-client2 change to phone stack already, so the current waitforstacks build there will have it correct?
[09:39] <sil2100> Mirv: yes
[09:40] <sil2100> Mirv: all stacks should be redeployed to have all the missing extra packages
[09:42] <Mirv> ok, great, then I'll just let that run until there are some results and prepare my phone
[09:52] <didrocks> sil2100: Mirv: please don't release anything yet
[09:52] <popey> psivaa: seems to be a regression between #121 and #131
[09:52] <didrocks> see ^
[09:52] <popey> Music no longer plays after screen blanks.
[09:52] <popey> be good to get someone else to confirm, to make sure it's not my dodgy phone ☻
[09:53]  * popey re-flashes clean #131 to confirm.
[09:54] <psivaa> popey: if you'd like to get confirmation on the music regression, then it's better to find someone in QA. i only run the tests from the devices in the lab
[09:54] <popey> (this is my dev phone so I could have broken it, so it *might* not be a regression)
[09:55] <popey> psivaa: who would such a person be, with a mako?
[09:56] <Mirv> ok
[09:57] <didrocks> popey: I'm flashing, but I guess psivaa should help as well
[09:57] <didrocks> psivaa: we are blocking production, we should all work together trying to get it back on shape
[09:57] <didrocks> whatever duties we are in
[09:57] <asac> hi
[09:58] <didrocks> hey asac
[09:58] <asac> whats up?
[09:58] <didrocks> 10:52:29    popey | Music no longer plays after screen blanks.
[09:58] <didrocks> asac:  ^
[09:58] <asac> when did this start?
[09:58] <didrocks> we don't know, we know it worked on #121
[09:58] <psivaa> didrocks: popey: is it only occurring in mako?
[09:58] <didrocks> psivaa: we only have mako to test for now
[09:58] <popey> i only have a mako
[09:59] <asac> could be many things i feel... would be great to narrow this down a bit more
[09:59] <popey> if someone were to send me other devices I'd test in parallel every morning over breakfast :D
[09:59] <didrocks> asac: well, first, let's confirm
[09:59] <popey> +1
[09:59] <didrocks> then, let's see on which image it started
[09:59] <asac> without knowing anything i would throw that at phonedation
[09:59] <asac> saying its a powerd thing :)
[09:59] <popey> it could well be my busted up phone setup from testing stuff
[09:59] <ogra_> didrocks, argh, i overslept ...
[09:59] <popey> yeah, hang fire
[09:59] <didrocks> (flash in progress)
[09:59] <didrocks> ogra_: no worry ;)
[09:59] <didrocks> ogra_: welcome to firedrill again!
[09:59] <popey> ogra_: ubuntu phone alarm not working? ☻
[09:59] <ogra_> popey, heh
[10:00] <didrocks> popey: I clearly hope it will be http://blamepopey.com/
[10:00] <popey> uh-huh

[10:00] <asac> i dont think its a full firedrill if we are still confirming... like defcon 3 maybe :)
[10:00] <didrocks> heh
[10:00] <didrocks> asac: well, firedrill as we are blocking the other planned release meanwhile :p
[10:00] <asac> yeah
[10:00]  * sil2100 tries on his mako as well
[10:01] <asac> i really think we need something like defcon states
[10:01] <didrocks> ok, I'll put daftpunk music on it
[10:01] <popey> PHONECON 1
[10:01] <asac> that we also associate with certain behaviours
[10:01] <asac> like phonecon 1 means: please refrain from all uploads
[10:01] <asac> (e.g. like yesterday)
[10:01] <didrocks> how daft punk music can be stopped on sleep? :)
[10:01] <popey> can we have a flashing light please?
[10:01] <didrocks> my mako wouldn't do that :p
[10:01] <ogra_> asac, but please with a shiny wall lamp like in wall games ...
[10:01] <popey> and an AWOOOGAH! noise
[10:01] <asac> 3 means: if you upload, even safe feeling things, please talk to LT
[10:01] <ogra_> *wargames
[10:01] <asac> wargames :)
[10:01] <asac> nice
[10:01] <ogra_> .... need .... coffeee ...
[10:02] <asac> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Dc_five_1.svg/150px-Dc_five_1.svg.png
[10:02] <ogra_> ...cant.... type ...
[10:02] <sil2100> popey: running a song and pressing the power button doesn't stop the music, but let me wait until the screen goes out by itself
[10:02] <asac> http://en.wikipedia.org/wiki/DEFCON
[10:02] <didrocks> asac: I hope it's a false alarm, really, if we rebuild, there is an lxc upload in the release pocket
[10:02] <ogra_> yeah
[10:02] <popey> sil2100: i waited
[10:02] <asac> "Nuclear war is imminent"
[10:02] <didrocks> flash quicker !:f::fdsfdsffds phone
[10:02] <didrocks> 5 seconds to download all images
[10:02] <didrocks> 10 minutes to install :p
[10:02] <sil2100> popey: uuuu
[10:02] <sil2100> didrocks: confirming regression, I guess?
[10:03] <ogra_> asac, yours is upside down
[10:03] <didrocks> sil2100: you are?
[10:03] <ogra_> http://2.bp.blogspot.com/_djUj8mqfpm8/TL31FNnvGPI/AAAAAAAACT4/Pvp7jqeWems/s1600/war-games-defcon-2.jpg
[10:03] <ogra_> and we indeed need the photogaph too :)
[10:03] <sil2100> didrocks, popey: waited for the screen to go off, after going of and waiting 2-3 seconds stops the music
[10:03] <didrocks> *shrugh*
[10:04] <popey> just copying music onto re-flashed phone to confirm
[10:04] <didrocks> asac: you followed the exact same procedure on image 121, you didn't click on the button?
[10:04] <didrocks> popey: reflashed already for you?
[10:04] <popey> ya
[10:04] <didrocks> come on, my mako is too slow…
[10:04] <popey> i probably started a few second before you
[10:04] <didrocks> ah ok ;)
[10:04] <didrocks> (it's rebooting)
[10:04] <ogra_> i saw someone complain on IRC that his music goes choppy after a few seconds in suspend
[10:05] <ogra_> (yesterday)
[10:05] <didrocks> ogra_: bug fix, not choppy anymore
[10:05] <didrocks> just no sound :p
[10:05] <popey> confirmed
[10:05] <ogra_> lol
[10:05] <popey> goes silent after ~50 seconds of playing
[10:05] <ogra_> didrocks, well, if it is fixed, lets promote it
[10:05]  * popey files a bug
[10:06] <didrocks> grrr, mtp doesn't work here to copy the music
[10:06] <popey> takes a while
[10:06] <popey> (to become available)
[10:06] <ogra_> yep, satrts pretty late in the boot
[10:07] <didrocks> ok, we need to find where is started
[10:07] <didrocks> let's bisect
[10:07] <didrocks> popey: so, image 121 was good, let's flash 127, right?
[10:07] <didrocks> if we still have it
[10:07]  * didrocks looks at cdimages
[10:08] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20140113.1.changes
[10:08] <ogra_> i put my bets on unity-voice-service
[10:08] <didrocks> ogra_: which image is it?
[10:08] <popey> bug 1269744
[10:08] <ogra_> oh, nice, i didnt know we ship libdvdnav ...
[10:08] <popey> yes, #121 is fine
[10:08] <ogra_> finally i can watch movies from disk on my phone :P
[10:09]  * popey flashes #127
[10:09] <didrocks> not sure why, mtp is totally screwed on my system
[10:09] <didrocks> but you already confirmed
[10:09] <didrocks> so, let me reflash with --bootstrap 126
[10:09] <didrocks> while popey is doing 127 ;)
[10:09] <ogra_> didrocks, well, it should have come up by now
[10:10] <ogra_> LOL
[10:10] <didrocks> sil2100: can you try 129?
[10:10] <ogra_> asac, ... see topic  :)
[10:10] <didrocks> let's try to redice the bisecting time
[10:10] <popey> Interestingly War Games got the DEFCON numbers the wrong way round. I can never remember which is the right way
[10:10] <popey> The directors commentary on the War Games DVD is interesting like that ☻
[10:11] <sil2100> didrocks: will try
[10:11] <ogra_> popey, and with libdvdnav on the phone i can watch it on my phone !
[10:11]  * didrocks adds -b
[10:11] <popey> hah
[10:11] <ogra_> (or at least navigate)
[10:11] <popey> 1 (in the flim) is bad, turns out in US speak 5 is bad.
[10:12] <ogra_> oh ... navigate .... how did jonogate turn out
[10:12] <popey> or the other way.. meh
[10:12]  * ogra_ chcks the news sites ... that kept me awake tonight, juggling trolls
[10:12] <popey> meh
[10:14]  * didrocks wonders if we should make a revert/bisecting hangout party
[10:15] <didrocks> ogra_: unity-voice came in which image?
[10:15] <ogra_> didrocks, 127
[10:15] <ogra_> well, it came in 126
[10:15] <didrocks> ok we'll see with my 126 test
[10:16] <didrocks> ah ok
[10:16] <psivaa> popey: didrocks: my maguro is ready to flash. which image do you want me to flash that with?
[10:16] <psivaa> i only have a maguro
[10:16] <didrocks> psivaa: if you can try 125
[10:16] <didrocks> psivaa: TBH, I guess mako/maguro has potentially the same issue
[10:16] <psivaa> didrocks: ack
[10:16] <didrocks> thanks ;)
[10:16]  * ogra_ would love to help ... but 25min download time ... i guess you have found it by then
[10:16] <didrocks> ogra_: that's why I didn't ask you ;)
[10:16] <popey> heh
[10:16] <ogra_> :)
[10:16] <didrocks> 5s to download an image here
[10:16]  * popey has a local mirror ☻
[10:17] <didrocks> my phone is the only limitation :p
[10:17] <popey> http://popey.mooo.com/mirror/
[10:17] <ogra_> popey, hmm, o probably have 20TB of spare disks rotating in the house ... i should do that too
[10:17] <ogra_> s/o/i/
[10:17]  * popey hugs btrfs ☻
[10:17] <popey> going to switch my laptop to btrfs for 14.04
[10:18] <didrocks> popey: nicely done :) if I want to be faster, I should get a smaller ethernet cable or plug directly to the fiber ;)
[10:18] <popey> hahah
[10:18] <didrocks> ahah ;)
[10:18] <didrocks> ok, phone rebooting, let's hope mtp will act normally this time
[10:19]  * popey testing 127
[10:20] <popey> #127 is okay
[10:20] <didrocks> popey: hum, maybe the mtp issue is client-side
[10:20] <didrocks> popey: I see the N4
[10:20] <didrocks> but an empty folder
[10:20] <popey> i see that
[10:20] <didrocks> and can't create anything
[10:20] <popey> then after a while it appears as mountable
[10:20] <popey> with folders
[10:20] <popey> takes ~30s
[10:20] <didrocks> ok, let's continue waiting
[10:20]  * sil2100 reboots to 129
[10:21] <popey> want me to go back to 123?
[10:21] <didrocks> popey: sounds legit, yeah
[10:21] <didrocks> sil2100: discare the 129 test ;)
[10:21] <sil2100> 127 is broken?
[10:21] <popey> 127 is fine
[10:21] <sil2100> Oh, ok
[10:21]  * popey updated the bug
[10:21] <popey> oof, "Server error, please contact an administrator.
[10:21] <popey> I am breaking *everything* today
[10:22] <cjwatson> didrocks: no idea why you weren't auto-whitelisted on ubuntu-devel, but I've manually whitelisted you now
[10:22] <didrocks> cjwatson: ah thanks, yeah, I mentionned it yesterday, that's quite new (but I don't post often to ubuntu-devel)
[10:22] <popey> bug 1269414
[10:23] <ogra_> so in 128 we had a new unity-mir ... (and application-api)
[10:23] <sil2100> didrocks: on 129 it's broken, I mean, sound is stopped after screen goes black
[10:23] <ogra_> oh
[10:23] <ogra_> and libmediainfo
[10:23] <sil2100> didrocks: so just confirmed
[10:24] <didrocks> popey: I wonder if my client mtp side is broken
[10:24] <didrocks> still an empty folder
[10:24] <didrocks> grrr, can't test because of that
[10:24] <ogra_> didrocks, adb push ...
[10:24] <didrocks> ogra_: do you know which folder?
[10:24] <ogra_> /home/phablet/Music
[10:24] <didrocks> thanks
[10:24] <ogra_> iirc
[10:24] <cjwatson> didrocks: it *should* have just worked since you're (transitively) in ubuntu-dev and didrocks@ubuntu.com is attached to your LP account; but I can't see the IS-run script to sync all that over to mailman unfortunately
[10:24] <cjwatson> (as far as I know)
[10:25]  * popey updates the daily test spreadsheet to add a manual test to leave music playing for 60s
[10:25] <ogra_> ++
[10:25] <didrocks> cjwatson: ok, let's take of this if this reproduce again, thanks
[10:26] <didrocks> NOT broken on 126
[10:26] <didrocks> popey: sil2100 ^
[10:26] <popey> ok, flashing 123 right now
[10:26] <didrocks> well, not needed I guess
[10:26] <didrocks> so, it's between 126 and 127
[10:27] <popey> no
[10:27] <didrocks> so what's in 127
[10:27] <popey> 127 is fine
[10:27] <didrocks> hum
[10:27] <sil2100> So 128 caused it?
[10:27] <didrocks> NOT broken, you mean?
[10:27] <didrocks> so 128 or 129
[10:27] <popey> oh, duh
[10:27] <sil2100> Right
[10:27] <didrocks> psivaa: ^
[10:27] <sil2100> Since 129 is broken
[10:27] <didrocks> ok, let's try 128
[10:28] <psivaa> ok my flashing is halfway. so i'll wait till it finishes
[10:28] <ogra_> yeah, i think it is the unity-mir update
[10:28] <ogra_> thats usually responsible for the app lifecycle
[10:28] <didrocks> can be yeah
[10:28] <didrocks> greyback: around? ^
[10:28] <ogra_> i pinged ricmm_ in -touch
[10:28] <didrocks> ah great :)
[10:29] <ogra_> (there is a clienbt sprint in .za ... they should all be awake)
[10:29] <sil2100> Too bad it's not really easily integration-testable
[10:29] <asac> ricmm was very keen to know if things did regress... so i am sure he will be super happy that we found something :)
[10:29] <ogra_> lol
[10:29] <didrocks> ahah, it's a way of seeing it :)
[10:29] <ogra_> sury
[10:29] <didrocks> asac: I'm just hoping that what entered distro since 4am didn't break anything else :p
[10:29] <didrocks> as we'll need to rekick an image
[10:29] <asac> really, he figured the rssreader thing because he was expectring regressions and since all dashboard was good had time left :)
[10:30] <ogra_> asac, oh so you think we need to introduce more regressions in the future so he doesnt get bored ?
[10:30] <greyback> didrocks: in meeting, sorry
[10:30] <asac> hehe
[10:30] <greyback> didrocks: ricmm also in meeting
[10:31] <didrocks> greyback: we'll continue confirming it's unity-mir, just know that potentially you are blocking the production line, so, as soon as you are ready… ;)
[10:32] <ogra_> didrocks, now you destroyed all concentration in the meeting and it will take twice as long !
[10:32] <ogra_> :)
[10:32] <sil2100> !
[10:32] <sil2100> ;)
[10:33] <didrocks> ogra_: if only we can add some action/suspens music remotely to them
[10:33] <didrocks> in background
[10:33] <didrocks> during their meeting :p
[10:34] <popey> they should put this on the projector https://upload.wikimedia.org/wikipedia/commons/f/fa/Dc_one_1.svg
[10:34]  * didrocks will build something soon at this pace :p
[10:35]  * didrocks sends good vibes to his phone booting on image 128
[10:37] <didrocks> ok trying now
[10:38] <didrocks> image 128 broken
[10:38] <didrocks> so closer and closer to unity-mir
[10:38]  * didrocks now pass the image in rw
[10:38] <didrocks> and revert unity-mir
[10:40]  * sil2100 feels bad because it was him who pressed the release button on unity-mir
[10:40]  * popey registers blamesil2100.com
[10:40]  * didrocks registers blamesil2100.com
[10:40] <sil2100> To my excuse I must add that no integration tests test this behavior!
[10:40] <ogra_> didrocks, if it isnt unity-mir itself it might be libapplication-api ...
[10:40] <popey> highfive!
[10:40] <didrocks> popey: high five!
[10:40] <didrocks> :)
[10:40] <sil2100> hahahaha
[10:40] <popey> spooky!
[10:41] <didrocks> ogra_: yeah, let's try one by one
[10:41] <sil2100> ;)
[10:41] <ogra_> same image ...
[10:41] <sil2100> ogra_: yes, I published unity-mir, platform-api and qtubuntu at the same time
[10:42] <ogra_> right, likely one of these three
[10:45] <didrocks> and unity-mir it is
[10:45] <sil2100> :<
[10:46] <didrocks> ricmm_: once you are back ^
[10:46] <ogra_> yay
[10:46] <didrocks> sil2100: popey: can one of you confirm?
[10:46] <sil2100> didrocks: let me rw my image and test
[10:46] <popey> sure, what deb do I need?
[10:46] <didrocks> sil2100: popey: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/5434608/+files/libunity-mir1_0.2%2B14.04.20140108.1-0ubuntu1_armhf.deb
[10:46] <popey> ta
[10:46] <didrocks> only that one
[10:46] <ogra_> libunity-mir1
[10:46]  * didrocks reflash latest image and revert unity-mir
[10:49]  * sil2100 reboots and tests
[10:50] <popey> didrocks: confirmed #128 fixed with libunity-mir reverted
[10:50] <didrocks> ok, I wonder if we shouldn't just revert it
[10:50] <didrocks> with a manual upload
[10:50] <popey> how big is the diff?
[10:51] <sil2100> didrocks: Gerry mentioned that without unity-mir, the experience will be a bit broken for tablet users - if platform-api and qtubuntu remain
[10:51] <sil2100> IIRC
[10:51] <didrocks> sil2100: well, how was it in the latest promoted image?
[10:51] <didrocks> sil2100: already broken or not?
[10:51] <didrocks> popey: the only relevant diff is: http://bazaar.launchpad.net/~mir-team/unity-mir/trunk/revision/164
[10:51] <didrocks> so quite massive
[10:52] <sil2100> didrocks: in the promoted image there was no platform-api and qtubuntu - greyback mentioned that it's best to have all 3 or none
[10:52] <sil2100> didrocks: we could check if reverting only unity-mir causes a big deal on the tablet or not
[10:52] <didrocks> sil2100: so, we should revert the 3?
[10:53] <didrocks> sil2100: can you check that?
[10:53] <didrocks> and compare to latest promoted image?
[10:53] <sil2100> didrocks: ok, confirming - reverting unity-mir fixed the issue
[10:53] <didrocks> on the tablet
[10:53] <didrocks> great
[10:53] <sil2100> didrocks: hm, don't have a tablet sadly! We will have to find someone with one
[10:53] <sil2100> Last time I pestered balloons
[10:54] <didrocks> ogra_: can you try that one on latest image? ^
[10:54]  * didrocks sends emails and try reverting on latest image
[10:54] <didrocks> (mako)
[10:54] <sil2100> ogra_: could you downgrade only unity-mir on a tablet and see if it's breaking badly sidestage or anything else?
[10:55] <didrocks> (compared to latest known experience)
[10:55] <sil2100> It would be best to have greyback around :|
[10:56] <didrocks> yeah
[10:56] <didrocks> or we can be safer
[10:56] <didrocks> revert the 3
[10:56] <didrocks> and be done
[10:56] <asac> i am pretty sure the sessions in CT are aligned around full hours
[10:57] <asac> so in a few minutes ricmm_ and greyback might be able to talk to us :)
[10:57] <asac> (or not)
[10:57] <ogra_> yeah
[10:57] <ogra_> sil2100, i have no tablet with working sidestage
[10:57] <sil2100> 13:15 < greyback> sil2100: correct. unity-mir would need to released too, as without the experience is broken
[10:57] <sil2100> This is what he told me some time ago
[10:58] <didrocks> same here
[10:58] <ogra_> well, my N10 is dead since a while, there definitely was no working sidestage with 121 which was the last image on it
[10:58] <didrocks> I thought ogra_ had a N10
[10:58] <didrocks> argh
[10:58]  * ogra_ charges 
[10:58] <didrocks> ok, let's revert all 3 of them
[10:58] <didrocks> let me try that on latest image first
[10:58] <sil2100> I remember balloons mentioned that sidestage with the latest packages worked good
[11:01] <didrocks> popey: updating the bug? (if not done already) with right components and so on :)
[11:01] <popey> i haven't
[11:01] <popey> will do.
[11:01] <didrocks> ok, confirming latest image + unity-mir revert = OK
[11:02] <popey> am confirming that too
[11:02] <popey> i think i broke launchpad
[11:03] <popey> reassigned bug 1269414
[11:04] <ogra_> my N10 is downloading
[11:05] <didrocks> ogra_: don't bother, we are going to revert the 3 I guess
[11:05] <didrocks> better to be on the safe side
[11:05] <ev> didrocks: I empathise with the desire to have all hands on deck with manual testing, but do you absolutely need psivaa for this? I have him as vanguard trying to clean up the fallout from the DC power maintenance last night.
[11:05] <didrocks> ev: I guess now that we identified the component, psivaa can go back to vanguard task
[11:06] <didrocks> ev: however, as mentionned today in the meeting, training him to retrace dialer_app would be a nice asset for the future
[11:07] <popey> didrocks: confirmed #131 with reverted libunity-mir 'fixes' the issue
[11:07] <ev> didrocks: cheers!
[11:07] <didrocks> popey: thanks!
[11:07]  * didrocks runs some tests and then, go for reverting
[11:09] <davmor2> didrocks: isn't there menat to be a permanent solution in place for persistence in apps so that other apps could utilise it?
[11:10] <didrocks> davmor2: nothing yet, but it's planned AFAIK
[11:10] <didrocks> davmor2: we have bigger fish first ;)
[11:10] <davmor2> didrocks: okay I was wondering if it had landed and the app needed updating to use it :)  but no still needs the cowboy in place :(
[11:11] <ogra_> davmor2, there is a whitelist in the platform api
[11:12] <davmor2> it wasn't anything daft like the whitelist got blanked then was it?
[11:12] <ogra_> probably
[11:12] <ogra_> or the function it uses got non-functional
[11:13] <didrocks> ok, reverting now
[11:13] <didrocks> let's kick an image once published
[11:13] <didrocks> sil2100: confirmed about webbrowser-app: one run, all passed
[11:14] <ogra_> ah, finally the download is done here :P
[11:15]  * ogra_ watches 131 install on his N10
[11:15] <sil2100> ;)
[11:19] <ogra_> the sidestage in 131 breaks input for me on N10
[11:20] <ogra_> oh, no, it just needs really weird gestures
[11:20] <ogra_> hmm, but doesnt accept taps in the app running in sidestage
[11:21] <didrocks> unity-mir ready
[11:21] <ogra_> so even if the revert breaks it, it seems to have never actually worked
[11:21] <didrocks> qtubuntu ready
[11:21] <didrocks> ogra_: well, I prefer to stay on the safe side and revert the whole set in lack of more expertise
[11:21] <ogra_> aha
[11:22] <ricmm_> dont revert
[11:22] <ogra_> native apps work, webapps dont
[11:22] <ricmm_> I'll fix, reverting is not always the answer :)
[11:22] <sil2100> ricmm_: too late
[11:22] <sil2100> ricmm_: it seems didrocks is already on the roll!
[11:22] <didrocks> ricmm_: well, you aren't around, are you now?
[11:22] <ricmm_> I was having lunch
[11:22] <didrocks> I didn't dput, the whole thing is ready
[11:22] <ricmm_> sure, this is me talking
[11:22] <ricmm_> dont dput
[11:22] <sil2100> Phew
[11:23] <didrocks> ricmm_: ok, so you are looking right now? Can we have an ETA starting from where we will dput the revert? Remember that test results are coming 5h later, we don't want to loose another day
[11:24] <didrocks> ricmm_: also, there are 2 additional commits in lp:unity-mir, are we sure they are safe?
[11:24] <didrocks> seems they are
[11:25] <ricmm_> they are
[11:25] <ricmm_> give me an hour
[11:25] <ricmm_> is that fine with you?
[11:25] <didrocks> ricmm_: sounds good :)
[11:25] <asac> ricmm_: how much time? 1h is fine i think, but didrocks to say
[11:25] <asac> hehe
[11:26] <didrocks> we all agree it's the right timeframe :)
[11:26] <ogra_> heh, the sidestage is really weird
[11:26]  * ogra_ fails to find an app that actually doesnt start in sidestage mode on N10
[11:27] <ogra_> even the filemanager does ... even though it starts in a fullscreen size it jumps into the sidestage
[11:27] <ricmm_> ogra_: who said sidestage was complete?
[11:27] <ricmm_> been waiting on a ted release for a month
[11:28] <ogra_> ricmm_, i didnt even know it was supposed to work
[11:28] <ogra_> my N10 was on trusty ... not -proposed
[11:28] <ricmm_> if you build trunk upstart-app-launch it will work with all apps the right way
[11:28] <ogra_> seeing it for the first time
[11:28] <ricmm_> oh
[11:28] <ogra_> (in a semi working state)
[11:31] <greyback> didrocks: hey, how am I blocking? What's wrong?
[11:31] <didrocks> greyback: ricmm is on it, it's unity-mir, but his commit ;)
[11:32] <greyback> didrocks: ah ok, let me know if I'm needed
[11:32] <didrocks> greyback: ask directly to ricmm, but it's app lifecycle, I think he knows the ins and out of it :)
[11:32] <davmor2> didrocks, asac, ogra_, popey: so that knock at the door will be my N4 \o/
[11:32] <ogra_> yay
[11:32] <didrocks> davmor2: heh, congrats!
[11:33] <greyback> didrocks: ack
[11:33]  * popey hides in the bushes outside davmor2's house
[11:33] <ricmm_> greyback: will need a review in a bit I guess
[11:33] <didrocks> davmor2: but keep your maguro for dogfooding the next image
[11:33] <greyback> ricmm_: am here
[11:33] <didrocks> popey: you as well, be ready ^
[11:33] <didrocks> popey: and don't find new bugs!
[11:33] <popey> \o/
[11:33] <didrocks> ;)
[11:33] <popey> haha
[11:33] <popey> muhahaha
[11:33] <davmor2> oh it came with a case to that was unexpected
[11:33] <didrocks> popey: that's… annoying :p
[11:33]  * didrocks hugs popey, thanks for giving so much testing!
[11:33] <popey> davmor2: added a manual test to the spreadsheet, leave music playing for a minute or so
[11:33] <davmor2> didrocks: but finding bugs is what I do :P
[11:33] <popey> np
[11:33] <asac> davmor2: very good
[11:34] <asac> finally you can see and test the real thing
[11:34] <ogra_> lol
[11:34] <popey> wise having a cover for the frictionless n4
[11:34] <ogra_> ++
[11:34] <ogra_> dont put it on angled surfaces
[11:34] <popey> surprised LG never tested "putting the phone down on something other than a perfectly flat surface"
[11:34] <ogra_> 1° is enough to make it slide down and fall
[11:35] <ogra_> mine sometimes only falls after 1-2h
[11:35]  * ogra_ has cushions on the ground everywhere now :P
[11:35] <popey> yeah, slowly creeping to the edge of the table when you're not looking
[11:35] <ogra_> yep
[11:35]  * popey imagines ogra_ lives in a hareem
[11:36] <ogra_> lol, dont tell susie
[11:36] <popey> ☻
[11:36] <sil2100> I especially bought a sturdy case for my N4
[11:36] <sil2100> After the story of popey's N4 which got devastated by a fall on the ground
[11:36] <popey> heh
[11:37] <ogra_> sil2100, yeah, better than me ... i joked about him ... just to have a broken phone a week later
[11:37] <ogra_> always pays back :)
[11:38] <sil2100> ;)
[11:43] <ogra_> popey, did you notice that the battery time got works on N4 or is my battery just wearing out ?
[11:43] <ogra_> s/works/worse/
[11:44] <popey> mine is almost always plugged in
[11:44] <popey> so i don't notice
[11:44] <ogra_> mine used to survive 1.5 days .... nowadays its less than a day
[11:44] <ogra_> i usually find it dead in the morning
[11:56] <sil2100> cihelp: dammit, intel hanged up again
[11:57] <sil2100> psivaa: could you take a look at the intel machine on cu2d? It's hanged and blocking the whole line again
[11:57] <psivaa> sil2100: which machine?
[11:57] <psivaa> sil2100: ack
[11:57] <sil2100> psivaa: qa-intel-4000
[12:03] <psivaa> sil2100: why do you think it hung? http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/1197/console is progressing
[12:04] <psivaa> and succeeded
[12:04] <tsdgeos> guy
[12:05] <tsdgeos> can anyone have a look at the autolander?
[12:05] <tsdgeos> http://s-jenkins.ubuntu-ci:8080/job/generic-land/
[12:05] <tsdgeos> seems there's lots of jobs waiting
[12:05] <sil2100> psivaa: uuuh, wait, this looks different from what I saw - one moment
[12:06] <sil2100> psivaa: aaaah! Ok, sorry, my bad then! It seems it's ok now
[12:06] <psivaa> sil2100: no problem. may have been a test glitch
[12:06] <psivaa> tsdgeos: looking at your issue btw now
[12:06] <tsdgeos> psivaa: great, thanks!
[12:09] <sil2100> popey: does sms messaging work for you on the latest image?
[12:10] <popey> sil2100: i sent and received sms on #131
[12:10] <popey> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Ai33BkOcORLLdE4xLTFtSE80ZkpITXZ3aV85cWtPX2c&usp=drive_web#gid=0
[12:10] <sil2100> hm, then there's something b0rken here on my device, probably need a re-flash
[12:10] <popey> that spreadhseet is what davmor2 and I use to track manual dogfood/testing we do
[12:10] <popey> if it's green, it worked
[12:10] <popey> unusual, I know.
[12:10]  * sil2100 bookmarks
[12:11] <davmor2> sil2100: if it's red run we will be blaming you ;)
[12:11] <sil2100> ;)
[12:12] <Saviq> is ps-generic-precise-amd64 offline? generic-land is stuck for a while now
[12:12] <davmor2> popey: when you flash on the mako do you not get the robot?  or is that just on mine (is it special already :) )
[12:12] <Saviq> psivaa, ↑↑
[12:13] <popey> davmor2: i dont watch it tbh
[12:13] <psivaa> Saviq: that's what im looking at now from tsdgeos req
[12:14] <davmor2> popey: I normally keep an eye on it till the robot then I know there are no problems unless it is image related :)
[12:14] <davmor2> ogra_: ^
[12:14] <Mirv> wondering first why builders seem busy, then noticing KDE 4.12.1
[12:14] <Saviq> psivaa, ah thanks
[12:15] <popey> davmor2: i think i see the robot briefly, but it spends way more time showing me the google logo
[12:15] <ogra_> davmor2, you should get the robot with the progressbar and violet bg
[12:15] <davmor2> ogra_: I got a blank screen
[12:15] <ogra_> davmor2, make sure the device is not on 4.4 before installing though
[12:15] <psivaa> tsdgeos: Saviq: that's online now. please check
[12:15] <ogra_> else you get radio trouble
[12:16] <tsdgeos> psivaa: awesome, thanks!
[12:16] <davmor2> ogra_: man now I'm told
[12:17] <Saviq> psivaa, yup, it's running, thanks
[12:17] <psivaa> Saviq: tsdgeos: yw
[12:17] <davmor2> ogra_: 4.4 or 4.4.2 or does it not matter?
[12:18] <ogra_> with 4.4 (and above) a radio firmware is used that is not backwards compatible
[12:18] <ogra_> i.e. does not work with our 4.2 stack
[12:22] <davmor2> ogra_: ah not 4.4 misread it as 4.4  so I'm looking at 4.2.2 or 4.3 so I'll grab 4.2.2 as that should work fine on the 4.2 stack that we have right :)
[12:22] <ogra_> yep
[12:23] <davmor2> ogra_: thanks for the heads up :)
[12:23] <ogra_> :)
[12:29] <didrocks> ricmm_: any news?
[12:30] <ricmm_> didrocks: being reviewed and tested
[12:31] <didrocks> ricmm_: you ROCK!
[12:31] <davmor2> ogra_: now I see the recovery mode that I didn't before and so will possibly see the robot too yay \o/
[12:31] <ricmm_> didrocks: test with pkgs from https://code.launchpad.net/~ricmm/unity-mir/respect-lifecycle-stages/+merge/201913
[12:31] <ricmm_> or whoever was testing
[12:31] <ogra_> cool
[12:31] <davmor2> yeap there he is I can ignore it now :)
[12:32] <sil2100> \o/
[12:32] <davmor2> ogra_: so it looks like the 4.4 stack might have updated gfx too then maybe being as the it didn't show before
[12:32] <sil2100> ricmm_: testing that then in the meantime of the review
[12:33] <ogra_> davmor2, yep, can well be
[12:33] <ricmm_> thanks
[12:33] <ogra_> davmor2, we should see the first 4.4 images some time next week ...
[12:33] <ogra_> then this wont be an issue anymore
[12:33] <davmor2> ogra_: Yay
[12:34] <ogra_> didrocks, suggest him for the next awards ;)
[12:34] <didrocks> ogra_: nobody ask me to suggest anyone. I'm not a manager :)
[12:35] <ogra_> tell your mgr. then :)
[12:39]  * sil2100 tests the new package
[12:40] <sil2100> So far so good
[12:40] <sil2100> didrocks, ricmm_: I confirm the branch fixes the issue with the screen fading and music stopping
[12:40] <sil2100> So a +1 from me
[12:41] <greyback> ricmm_: tested
[12:41] <greyback> ricmm_: approved
[12:41] <greyback> sil2100: +1 from me also, I've top approved it
[12:41] <ogra_> yep, works fine here too
[12:43] <ricmm_> didrocks: overshot by like 15 min
[12:43] <ricmm_> darn
[12:43] <didrocks> ricmm_: that's fine :)
[12:43] <didrocks> thanks alot!
[12:43] <ogra_> haha
[12:43] <didrocks> so, can you get it merged?
[12:44] <didrocks> and sil2100, can you release it?
[12:46] <davmor2> sil2100: what about if you open another app so the music player isn't in the forground
[12:46] <davmor2> foreground even
[12:47] <davmor2> sil2100: I'm assuming it will work but it is worth checking before it gets pushed :)
[12:47] <ogra_> i think it is the same code path for both
[12:48] <davmor2> ogra_: as I say I assume it will work
[12:48] <davmor2> ogra_: however Assumption is the mother of all F*** ups
[12:48] <ogra_> :)
[12:50] <davmor2> oh N4 I get screenshots  again Yay, it's the little things :)
[13:00] <popey> davmor2: that was the original bug report
[13:01] <sil2100> davmor2: it works ;)
[13:04] <Mirv> hmm, I wonder if something is wrong in PPA:s or PPA dependency setups. getting uninstallable packages for no reason (can be installed with same config locally)
[13:04] <Mirv> eliminating more parameters now
[13:05] <ogra_> argh !
[13:05] <sil2100> Mirv: just like I had before, right?
[13:05] <ogra_> my last update made the linker bug re-apper
[13:05] <ogra_> sigh
[13:05]  * ogra_ cant exec anything anymore 
[13:06] <Mirv> sil2100: yeah, actually. then I thought that maybe I did some package copying and deleting that messed up qt5-beta-proper, but now I'm getting similar elsewhere.
[13:06] <Mirv> sil2100: so no I couldn't build in another PPA which had set up to build against qt5-beta2. I'll now try without the dependency.
[13:07] <didrocks> sil2100: is is merged, what's the status?
[13:08] <ogra_> grrr and i cant sudo to set the ld.so link
[13:09] <sil2100> didrocks: it's merged
[13:09] <sil2100> psivaa: ok, it seems we have some problems with nvidia now
[13:09] <sil2100> didrocks: cu2d is having problems, nvidia otto machine is in some strange state and again blocking everything
[13:09] <sil2100> psivaa: you think killing the job will do?
[13:10] <sil2100> No time to loose, anyway it's taking AGES already
[13:10]  * sil2100 kills the job
[13:10]  * ogra_ sighs and reboots to initrd to hack around it 
[13:10] <sil2100> I thought we're over with the times when one had to look at otto machines every 15 minutes to make sure nothing is broken
[13:14] <sil2100> didrocks: should I stop all the cu2d jobs and force only unity-mir to be built and released?
[13:15] <didrocks> sil2100: +1
[13:19] <sil2100> didrocks: in the meantime I also looked into messaging-app, aaaand...
[13:21] <sil2100> didrocks: messaging-app itself seems ok, but I noticed a problem (from my experiments it might not be related to daily-build)
[13:21] <sil2100> didrocks: when installing messaging-app-autopilot, it seems that some of its dependencies break message sending and receiving
[13:22] <didrocks> sil2100: it was already the case before?
[13:22] <sil2100> didrocks: so, once I install messaging-app-autopilot, I cannot receive or send any messages - regardless of what version of messaging-app I have
[13:22] <sil2100> didrocks: not sure, I only tested that simply downgrading messaging-app and messaging-app-autopilot did not help, only a complete removal of messaging-app-autopilot and its dependencies (some ofono packages were there) helped
[13:23] <sil2100> I'll try on stock messaging-app
[13:23] <didrocks> sil2100: ah, it's the mock ofono
[13:23] <didrocks> right?
[13:23] <didrocks> that's pitti's work
[13:23] <didrocks> and yeah, on purpose :)
[13:23] <ogra_> grmbl
[13:23] <didrocks> sil2100: it's ofono-phonesim, right?
[13:24] <didrocks> try installing it/removing it (but I don't think it's an issue ;))
[13:25] <sil2100> Ok ;)
[13:25] <sil2100> A bit strange though, didn't expect my phone to be entirely useless after installing messaging-app-autopilot
[13:25] <didrocks> sil2100: try removing it
[13:25] <didrocks> and keep us posted
[13:33] <davmor2> sil2100: as I said I assumed it would but it is always worth checking :)
[13:34] <davmor2> didrocks: I think I found an issue with accounts on the n4.  I setup u1 account to grab some click apps, I then went to add some more accounts and now accounts isn't opening everything else in settings opens fine just accounts that isn't, digging into some logs now
[13:35] <ogra_> davmor2, not opening or only showing you the U1 account greyed out
[13:35] <davmor2> ogra no opening
[13:35] <ogra_> ah, k
[13:36] <davmor2> ogra_: I click on accounts and nothing.  If I click on sounds it opens.
[13:36] <ogra_> weird
[13:37] <ogra_> definitely works on 121 for me
[13:38] <davmor2> ogra_: indeed it opened fine first time to add the u1 account for me on 131
[13:38] <ogra_> bah
[13:38] <ogra_> my phone hangs hard
[13:38] <ogra_> with half way swiped lock screen
[13:38] <ogra_> grmbl
[13:39] <ogra_> havent had that in months
[13:39] <ogra_> and no adb either ... seems to actually hang hard
[13:39]  * ogra_ reboots
[13:39] <davmor2> ogra_: n4 or maguro if it is the latter it happens for me most days
[13:39] <ogra_> n4
[13:39] <ogra_> i'm used to maguro being crap :)
[13:40] <ogra_> but my N4 is my private dogfood phone ... usually always on stable images
[13:40] <ogra_> (after asac's change i will only have a single device for work *sniff*)
[13:41] <ogra_> and the emulator makes my laptop hover on full fan speed
[13:41] <davmor2> yeah maguro was my phone now n4 will be instead :D
[13:45] <psivaa> sil2100: sorry, which nvidia machine?
[13:48] <sil2100> psivaa: autopilot-nvidia - I cancelled the job and now currently there's nothing working on it
[13:49] <psivaa> sil2100: ok, i am able to connect to it.
[13:49] <sil2100> psivaa: I guess some test just caused autopilot to go crazy, you can see the logs here:
[13:50] <sil2100> http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=autopilot-nvidia/1197/console
[13:50] <sil2100> psivaa: it seems compiz died...
[13:50] <sil2100> psivaa: *** Error in `compiz': malloc(): memory corruption: 0x0b3045c8 *** <- doesn't look good
[13:51] <psivaa> sil2100: righ, let me take a look at it in KVM
[13:51] <psivaa> cjohnston: do you want to do this ^? or ok letting me do it
[13:51] <psivaa> ?
[13:51] <cjohnston> psivaa: if you have the history and want to, go for it
[13:52] <psivaa> cjohnston: nothing much of a history, except sil2100's messages above
[13:53] <davmor2> ogra_: think I found it TaskController::stop appId='online-accounts-ui' TaskController::stopApplication appId='online-accounts-ui' FAILED FAILED to ask Upstart to stop application 'online-accounts-ui' that would mean it is still up but not visible I guess right?  So just the system getting it's knickers in a twist right?
[13:54] <ogra_> yeah
[13:58] <popey> davmor2: just reproduced that in system settings, unity blew up
[13:59] <popey> added ubuntu one, backed out, added evernote, backed out, now settings is just white for me
[13:59] <ogra_> popey, try removing evernote ...
[13:59] <ogra_> and see if it still happens then
[13:59] <popey> the package or the account?
[14:00] <davmor2> ogra_: I've been converted vim rocks, /online-accounts then n to find the faulty lines is blisteringly fast :)
[14:00] <ogra_> ++
[14:00] <popey> hmm
[14:00] <ogra_> vim is love
[14:00] <popey> killed settings and I can get back in now
[14:01] <popey> i have an online-accounts whoppsie
[14:01] <davmor2> popey: sounds like a different issue to mine
[14:01] <popey> -typo
[14:02]  * popey files a bug
[14:07] <sil2100> Mirv: https://code.launchpad.net/~sil2100/appmenu-qt/disable_qt5/+merge/201931 <- please :)
[14:07]  * davmor2 files a bug too
[14:07] <sil2100> With cherries on top
[14:08] <sil2100> didrocks: ok, so platform stack is ready... the check job failed, but it seems nvidia is down (or being investigated) - it passed successfully on intel
[14:08] <sil2100> didrocks: should I do a test-everything on my phone, or should we just push it out ASAP?
[14:10] <didrocks> sil2100: +1 ;)
[14:11] <didrocks> if (not more)
[14:11] <sil2100> So, testing you mean?
[14:11] <ogra_> syntax error: that was an or question ... cant answer with a boolean
[14:11] <didrocks> yep ;)
[14:11] <sil2100> ;D
[14:12] <didrocks> ogra_: in python and javascript, implicit convertion works
[14:12] <ogra_> heh
[14:12] <sil2100> Oh noes
[14:14] <psivaa> sil2100: I've relaunched the nvidia job after reboot. the jobs appear progressing but has not reached the point where it failed earlier.
[14:14] <psivaa> will soo how it goes
[14:15] <psivaa> sil2100: and that has succeeded
[14:15] <psivaa> not sure if we are letting a compiz issue slip through
[14:16] <sil2100> psivaa: thanks for taking care of that, knowing our luck today it might have been a single 'issue' that's probably hard to reproduce
[14:16] <sil2100> Not sure if we have even enough info to fill in a bug?
[14:17] <psivaa> sil2100: yea.
[14:48] <didrocks> sil2100: working? can we publish? ;)
[14:49] <ogra_> didrocks, is that 131 ?
[14:49] <ogra_> dashboard doesnt look so good for it
[14:50] <didrocks> ogra_: the image isn't even kicked
[14:50] <sil2100> didrocks: working, but there's sooo many AP tests to run that it'll still take a while ;)
[14:50] <ogra_> oh
[14:50] <ogra_> k
[14:50] <didrocks> ogra_: as discussed this morning, ignore the webbrowser-app issues, it's flakyness
[14:50] <didrocks> (confirmed here)
[14:50] <ogra_> k
[14:50] <sil2100> didrocks: so far unity8, uitk, gallery-app are fine - you want to publish now?
[14:52] <didrocks> sil2100: hum, no, only unity-mir
[14:52] <didrocks> sil2100: the rest will be later on :)
[14:52] <didrocks> but let's do 2 batches, the fix
[14:52] <didrocks> image built
[14:52] <didrocks> image promotion
[14:52] <didrocks> and then, we'll look at what was planned for release
[14:53] <sil2100> didrocks: ah, I mean, do you want me to publish unity-mir now that only partially all AP-suites I ran ;)
[14:53] <sil2100> didrocks: since I assumed that I should run all AP tests
[14:53] <sil2100> didrocks: (while that takes a loong time)
[14:53] <didrocks> sil2100: yeah, better to run them all
[14:53] <didrocks> sorry, I thought you talked about components to release ;)
[14:54] <sil2100> didrocks: no no, just which test suites are done, since unity8 AP tests took a long time to complete
[14:54] <sil2100> Now it's going smoothly forward
[14:54] <didrocks> great
[15:21] <davmor2> didrocks: right how we doing for image 132?
[15:22] <didrocks> davmor2: well, sil2100 is running all AP tests before we publish the fix
[15:22] <ogra_> davmor2, waiting for sil2100 to finish
[15:22] <ogra_> then publish the fix .... wait til its through the infrastructure
[15:23] <ogra_> ... build an image ... wait till dashboard picks up testing  ....
[15:23] <davmor2> yay I got time to do other stuff then woohoo!
[15:23] <ogra_> publish tomorrow morning (most likely)
[15:23] <sil2100> Almost finished!
[15:24] <davmor2> man the n4 is so much faster
[15:24] <sil2100> One last click test doing
[15:24] <ogra_> davmor2, its actually usable :)
[15:25] <didrocks> davmor2: basically, I would say a couple of hour before the image is built
[15:25] <davmor2>  /me hears the sound of a distant explosion, Karma teaching a sil2100 a valuable lesson, never say nearly finished, It's like going into a cellar in a horror film :)
[15:26] <sil2100> ;_;
[15:27] <sil2100> didrocks: in the meantime, an ACK please! http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-mir_0.2+14.04.20140116-0ubuntu1.diff
[15:28] <cjwatson> sil2100: haven't reviewed it all, but Multi-Arch: same is definitely wrong there
[15:28] <timp> davmor2: imagine that he said "almost finished, brb!"
[15:29] <cjwatson> that's either foreign if you provide architecture-independent interfaces from that package (I think you do) or just leave it out otherwise
[15:29] <timp> davmor2: it could be even worse, but let's not go there ;) http://scream.wikia.com/wiki/The_Rules
[15:29] <sil2100> cjwatson: true!
[15:29] <didrocks> yeah, not a multiarch dir
[15:29] <cjwatson> also an unnecessary dot-only line in the package description
[15:29] <cjwatson> nitpicks 'r' us
[15:29] <ogra_> heh
[15:29] <sil2100> didrocks: should I fix that, rebuild and publish?
[15:30] <didrocks> sil2100: I don't think we want to wait yet 2 hours for this. I would say prepare a MP with the fixes and we'll approve
[15:30] <davmor2> timp: that's the end of the world and zombie apocalypse usually right, It'll finish when it's good and ready I find is a safe bet :)
[15:30] <sil2100> ;)
[15:30] <didrocks> cjwatson: if we propose that version, there is no side-effect (due to the multiarch mismatch), right?
[15:30] <didrocks> publish*
[15:30] <cjwatson> didrocks: I wouldn't like to guess
[15:31] <cjwatson> didrocks: probably not serious if there are no dependencies on that package anywhere else, but it should still be fixed ASAP as it'll be confusing for anyone who does run into it while test-building
[15:31] <didrocks> cjwatson: yeah, it's a new one and not installed yet, so hence the MP (and we have another release of unity-mir with a whole Mir stack coming)
[15:32]  * sil2100 learned a lesson to first review the packaging diff and only then do the testing
[15:33] <sil2100> didrocks, cjwatson: https://code.launchpad.net/~sil2100/unity-mir/fix_multi-arch_tests/+merge/201946
[15:33] <sil2100> Should I publish unity-mir?
[15:34] <didrocks> sil2100: if all tests pass, please do
[15:34] <didrocks> sil2100: can you fix the extra dot that cjwatson pointed out?
[15:35] <sil2100> didrocks: I looked at that, but it's a bit consistent with their description style
[15:35] <sil2100> didrocks: but I can change that
[15:36] <didrocks> sil2100: tell us when you fixed them :)
[15:36] <didrocks> but publish first!
[15:36] <sil2100> didrocks: published! I'll remove the dot, but the description anyway would need to be tweaked
[15:38] <sil2100> didrocks: and pushed a modification
[15:39] <sil2100> didrocks: I'll release messaging-app once the image with unity-mir is kicked
[15:39] <didrocks> sil2100: I guess get everything prepared
[15:39] <didrocks> sil2100: disable build all
[15:40] <didrocks> sil2100: and let's wait for test results before pushing more
[15:40] <sil2100> didrocks: how can I disable build_all? SHould I go to build_all-head and press 'Disable project'?
[15:41] <didrocks> sil2100: yeah
[15:50] <sil2100> didrocks: in proposed \o/
[15:50] <didrocks> sil2100: in the description, I would add "test"
[15:50] <didrocks> (in the short one)
[15:51] <didrocks> sil2100: otherwise, good news, let's hope it builds on the missing archs quickly and get migrated ASAP
[15:52] <sil2100> didrocks: pushed, tell me if it's better now
[15:53] <didrocks> sil2100: hum, the push is not detected yet
[15:53] <cjwatson> didrocks: missing archs> not relevant, unity-mir in trusty only has binaries for amd64 armhf i386
[15:53] <cjwatson> I assume the rest will dep-wait or something but proposed-migration won't wait for them
[15:55] <didrocks> cjwatson: ah, it even doesn't wait for the run to complete and say "dep-wait"?
[15:55] <cjwatson> no, proposed-migration doesn't look at LP build status at all
[15:55] <didrocks> ah ok, just basing on the destination arch build status
[15:56] <cjwatson> it only cares what binaries are in the two suites in the archive that it's comparing
[15:57] <didrocks> ok, making sense
[15:57] <didrocks> thanks for the precision
[15:57] <cjwatson> with the exception of the autopkgtest stuff, the core of proposed-migration can run offline
[15:57] <sil2100> didrocks: ... "has uncommitted changes", gosh
[15:57] <cjwatson> not that we bother isolating it or anything, but as a rule of thumb :)
[15:58] <sil2100> didrocks: now it should be good
[16:03]  * sil2100 is slowly preparing for take off to practice
[16:03] <sil2100> I'll be back around 20 though!
[16:06] <didrocks> sil2100: approved, thanks :)
[16:13] <mandel> vila, can you give me a hand in a blocking issue with CI failing?
[16:19] <cjohnston> mandel: use the vanguard in the topic please
[16:20] <vila> mandel: topic line mentioins doanac.. yeah, what cjohnston said ;)
[16:20] <mandel> he, thx
[16:20] <doanac> i'm here
[16:20] <mandel> doanac, I've got a failing test in CI that makes no sense and is blocking a branch from landing and I'd like some feedback/help
[16:21] <doanac> mandel: you have a link?
[16:21] <mandel> doanac, the test uses http://qt-project.org/doc/qt-5.0/qtcore/qeventloop.html#exec to avoid the use of timeouts when waiting for a signal, for some reason the tests are perfectly fine on the developers machines and are failing on CI
[16:21] <mandel> doanac, one sec and I'll get the failure link
[16:22] <mandel> doanac, https://jenkins.qa.ubuntu.com/job/ubuntu-download-manager-trusty-amd64-ci/166/console
[16:23] <mandel> doanac, I'm really puzzled and I was wondering if you guys have seen something similar happening or if there is a env var we could set to skip those tests in CI but force them in the reviews
[16:26] <doanac> fginther: you know if anything like that exists? ^
[16:27] <mandel> doanac, we could set an env variable.. we used to have some tests that failed in jenkins in u1 back in the day
[16:27] <mandel> doanac, it is really puzzling (the failure)
[16:27] <doanac> mandel: what seems concerning is that it passes most of the time. seems like the test could be flaky?
[16:29] <cjwatson> 1/wg 112
[16:29] <cjwatson> sigh
[16:29] <mandel> doanac, is a new test and it passes all the time my machine and others but fails on Jenkins, I have increased the timeout added a QEventLoop to block until the signal is executed etc.. and nothing
[16:29] <mandel> doanac, the test is very reliable on the desktop
[16:33] <didrocks> unity-mir published
[16:33] <didrocks> kicking an image build
[16:33] <ogra_> \o/
[16:34] <fginther> mandel, when you test locally, are you doing a package build (i.e. pbuilder or sbuild)?
[16:35] <mandel> fginther, no, there I'm just doing a qmake && make && make check
[16:35] <mandel> fginther, I can try with pbuilder if you want but that should not be an issue, should it?
[16:36] <fginther> mandel, it shouldn't, but it might be worth a data point
[16:36] <mandel> fginther, I'll give it a go, more info never hurts
[16:37] <fginther> mandel, I'll try one locally as well
[16:37] <mandel> fginther, there are no build instructions, you can do a bzr pull; mkdir build; cd build; qmake ../download-manager.pro and then make && make check
[16:37] <mandel> fginther, I should add a bug about that missing :-/
[16:37] <fginther> thx
[16:47] <fginther> mandel, is that test trying to download "http://www.python.org/ftp/python/3.3.3/Python-3.3.3.tar.xz" ?
[16:47] <mandel> fginther, no, it just uses that url as example, no requests are done
[16:47] <mandel> fginther, is just testing the callback execution
[16:47] <mandel> very very unit test
[16:48] <fginther> mandel, does it use any sockets?
[16:48] <mandel> fginther, uses dbus
[16:49] <fginther> mandel, and your tests start a dbus process?
[16:49] <mandel> fginther, you are scaring me a little because I'm writing integration tests that will do request to localhost after the test case starts a simple http server (python) would that be an issue?
[16:50] <mandel> fginther, this tests precisely do not but in the future they will
[16:50] <fginther> I asked about the URL, because firewall rules prevent access to everything not on a whitelist
[16:50] <fginther> so python.org would be blocked
[16:51] <mandel> fginther, then it is not an issue, I do not perform request outside, is just and example of an url
[16:51] <fginther> launchpad is not blocked if you need a URL source
[16:51] <fginther> got it
[16:51] <cjwatson> relying on any external site is a bad idea for reliability though
[16:51] <cjwatson> even launchpad
[16:52] <mandel> cjwatson, is not relying, could have been http://example.com it does rely on the fact that it is a well formed url
[16:52] <fginther> mandel, do any of the working tests use dbus?
[16:53] <mandel> fginther, no, they do not
[16:53] <fginther> mandel, what about these messages: CRITICAL - Could not register service QDBusError("org.freedesktop.DBus.Error.NotSupported", "Unable to autolaunch a dbus-daemon without a $DISPLAY for X11")
[16:53] <cjwatson> mandel: right, I was replying to fginther
[16:53] <fginther> cjwatson, in that case I agree :)
[16:53] <cjwatson> (I actually think that any example URLs *should* be in example.com or similar - there's an RFC for this)
[16:54] <mandel> fginther, yes, that does not look good at all :-/
[16:54] <mandel> fginther, and is going to be a PITA because I have lots of integration tests in future branches that use dbus to test the entire "stack"
[16:54] <mandel> :-/
[16:54] <fginther> mandel, if you need x or dbus for testing, the test need to start these services themselves (i.e. using xvfb or something)
[16:55] <cjwatson> RFC2606
[16:55] <mandel> fginther, well, In the integration tests I start the dbus process directly, therefore I don't think it should be an issue, nevertheless this tests are nto affected by that
[16:55] <mandel> fginther, this guys are just waiting for a qt signal to be emitted and for some reason they are failing
[16:57] <fginther> mandel, but it sounds like the missing $DISPLAY could be a problem
[16:57] <fginther> ?
[16:58] <mandel> fginther, I'll do something, I'll change the test to have the daemon started even if it is not needed and that way we can see if it works :)
[16:58] <ogra_> didrocks, oh, landing report before meeting ??
[16:58] <mandel> fginther, worst case scenario we learn is not an issue
[16:59] <didrocks> ogra_: well, there is no surprise in what we'll announce (and the meeting will be short, no robert, no ken…)
[16:59] <fginther> yep
[16:59] <ogra_> ah, k
[16:59] <didrocks> ogra_: so, getting ahead a little bit (it was more to update people)
[16:59]  * ogra_ goes upstairs 
[17:01] <didrocks> plars: coming?
[17:01] <plars> didrocks: trying to, browser problem, one sec
[17:01] <didrocks> oki ;)
[17:09] <plars> wow, I think I have it going
[17:10] <plars> cool, I got an image out at the end!
[17:10] <plars> no glance yet, just local for debugging
[17:10] <plars> but all the rabbit stuff worked
[17:11] <plars> now it's processing all the backlog of crap I sent it
[17:11] <plars> heh
[17:11] <plars> which is good, it'll go through multiple times :)
[17:13] <plars> one hitch I hit - I need an extra debian package installed. I'd hope there's some way to specify that in the charm?
[17:13] <plars> I need qemu-utils
[17:16] <didrocks> davmor2: hey
[17:16] <plars> ah
[17:16] <plars> wrong line
[17:17] <didrocks> davmor2: so, image 132 is going to be published in like 30 minutes
[17:17] <davmor2> yeah
[17:17] <didrocks> can you do a dogfooding run on maguro?
[17:17] <didrocks> and please send me an email with +1/-1 ;)
[17:17] <davmor2> didrocks: yeap
[17:17] <didrocks> so that I know how my day will start…
[17:17] <didrocks> that + AP tests ;)
[17:17] <didrocks> thanks davmor2!
[17:17] <davmor2> didrocks: no worries :)
[17:20] <popey> oh, we can come down from DEFCON1 now!
[17:20] <popey> oh, we did
[17:21] <popey> phew
[17:21]  * didrocks can't wait for DEFCONF0 :p
[17:21] <didrocks> ahah
[17:33] <kenvandine> ricmm, are you going to add ual to landing asks?  should i?
[17:33] <kenvandine> ricmm, i'm going to need the new api soon
[18:35] <popey> davmor2: initial dogfooding seems good for me on mako
[18:35] <davmor2> popey: maguro just rebooting
[18:36] <popey> kk
[18:40] <fginther> mandel, I can reproduce the test failures by running "make check" from an ssh session (which removes all of the DISPLAY and DBUS related env)
[18:49] <davmor2> popey: how many music tracks do you have on the phone?  what happen on the home page if you expand the music section?
[18:50] <plars> so far, so good on the automated tests, but it's not very far in - we are past the webbrowser tests on both though
[18:51] <popey> davmor2: not many, crash
[18:51] <popey> known bug, been there a long while
[18:51] <popey> davmor2: see bug links in column Y
[18:52] <davmor2> popey: cool I need to try it on my maguro I've not experienced it before but I'm just waiting for it to get a location :)
[18:52] <popey> davmor2: for location i tail /var/log/syslog and make sure I see location reporting number of satellites it can see
[18:52] <popey> i dont wait for a full lock
[18:52] <popey> it takes aaaaaages
[18:52] <popey> and you have to hang out the window to get ~21 satellites
[18:57] <davmor2> I just sit it by the window for 7-11 minutes but I like to be sure it actually gets a fix rather than just picking up satellites as the 2 don't equate to the same thing ;)
[18:58] <davmor2> popey: the fact you can't use maps.google.com to do anything is besides the point
[18:58] <popey> hah
[18:58] <popey> OSM!
[18:58] <davmor2> popey: maps.google.com open it try typing in a destination
[19:12] <davmor2> rsalveti: do you happen to know what triggers maliit?  if you goto maps.google.com in the browser and click on destination the keyboard never appears, I'm trying to figure if it is the browser to blame, maliit or maliit not triggered due to a missing tag in the browser element.
[20:08] <popey> davmor2: 132 good from your side?
[20:08] <davmor2> popey: yeap did you not get the email I'm sure I added you to it :)
[20:09] <popey> i did!
[20:09] <popey> sorry
[20:09] <popey> nice one dude!
[20:35] <jdstrand> fyi, apparmor/dbus is put ON HOLD, but all testing done. I'll keep an eye on the spreadsheet
[21:28] <fginther> mandel, ping
[22:05] <robru> if anybody sees this, please ping me (i'm testing something)
[22:09] <plars> robotfuel: I see you
[22:09] <plars> robotfuel: sorry, misfire
[22:09] <plars> robru: I see you
[22:09] <robru> plars, great, thanks
[22:09] <robotfuel> heh :D
[23:08] <sergiusens> plars, what is this, avatar?
[23:08] <sergiusens> :-)
[23:09] <plars> sergiusens: heh, I wonder if I made him look behind him when he got that message
[23:10] <plars> awtocomplete fail