[00:17] <lool> ok, so I'm latested mir + keyboard
[00:17] <lool> still getting unity8 + maliit + hud crashes right now
[00:18] <lool> having a hard time getting the unity8 UI
[00:18] <lool> but eventually got it
[00:18] <lool> have to press power button at right time
[00:18] <lool> rebooting to confirm
[00:18] <lool> haha I think I know what makes it work on second boot
[00:18] <lool> it's because it's not writing the crash file
[00:19] <lool> that takes long
[00:19] <lool> ah lost it again
[00:20] <lool> can't wake up the screen anymore
[00:21] <lool> reboot not even working  :-(
[00:22] <asac> lool: what are you running?
[00:23] <lool> #89 + mir and ABI rebuilds from PPA + keyboard
[00:23] <lool> it comes up
[00:24] <lool> ok well it's super simple to crash
[00:24] <lool> just press the power button like crazy
[00:24] <lool> if I go slowly, it's ok
[00:24] <lool> asac: this might be an existing condition
[00:24] <lool> asac: want to give it a try?  :-)
[00:25] <lool> asac: if you're on #89, does it remain black if you press power button a bunch of times?
[00:25] <lool> reboot worked this time
[00:25] <asac> lool: my phone is busted ... i can install latest again
[00:25] <lool> I guess I was a bit unlucky on first and second boot
[00:26] <asac> lool: so you say now its stable?
[00:26] <lool> asac: I think I was a bit unlucky in tsting on my previous install and on second boot here
[00:26] <lool> I also understand why second boot works
[00:26] <lool> it's not apparmor related, it's just that there's an unity8 crash file in place
[00:27] <lool> so a second one isn't generated and it restarts quickly enough in the startup sequence
[00:27] <lool> I just did a phone call
[00:28] <lool> that worked
[00:28] <lool> ok
[00:28] <lool> asac: so I tested basic functionality
[00:28] <lool> it looks like #89
[00:29] <lool> will land these parts after testing keyboard just a bit
[00:29] <lool> ok
[00:30] <lool> == Publishing mir ==
[00:31] <lool> win 75
[00:32] <asac> lool: leave a few channels :)
[00:39] <lool> I have super good news
[00:39] <lool> unity8 doesn't crash once I take hud in
[00:39] <lool> and the hud crash is indeed gone
[00:39] <lool> so we're likely NOT going to see this race on start where it writes the crash
[00:39] <lool> thanks to th enew hud
[00:40] <lool> Last stable build (#43), 1 min 52 sec ago
[00:40] <lool> just a maliit crash now
[00:41] <asac>  \o/
[00:41] <asac> lool: so everything in now?
[00:41] <asac> or ready for copying voer ?
[00:43] <lool> asac: slowly getting into unapproved
[01:03] <lool> sergiusens: landings 168 and 169 -- are the clicks in place?  (dropping-letters stockticker sudoku)  and was music-app built?
[01:03] <lool> checking music-app
[01:04] <sergiusens> lool, music app is not supposed to go in the image as click
[01:05] <asac> will we regress tests when converting them to click? :P
[01:05] <lool> sergiusens: I know, just checking whether it will be in
[01:05] <lool> asac: we're not converting anything this time
[01:05] <lool> asac: just fixing existing tests
[01:06] <lool> sergiusens: can we resume click conversion on friday only?
[01:06] <sergiusens> asac, I'm just staging things for tomorrow, not applying anything
[01:06] <lool> as to leave thursday green for user experience fixes/tweaks
[01:06] <sergiusens> lool, sure
[01:07] <sergiusens> lool, stock ticker didn't make it but you can skip it
[01:07] <lool> rsalveti: you're still landing libhybris?
[01:08] <lool> rsalveti: spreadsheet says for image 90?
[01:08] <sergiusens> lool, it seems trunk is broken or the jenkins instance failed badly
[01:10] <sergiusens> lool, and the music app MR from mine never merged; you can skip it too
[01:10] <sergiusens> fginther, do you know why? https://code.launchpad.net/~sergiusens/music-app/manifest/+merge/190250
[01:11] <sergiusens> fginther, this also failed for no known reason https://code.launchpad.net/~sergiusens/sudoku-app/click/+merge/190231
[01:12] <sergiusens> fginther, from the MR there are no changes made after the approval :-/
[01:15] <sergiusens> fginther, seems stock ticker has been skipping jenkins as trunk doesn't even debuild :-/
[01:16] <cyphermox> fginther: ping?
[01:17] <cjohnston> cyphermox: anything I can try to help you with?
[01:18] <sergiusens> fginther, if you can re trigger https://code.launchpad.net/~sergiusens/stock-ticker-mobile-app/click/+merge/190238 would be great
[01:18] <cyphermox> cjohnston: I just wanted to make sure whether someone was working on "fixing" the autopilot tests
[01:18] <cyphermox> cjohnston: as in, more specifically, the lxc containers that run this with otto
[01:19] <cjohnston> cyphermox: is this the same issue that vila was looking into this morning?
[01:19] <cyphermox> cjohnston: so as not to interfere if I'm about to look into it and someone is already hard at work
[01:19] <cyphermox> cjohnston: maybe? I don't know what he was working on this morning
[01:19] <cjohnston> sergiusens: that MP should automagically retrigger when someone approves it
[01:20] <sergiusens> cjohnston, so stock ticker is auto triggered again?
[01:20] <sergiusens> cjohnston, the emails were a bit confusing
[01:21] <sergiusens> cjohnston, what about https://code.launchpad.net/~sergiusens/sudoku-app/click/+merge/190231 ... the message is kind of like from a ci issue
[01:21] <cjohnston> sergiusens: I'm not 100% sure.. however the first step would be that the MP needs to be approved
[01:21] <sergiusens> cjohnston, as in infra; might be the launchpadlib api returning no approved revno as usual
[01:21] <cjohnston> cyphermox: im looking for the context from this morning..
[01:21] <cyphermox> cjohnston: what I'll be looking into is this failure case:  http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-intel/2484/console
[01:22] <cyphermox> cjohnston: however I'll need help to fix this: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=qa-nvidia-gtx660/2485/console
[01:23] <cjohnston> cyphermox: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-intel/2465/console is what he was looking at this morning
[01:23] <cjohnston> which looks to be quite similar
[01:23] <sergiusens> cjohnston, anyways, this is for future research, but http://91.189.93.70:8080/job/sudoku-app-autolanding/14/parameters/? has revno 137 and that's the last one in the MR
[01:24] <cjohnston> sergiusens: ya.. im looking at that now
[01:24] <cyphermox> cjohnston: I wouldn't say so conclusively, there isn't enough information to tell either way
[01:25] <cjohnston> sergiusens: let me see if I can kick that one again
[01:26] <lool> kgunn: trying https://code.launchpad.net/~lool/hud/readd-desktop-bdep/+merge/190283
[01:26] <lool> cyphermox: do you know anything about hud?
[01:26] <cyphermox> lool: yeah, why?
[01:27] <cyphermox> ah, I misread, sure I'll review
[01:27] <lool> cyphermox: Actualy was looking for some recommendation on testing it on desktop
[01:27] <lool> cyphermox: is it enough if I see file menu from e.g. gedit in hud?
[01:27] <cyphermox> lool: ah. well that should probably be enough, yeah
[01:28] <lool> cyphermox: review welcome then  :-)
[01:28]  * cyphermox wonders why that b-dep was ever dropped
[01:28] <fginther> sergiusens, hey
[01:29] <lool> doing a CI run
[01:30] <sergiusens> fginther, hey, so you can read the backlog if you like or just ignore; mhall just reapproved the failures
[01:30] <cjohnston>                       | is a valid candidate in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html so, again iiuc, should
[01:30] <cjohnston>                       | be available soon and fix Mirv issue
[01:31] <sergiusens> fginther, but I was wondering if you ever reenabled the music app stuff
[01:31] <cjohnston> grr
[01:31] <cjwatson> valid candidate only means it passed the first stage of two
[01:32] <fginther> sergiusens, music-app is disabled intentionally
[01:32] <sergiusens> fginther, ack
[01:33] <sergiusens> to bad I can't get the regressed fix in :-/
[01:33] <cjohnston> sergiusens: http://91.189.93.70:8080/job/sudoku-app-autolanding/15/console
[01:33] <sergiusens> cjohnston, yay
[01:33] <sergiusens> thanks
[01:40] <cyphermox> lool: looks fine but I'd close a bug with it, and I'd make sure the resulting package properly has bamf in its binary depends. Seems to me like it could not be there
[01:43] <cyphermox> lool: nevermind, that... worth checking but I revise my assessment, it's probably in the depends
[01:44] <cyphermox> approved, but I heard you may have to wait before ci / autolanding happens
[01:44] <cyphermox> cjohnston: so should I just leave the lxc containers alone and let vila handle it when he's online?
[01:46] <lool> cyphermox: yup
[01:46] <lool> cyphermox: I'll test the binaries on my desktop
[01:46] <cyphermox> ok
[01:46] <cjohnston> cyphermox: now that fginther is around, he may have more info from vila's findings
[01:48] <fginther> cyphermox, vila mentioned the fix was in proposed, but failed to mention the package
[01:48] <cyphermox> it's lxc
[01:48] <cyphermox> just a matter of upgrading that package and rebooting, and intel should probably be fine
[01:49] <fginther> cyphermox, ack
[01:49] <cyphermox> fginther: nvidia shows a different issue but it will still need to be applied there
[01:51] <lool> cyphermox: I had to fix a bdep
[01:51] <lool> cyphermox: qt was needed on !armhf  :-)
[01:51] <lool> cyphermox: mind top approving?
[01:52] <cyphermox> oh, right yeah qtbase would have been required everywhere
[01:52] <cyphermox> sure
[01:53] <lool> thanks
[01:54] <cyphermox> done
[01:57] <cyphermox> fginther: you handling the package update? (just making sure, I have access to do it, but there's another issue with the nvidia autopilot machine I don't have access to fix)
[01:58] <fginther> cyphermox, I don't think I have access to those machines
[01:58] <cyphermox> ah
[01:58] <cyphermox> then I'll just go ahead and do it
[01:58] <fginther> cyphermox, thanks, I'll look into that tomorrow
[01:58] <fginther> for next time
[01:58] <cyphermox> sure
[01:59] <cyphermox> it's actually super easy, perhaps we can hangout tomorrow and I'll walk you through it
[01:59] <cyphermox> and you most likely already do have access
[02:00] <cyphermox> that said, if you have root or jenkins access on 10.97.0.1, could you prod the qa-nvidia files roughly to fix http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=qa-nvidia-gtx660/2486/console ?
[02:01] <fginther> cyphermox, let's see...
[02:07] <cyphermox> fginther: also, you aware of anything broken with jenkins-slave and why the version would have to stay at 1.509.2+dfsg-1 ?
[02:08] <cyphermox> arf, whatever
[02:08] <fginther> cyphermox, does it need to match the master
[02:08] <cyphermox> possibly
[02:09] <cyphermox> not sure, it's just a debian revision though
[02:09] <fginther> I doubt it does, I think the master supplies all the relavent jar files
[02:09] <cyphermox> I'll update, and there will be a trace here that it's what I did, so if things still don't work, I'll know to revert back to -1
[02:09] <fginther> ack
[02:10] <fginther> have you seen that file permission issue before (it's owned by jenkins, not sure why it's giving it problems)
[02:11] <cyphermox> nope
[02:12] <cyphermox> I assume someone did something manually that caused this permissions issue
[02:12] <cyphermox> rebooting dx-autopilot-intel and qa-nvidia-gtx660 now to finish fixing lxc
[02:13] <fginther> go ahead, I hopefully fixed the perm issue
[02:13] <cyphermox> ack
[02:13] <cyphermox> I'll test it as soon as the machines are back up, I'll have a new container created and try to run some tests through
[02:13] <fginther> was that fix just an update of lxc?
[02:17] <cyphermox> yes
[02:17] <cyphermox> that and reinstalling the jenkins-slave package which was in a very inconsistent state, and blocking all updates of packages
[02:17] <fginther> ack
[02:18] <cyphermox> all the changes are in /var/log/apt/term.log / history.log
[02:23] <cyphermox> fginther: confirming, tests now actually do run again
[02:23] <fginther> cool
[02:23] <cyphermox> they still fail, but that's just because some packages are actually broken or something
[02:23] <fginther> :-)
[02:25] <cyphermox> lool: /var/log/upstart/otto-setup.log:   libmirserver5:i386 Depends on libmirplatform [ i386 ] < none -> 0.0.14+13.10.20131010-0ubuntu1 > ( libs ) (= 0.0.13+13.10.20131003-0ubuntu1) can't be satisfied!
[02:25] <cyphermox> /var/log/upstart/otto-setup.log:   Installing libmirserver6 as Depends of libubuntu-application-api-mirserver1
[02:25] <cyphermox> ^ mir itself or some related package it actually broken, for realz
[02:25] <cyphermox> something built with an older version, I'm guessing
[02:26] <lool> cyphermox: ah we need to update the list I guess
[02:26] <cyphermox> perhaps
[02:26] <lool> cyphermox: didn't know / had forgotten this
[02:27] <cyphermox> I don't think it's the case though, that seems like broken versioned deps more than something wrong in the list
[02:27] <lool> cyphermox: pushing
[02:27] <lool> cyphermox: No I think it's explicitly listed
[02:27] <lool> I've done the rebiulds in the PPA already, should be installable
[02:27] <cyphermox> yeah, I see, you're right
[02:27] <cyphermox> should I file the merge?
[02:28] <lool> nope
[02:28] <lool> pushed
[02:28] <cyphermox> ah, ok
[02:28] <lool> I do like Didier, I push directly to cupstream2distro-config   :-P
[02:28] <lool> sorry
[02:28] <cyphermox> ok
[02:28] <cyphermox> well we still need to update the jobs
[02:28] <lool> I will do a mp next time
[02:28] <lool> cyphermox: I'm doing one
[02:28] <cyphermox> alrighty then :)
[02:28] <lool> second one coming
[02:28] <plars> lool: ubuntu-keyboard autopilots seem to have problems still (especially with mir), was talking to bfiller about that earlier
[02:28] <lool> stacks/saucy/platform.cfg done, stacks/saucy/unity8.cfg in progress
[02:29] <lool> plars: Yes, see #qa
[02:29] <lool> plars: they are known borken
[02:29] <plars> lool: yeah, I was hoping to add them to the daily runs, but he recommended holding off until after 13.10
[02:30] <plars> lool: if they stabilize before then though, I'd be happy to put them in
[02:31] <plars> lool: planning to kick off an image tonight?
[02:31] <cyphermox> lool: ok, so I'll have platform run tests now, so we can check that something possibly goes green
[02:32] <lool> ok
[02:32] <lool> cyphermox: thanks
[02:32] <lool> plars: yes
[02:32] <lool> plars: trying to squeeze hud in
[02:33] <cyphermox> lool: going to be unity8 instead, platform goes green regardless
[02:53] <fginther> bfiller, ping
[02:54] <bfiller> fginther: hey
[03:42] <lool> == Building #90 ==
[03:43] <lool> bfiller, fginther: Would be nice to get this to land https://code.launchpad.net/~om26er/camera-app/disable_video_button/+merge/189566 -- I failed
[03:43] <lool> I've put it on the plan for later this UTC today
[03:46] <bfiller> lool: not sure why the autopilot is failing
[03:47] <bfiller> lool: I tried it on the maguro and worked for me
[03:50] <fginther> lool, bfiller, those same tests failed on  the image test
[03:51] <fginther> at least on mako, hmmm
[03:54] <fginther> lool, rebuilding that failed maguro test here: http://10.97.0.26:8080/job/generic-mediumtests-runner-maguro/2280/
[04:00] <Mirv> vila: awesome! thanks a lot, and good to learn again about the system
[04:01] <fginther> Mirv, morning
[04:01] <Mirv> fginther: "evening" :) or night.
[04:04] <Mirv> ok, so https://launchpad.net/ubuntu/saucy/+source/lxc/1.0.0~alpha1-0ubuntu10 is in release pocket so otto should get fixed
[04:20] <Mirv> launched unity8 + indicators builds, should arrive probably a bit after #90 is ready so I can start testing those
[04:20] <cyphermox> Mirv: don't expect autopilot tests to work
[04:21] <cyphermox> Mirv: seems like both autopilot machines are still having issues due to dbus access through apparmor
[04:21] <cyphermox> (through lxc)
[04:21] <cyphermox> Mirv: I've already updated both to the new lxc
[04:23] <cyphermox> this needs to be further looked at, but I really need to go to bed -- could you file a bug or poke the security team and/or stgraber, and provide them with /var/log/upstart/lightdm.log from the lxc containers? you can get that by starting and logging into the containers manually
[04:23] <Mirv> cyphermox: oh, so it was not enough :( well, I'm used to skipping the check jobs
[04:23] <Mirv> cyphermox: I know how to unpack a recent .otto file at least, possibly also can find how it was to log in
[04:23] <Mirv> cyphermox: I'll contact stgraber
[04:24] <cyphermox> on dx-autopilot-intel, sudo lxc-start -n <container>
[04:24] <cyphermox> on the console you'll see init complain about lightdm failing to start, and there will be logs in /var/log/upstart/
[04:25] <cyphermox> stgraber is in the same timezone as I am though so he might not answer fast :)
[04:25] <cyphermox> ttyl
[04:25] <Mirv> yep, I'll wait for these newest runs to finish
[04:25] <cyphermox> ok
[04:26] <Mirv> we get builds, and we do manual testing on devices anyhow, so funnily enough it's not critical
[04:26] <Mirv> unfortunate, though, getting green light on AP on desktop side is a very useful indicator
[04:28] <Mirv> merging lool's manual unity-mir update
[06:24] <Mirv> FYI I needed to do cu2d-skip -r saucy indicators indicator-messages arm64
[06:26] <didrocks> urgh, arm64?
[06:26] <didrocks> Mirv: hey, it was waiting on it? IIRC, I put that in the ignore list
[06:27] <didrocks> has indicator-messages built or published in saucy on arm64? That would be the only explanation why it's monitoring it
[06:29] <jibel> didrocks, FYI, check jobs because lightdm fails to start
[06:30] <jibel> didrocks, I honestly didn't really had time to look at the details, vila thinks it's because of apparmor
[06:31] <didrocks> jibel: so vila is looking at it? (good way to dive into otto)
[06:36] <jibel> didrocks, he was but was blocked on this apparmor issue
[06:36] <jibel> didrocks, I'm quickly reviewing build 90 and will have a closer look
[06:43] <didrocks> jibel: thanks a lot! still catching up on emails
[06:52] <Mirv> jibel: didrocks: so there was supposed to be lxc update that would fix the otto problem, but cyphermox reported it did not help, and suggested to login to lxc and check /var/log/upstart/lightdm.log and provide that to security team / stgraber
[06:52] <Mirv> didrocks: welcome back, also :)
[06:52] <Mirv> didrocks: there were some recent arm64 churning around, but I don't know the details. maybe related.
[06:55] <didrocks> Mirv: thanks! ok, I'll ask cjwatson abour arm64 ;)
[07:23] <cjwatson> didrocks: the arm64 port is spinning up
[07:23] <cjwatson> didrocks: so yes, it's possible you'll need to cause some things to skip it
[07:24] <cjwatson> didrocks: indicator-messages/arm64 has indeed built and published
[07:24] <didrocks> cjwatson: ok, basically the logic is "check if a binary is available for that arch at the destination and wait for it if there"
[07:24] <didrocks> ok, I'll hack something around for the transition
[07:24] <didrocks> thanks for confirming cjwatson :)
[07:24] <didrocks> Mirv: I'll handle that once I've finished with my emails ^
[07:25] <cjwatson> as infinity put it, "Apple's told the world we all need 64-bit phones", so you folks may care about arm64 at some point rather than it being an irritation :)
[07:28] <didrocks> cjwatson: oh, it's not an irritation at all, just need to handle the fact that the ppa doesn't build arm64 while distro seems to have done so
[07:28] <didrocks> cjwatson: so cu2d was waiting forever
[07:29] <didrocks> cjwatson: if you can enable arm64 on our ppas, that's fine as well
[07:29] <didrocks> (if we have enough builders of course)
[07:29] <cjwatson> didrocks: (a) I can't (b) we're chronically short of builder time (c) I suspect the failure rate will just annoy the shit out of you right now :)
[07:30] <didrocks> cjwatson: ok, so better for us to skip it, got it
[07:31] <cjwatson> we have three builders which we've temporarily (?) stolen from PES, which occasionally throw random faults, and which are desperately trying to get through as much of the backlog as possible before release now that we have a mostly-working toolchain, and one sim which takes hours to even get out of bed but which can be used in desperation cases
[07:31] <didrocks> yeah, so sounds the saner path is to skip it for saucy in the code
[07:31]  * didrocks adds a note
[07:38] <cjwatson> main goal is to have enough in saucy that we can demonstrate that we're making an effort to catch up with other distributions, and that users and customers/partners (we have some already, this is a funded port) can experiment
[07:53] <lool> morning
[07:54] <lool> Mirv: oh wow thanks for noticing and doing it!
[07:54]  * ogra_ dances around bug 1234743
[07:55] <ogra_> seems CM has a patch for it
[07:56] <ogra_> i guess i'll have to build a kernel today
[08:00] <robru> ogra_, heeyyyyyyy there buddy! can you take a look at this super-quick? https://code.launchpad.net/~robru/ubuntu-seeds/ubuntu.saucy/+merge/190262 ;-)
[08:01] <ogra_> robru, wow, we seed it on desktop ?
[08:01] <robru> ogra_, yes, it is going to be the new container for webapps. we desperately need this in 13.10
[08:02] <robru> ogra_, it means we get to shuffle off a lot of crappy firefox/chromium distropatches
[08:03] <ogra_> robru, is there an approved MIR for it ?
[08:03] <robru> ogra_, yes, somewhere. let me find that...
[08:03] <ogra_> seems it sits in universe atm
[08:04] <Mirv> didrocks: could you do a packaging ack? http://10.97.0.1:8080/view/cu2d/view/Saucy/view/Unity8/job/cu2d-unity8-saucy-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity8_7.82+13.10.20131010-0ubuntu1.diff - both dependency additions are from adding the albumart support
[08:04] <Mirv> or ogra_ if he's quick
[08:04] <robru> ogra_, https://bugs.launchpad.net/ubuntu/+source/unity-webapps-qml/+bug/1206268
[08:06] <ogra_> robru, lol, thats the same bug, but i was blind and didnt notice the [MIR] in the title :P
[08:06] <robru> ogra_, haha, yeah
[08:09] <robru> ogra_, did I do the seed correctly? some seed items are in (parentheses) and some aren't, it wasn't clear to me what the distinction is
[08:10] <ogra_> robru, parentheses mean its a recommends (you can uninstall it without tearing ubuntu-desktop out with it)
[08:10] <popey> ogra_: you seeing icons in "more suggestions" on #90?
[08:10] <ogra_> popey, havent started on 90 yet
[08:10] <didrocks> Mirv: sounds sane enough, +1
[08:10] <robru> ogra_, oh, ok. yes, then my MP should be good then
[08:11] <ogra_> robru, already merged, regenerating ubuntu-meta now
[08:11] <robru> ogra_, THANK YOU! and goodnight ;-)
[08:11] <ogra_> sleep well :)
[08:11] <Mirv> robru: good night! :)
[08:24] <asac> hi!
[08:24] <asac> :)
[08:25] <asac> psivaa: are we retrying 90? :)
[08:25] <asac> in particular notes-app feels like it is a regression again
[08:25] <psivaa> asac: i'll do that now.. just starting
[08:25] <asac> hi didrocks !
[08:26] <asac> didrocks: welcome back! :)
[08:26] <ev> congratulations didrocks! Welcome back!
[08:26] <didrocks> hey asac! thanks ;)
[08:26] <didrocks> thanks ev ;)
[08:26] <ogra_> condolenc^Wcongrats didrocks !
[08:26] <popey> asac: what's wrong with notes app?
[08:27] <lool> ogra_: would you think you could do the click list thing easily in the manifest?
[08:27] <ogra_> :)
[08:27] <lool> ogra_: would be nice to see the click updates in your diff then  :-)
[08:27] <asac> popey: in build 90 the AP test failed or didnt run. guess we need to retryu that job
[08:27] <asac> lool: are you still awake?
[08:27] <popey> asac: http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/mako/90:20131010:20131010/4646/notes-app-autopilot/
[08:27] <popey> pass there?
[08:27] <didrocks> ogra_: ahah, thanks a lot :)
[08:27] <ogra_> lool, will need a few changes, livecd-rootfs needs to spit it out on the livefs builder and cdimage needs to learn about copying them
[08:28] <ogra_> lool, i'll try to do that today
[08:28] <asac> popey: http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/90:20131010:20131010/4644/
[08:28] <asac> popey: we are looking at touch_mir only nowadays
[08:28] <popey> ah
[08:29] <ogra_> oh, hmm, wait, i can probably inject it directly into the manifest file
[08:29] <popey> oof
[08:29]  * ogra_ will think about this after the call
[08:31] <lool> ogra_: cool
[08:31] <lool> asac: I had a long night!
[08:33] <ogra_> boooo
[08:33] <ogra_> (server disconnects)
[08:33] <cjwatson> ogra_: yeah, sticking it in manifest directly in the same format is probably sane enough
[08:34] <cjwatson> ogra_: as long as anything generating changelogs is prepared to at least tolerate the packages being missing, and possibly later fetch changelogs from the app store or whatever
[08:34] <ogra_> cjwatson, well, thats jibel's prob, my changelog only is a manifest diff
[08:34] <ogra_> he does the detailed stuff
[08:35] <cjwatson> it may be his problem but I'm sure you don't want to break it at this point ...
[08:37] <ogra_> no, indeed
[09:06] <dpm> hi, would anyone know what's up with the jenkins jobs for core apps? It seems Jenkins reviews don't get triggered again? Here's an example -> https://code.launchpad.net/~rpadovani/ubuntu-clock-app/09Oct2013/+merge/190139
[09:06] <lool> == Building #91 ==
[09:06] <lool> dpm: Some seem to have been disabled, not sure why
[09:08] <dpm> lool, no idea why, either. Would someone be able to help to reenable them so that we don't have to wait until fginther is online?
[09:12] <lool> dpm: I technically might be able to
[09:13] <lool> dpm: do you have a list?
[09:13] <lool> dpm: I'm not sure whether it's a good idea though
[09:14] <lool> dpm: we disabled a bunch of upstream merger jobs because the tests are failing everywhere
[09:14] <lool> dpm: so it's not helpful to send failures
[09:14] <lool> dpm: fginther reenabled some known good ones
[09:15] <lool> dpm: let's wait til he's up to confirm these?
[09:15] <dpm> lool, ok, in that case, sounds good, thanks
[09:15] <lool> dpm: I tried to run a music-app one by hand overnight, and got some failures
[09:15] <didrocks> popey: hey! did you start dogfooding a little bit 90? can you try the usual tests and keep us posted?
[09:16] <psivaa> asac: notes on mako_mir has run (24 pass 1 fail) waiting in transit to dashboard
[09:17] <asac> psivaa: 1 fail == systemsettle?
[09:18] <psivaa> asac: no, it's a test fail different ones during different ones.. flaky tests.
[09:18] <popey> didrocks: i have started, yes
[09:18] <popey> didrocks: icons missing in more suggestions.
[09:18] <psivaa> asac: rerunning may make the passrate low being that flaky
[09:18] <didrocks> popey: turn on the Internet! :)
[09:18] <asac> psivaa: i thought we fixed notes-app flaki tests
[09:18] <popey>           inet addr:192.168.1.120  Bcast:192.168.1.255  Mask:255.255.255.0
[09:18] <popey> it is on
[09:19] <asac> popey: on touch_ro ... e.g. this is a new flaki one
[09:19] <popey> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=46 time=34.3 ms
[09:19] <popey> this is on mir
[09:22] <psivaa> asac: not sure about that.. imho test may appear flaky due to other changes as well.. e.g mir etc
[09:23] <didrocks> psivaa: maybe starts with the 0% ones
[09:23] <cjwatson> popey: oh, good, I was about to ask about that since I was testing a new click version and icons are missing :)
[09:23] <cjwatson> so not my fault
[09:23] <didrocks> asac: psivaa: is 0% on unity8 expected, even without the staged fix?
[09:23] <cjwatson> (missing for newly-installed apps too)
[09:23] <Mirv> didrocks: yes
[09:24] <asac> didrocks: my understanding is that its supposed to get much better with the stale socket fix
[09:24] <psivaa> didrocks: yea we have not made unity8 run fully with mir yet
[09:24] <asac> didrocks: 167
[09:24] <popey> http://imgur.com/uoOfi0D  <- missing icons
[09:24] <didrocks> asac: yeah, ok, I'm up on that one :)
[09:25] <didrocks> popey: do you know if after enabling wifi (I had no network at first), I need to reboot to see the more suggestions?
[09:25] <didrocks> (I never noticed that)
[09:25] <didrocks> maybe because of my script making immediately the image rw + reboot
[09:25] <popey> didrocks: usually locking / unlocking may show them
[09:25] <asac> lool: the powerd fix that is supposed to improve performance is in 90?
[09:26] <popey> i have seen more suggestions not show up on first boot
[09:26]  * didrocks tries
[09:26] <didrocks> popey: usually maybe… not now then :p
[09:26]  * didrocks reboots
[09:26] <popey> lock / wait / unlock then ☻
[09:26] <didrocks> too late, trying to boot now
[09:27] <didrocks> ah better
[09:28] <didrocks> popey: interestingly, the same icons are not appearing for me, but the other are
[09:28] <didrocks> maybe a server side issue?
[09:28] <popey> bug 1237875
[09:28] <didrocks> popey: thanks!
[09:28] <popey> np
[09:28] <didrocks> popey: let's continue dogfooding and check in few minutes if you think we can promote that image
[09:28] <popey> oooh!
[09:29] <popey> more suggestinos just disappeared
[09:29] <popey> then re-appeared
[09:30] <popey> wish unity-scope-click.log had timestamps
[09:33] <jibel> popey, confirmed it's new on 90, did you file a bug or should I?
[09:34] <popey> doing now
[09:37] <popey> jibel: bug 1237886
[09:39]  * popey wonders if someone gave the backend a kick, the icons appear now
[09:41] <didrocks> popey: you did lock/wait/unlock?
[09:41] <didrocks> popey: apart from that one, any other worrying issue that should prevent us from promoting it?
[09:41] <didrocks> jibel: ^
[09:42] <popey> its quite a bit slower
[09:42] <didrocks> than previous Mir image?
[09:42] <didrocks> or compared to SF?
[09:42] <popey> no, than SF
[09:42] <didrocks> yeah, that's an expected (and acceptable from the executives) regressions
[09:42] <popey> ok
[09:43]  * didrocks isn't on the same server than popey maybe… :p
[09:43] <jibel> popey, James tait fixed the icons some minutes ago
[09:43] <popey> ah
[09:44] <jibel> didrocks, 90 LGTM, not too many crashes (don't enable/disable BT from u-s-s) and the main regression found is acceptable
[09:45] <didrocks> jibel: main regression being bug 1237886?
[09:45] <jibel> didrocks, yes
[09:45] <didrocks> popey: ack for you as well? ^
[09:45] <popey> yeah, agreed. it seems pretty good here too.
[09:45] <didrocks> jibel: thanks!
[09:45] <didrocks> ok, let's promote it then
[09:45] <jibel> didrocks, it is also a bit more responsive than previous build but I didn't stress the device
[09:45] <didrocks> jibel: don't stress it too much IMHO (j/k) ;)
[09:45] <didrocks> where is ogra? ;)
[09:46] <didrocks> popey: do you kno who else can promote the image? (apart from stephane)
[09:47] <Mirv> I agree, a bit more responsive than 89, probably thanks to the powerd part
[09:47] <popey> ogra_ was having freenode issues, he's on other irc networks ☻
[09:47] <ogra_> my bip server went crazy
[09:47] <ogra_> didrocks, lool, rsalveti, serguiens, infinity, cjwatson, stgraber and me at least
[09:47] <didrocks> ogra_: ready to promote #90 please? :)
[09:47] <didrocks> I think popey need to send an email?
[09:47] <popey> i shall
[09:48] <didrocks> thanks guys!
[09:48] <ogra_> did qanyone test on maguro ?
[09:48]  * ogra_ didnt yet
[09:48] <popey> i have not
[09:48] <didrocks> ogra_: I don't think that we are going to block on maguro anymore (now that we have Mir)
[09:48] <popey> is 90 == 20131010 ?
[09:48] <ogra_> didrocks, ??
[09:48] <didrocks> ogra_: we know we'll regress (or did the world change?)
[09:48] <ogra_> why would Mir change anything
[09:49] <didrocks> like, it was going to be slow as hell
[09:49] <ogra_> its slow, like it is on mako ... but beyond that it works
[09:49] <jibel> popey, yes
[09:49] <ogra_> and i think i have a fix for the slowness later today ;)
[09:49] <ogra_> (for the driver side at least)
[09:49] <ogra_> didrocks, in any case, many of us have a maguro and need it to work
[09:50] <didrocks> ogra_: oh great! do you think you can give a 5 minutes tests?
[09:50] <didrocks> I was thinking that we were going to call it unsupported and be done
[09:50] <ogra_> for development, fixes and testing ... probably not as a daily phone though :)
[09:50] <didrocks> (the fact that for development people are using it is a right pick)
[09:50] <seb128> ogra_, what about grouper?
[09:50] <ogra_> yeah, its downloading ... give it 20min
[09:50] <didrocks> ogra_: ok, keep us posted, thanks!
[09:50] <cjwatson> grouper at least booted but I haven't tried tests
[09:51] <cjwatson> apart from installing a couple of click packages
[09:52] <ogra_> seb128, grouper and manta are nice to have
[09:52] <ogra_> second prio atm
[09:52] <seb128> k
[09:52] <ogra_> grouper should at least work again though
[09:52] <ogra_> apart from the bluetooth issue
[09:52] <seb128> that's a good news ;-)
[09:53] <popey> thanks jibel
[09:53] <didrocks> ogra_: http://people.canonical.com/~ogra/touch-image-stats/20131010.1.changes, is that automated or you kicked it manually?
[09:53] <didrocks> (the image build)
[09:54] <ogra_> thats automatic, there is a cron job checking cdimage for new images every 5 min
[09:54] <didrocks> ogra_: I'm speaking about starting the build
[09:55] <ogra_> oh, thats manual
[09:55] <didrocks> ok, you did it :)
[09:55] <ogra_> ?
[09:55] <didrocks> for #91
[09:55] <ogra_> i didnt build any images in three or four days
[09:55] <didrocks> hum
[09:55] <didrocks> maybe lool did then?
[09:55] <ogra_> i left that to loic the last days
[09:55] <didrocks> ok
[09:55] <popey> http://people.canonical.com/~ogra/touch-image-stats/20131010.1.changes is that 91?
[09:55] <popey> i.e. not 90
[09:56] <didrocks> popey: yeah, 90 is 20131010
[09:56] <popey> kk
[10:02] <popey> ogra_: ping when published pls
[10:10] <lool> I'm back
[10:11] <lool> didrocks: I started a build after the call as noted here
[10:11] <lool> didrocks: the 10 one is from "late yesterday" aka 4:30 this morning or so, and the .1 one is from just after our call to pick up unity8 and run the image tests
[10:11] <lool> asac: powerd fix is in #90 yes
[10:12] <lool> asac: it's improving performance when resuming from deep sleep (you have to wait some minutes to reach this state)
[10:13] <ogra_> oh, crap, i think it installed 91 now
[10:13] <ogra_> ah, no
[10:24] <lool> 	62	0	0	0	100%	
[10:24] <lool> ups
[10:24] <lool> odd thing  :-)
[10:24] <lool> cleaning the landing spreadsheet
[10:24] <lool> I'm about to step out for lunch
[10:25] <lool> image #91 works nicely here
[10:25] <lool> will play with it some more
[10:30] <ogra_> saving contacts doesnt work in 90 ...
[10:30] <ogra_> diapler app doesnt come up with 90
[10:30] <ogra_> (i can take calls and can tap the dialer app to make it start with the currently running call)
[10:31] <lool> So the -pthread change is confirmed NOT to fix maliit crashes
[10:31] <lool> ogra_: dialer-app worked for me in #90 this night
[10:31] <lool> err morning
[10:31]  * lool tries outgoing call
[10:31] <ogra_> well, it just doesnt come up if you accept a call
[10:31] <lool> yeah works
[10:32] <lool> ogra_: ah
[10:32] <ogra_> i can make the call and all
[10:32] <ogra_> it just doesnt go on screen
[10:32] <lool> trying
[10:32] <lool> ogra_: oh is it meant to?
[10:32] <ogra_> i have to start it via the icon druing the call to see it
[10:32] <ogra_> yes
[10:32] <ogra_> on SF it used to come to the front
[10:32] <ogra_> right after tapping accept
[10:32] <lool> ogra_: But I think we're using snap decisions now?
[10:33] <lool> ogra_: Anyway it was always like this for me  :-)
[10:33] <lool> let's see if it's per design or not
[10:33] <ogra_> it never was like this before
[10:33] <ogra_> right
[10:33] <ogra_> you still can recieve calls
[10:33] <ogra_> so at most its a UI regression
[10:34] <ogra_> 90 looks good otherwise ... the click lens seems a bit crashy
[10:34] <ogra_> (it vanishes and re-poüpulates quite often)
[10:34] <ogra_> popey, ^^^
[10:34] <ogra_> didnt you also see that on mako ?
[10:34] <popey> ogra_: bug already filed about that
[10:34] <popey>  bug 1237886
[10:35] <popey> oh, no thats the other one
[10:35] <popey> no, that is it ☻
[10:36] <ogra_> the category completely vanishes and re-populates if i close an app
[10:36] <ogra_> oh
[10:37] <ogra_> the close button goes away again if you swipe left/right
[10:37] <ogra_> nice
[10:38] <popey> yes
[10:38] <ogra_> ok, 90 looks fine to me
[10:38] <ogra_> well
[10:38] <ogra_> FSVO fine
[10:38] <ogra_> :P
[10:39] <popey> :D
[10:40] <ogra_> ok, 90/20131010 promoted ... give it a few to mirror ...
[10:40] <ogra_> lool, didrocks, asac ^^^
[10:41] <popey> 71.6MB downloading \o/
[10:42] <popey> mail sent
[10:43] <ogra_> thx
[10:43] <didrocks> \o/
[10:43] <didrocks> thanks ogra_, popey
[10:44]  * ogra_ goes to play with maguros graphics driver now 
[10:44] <asac> guys, but 90 is not the image we want... we want 91 for todays release candidate :)
[10:44] <asac> or even 92... the fixes
[10:44] <ogra_> asac, ergh ...
[10:45] <didrocks> yeah, let's cross fingers for 91 AP results
[10:45] <asac> 89 was better than 90
[10:45] <asac> now we cant promote 89 anymore :)
[10:45] <didrocks> but nice to have a first Mir image promoted ;)
[10:45] <asac> yeah thats good
[10:45] <ogra_> right
[10:45] <ogra_> and it isnt that bad
[10:45]  * asac just sees rick coming screaming that the click scopes etc. are regressed
[10:45] <didrocks> psivaa: you are watching the AP results for 91?
[10:45] <ogra_> at leas using it here
[10:45] <asac> well, 89 was better from the user experience :)
[10:45] <asac> anyway
[10:45] <asac> ttyl
[10:46] <psivaa> didrocks: yes
[10:46] <asac> didrocks: we really need to get the scope regressions under control somewhat
[10:46] <didrocks> thanks psivaa
[10:46] <psivaa> yw :)
[10:46] <asac> didrocks: ralsina is off... alecu have to help out
[10:46] <didrocks> asac: yeah, I'm dealing with it right NOW! ;)
[10:46] <asac> ok
[10:46] <asac> thanks
[10:46] <didrocks> yw!
[10:47] <lool> ogra_: cool
[10:47] <ralsina> asac, didrocks: is it the missing icons? That was a server side issue from what I saw yesterday (and yes, I am off but I cheat a little)
[10:47] <lool> ok, trying a dbus workaround for maliit
[10:48] <asac> ralsina: dont do that. we also have apps disappearing from app lens etc.
[10:48] <ralsina> asac: oh, fun
[10:48] <lool> ralsina: BTW sorry I was wrong, another u1-credentials is in the pipe, but we can live without it today and land it between friday and wed
[10:48] <lool> ralsina: get some rest!
[10:48] <didrocks> ralsina: the other one is about more suggestions category randomly disappearing
[10:48] <asac> ralsina: regression from 89 to 90
[10:48] <asac> didrocks: probably crashing?
[10:48] <didrocks> yeah, and go away ralsina, get some rests ;)
[10:49]  * asac thinks that if stuff disappears its usually that the scope crashed etc.
[10:49] <ralsina> lool, didrocks, asac: ok, alecu can handle that, I am off now :-)
[10:49] <didrocks> asac: nothing is /var/crash
[10:49] <didrocks> ralsina: ttyl! :)
[10:50] <didrocks> 12:50:15      mhr3_ | didrocks, fix for that was merged in click scope yesterday
[10:50] <ogra_> on maguro i have a good bunch of crash files
[10:50] <didrocks> asac: ^
[10:50]  * didrocks looks
[10:50] <ogra_> locally i mean
[10:51] <asac> i always have crash files
[10:51] <asac> yes
[10:51] <ogra_> i only have them since Mir
[10:51] <didrocks> asac: ogra_: I have 2 of them, but not related to this, I meant
[10:51] <asac> yeah since mir i have even more
[10:51] <ogra_> http://paste.ubuntu.com/6217497/
[10:51] <didrocks> sil2100: it seems there are work for you :)
[10:51] <popey> um
[10:51] <popey> I updated my daily phone from 89 to 90
[10:51] <popey> system     705  1.3  2.8  67728 54072 ?        Sl   09:59   0:43 /system/bin/surfaceflinger
[10:51] <popey> no mir
[10:52] <didrocks> sil2100: https://code.launchpad.net/~ubuntuone-hackers/unity-scope-click/trunk, hence we have rev 73 at least, let me add a landing plan
[10:54] <didrocks> hum, the history tab I took great care is completely removed now (of the landing plan)
[10:56] <lool> didrocks: the DONE one?
[10:56] <lool> didrocks: it was completely broken this morning, I just removed it this morning
[10:56] <didrocks> ok
[10:57] <didrocks> all my updates, snig!
[10:57] <didrocks> snif ;)
[10:57] <lool> didrocks: Sorry, I should have checked with you first on this, I thought it was still my broken query
[10:57] <lool> didrocks: everything was squashed in one thing, it was unreadable
[10:57] <lool> didrocks: I can try fishing it back though
[10:57] <lool> didrocks: really sorry if I dropped something useful, it looked so much like my broken page  :-)
[10:58] <didrocks> lool: no worry, I wanted to follow what you landed, but if it was broken
[10:58] <Mirv> bah, got some error in unity 7 testing, surely not from indicator-messages so I guess I didn't reboot or something
[10:58] <popey> so.. chaps.. why am I still on surfaceflinger on #90?
[10:59] <didrocks> sil2100: before you land the qtorganizer5-eds, can you please check with me?
[10:59] <Mirv> popey: hmm, I flashed #90 this morning and .display-mir was there and no flinger process
[10:59] <popey> oh balls, my phone is on 83!?
[10:59] <asac> didrocks: lool: so 92 should continue to be only on regressionns from mir
[10:59] <asac> i see eds is now in flight
[10:59] <Mirv> popey: forgot --devel-proposed?
[10:59] <popey> I updated to 90 though. system settings lied
[10:59] <didrocks> asac: yeah, noticed that, hence the ping to sil2100
[10:59] <asac> ok thanks
[11:00] <asac> if its not in archive yet its good
[11:00] <asac> didrocks: double check that that the other item for 92 is wanted
[11:00] <asac> 174
[11:00] <popey> Mirv: no, updated from system settings
[11:00] <didrocks> asac: I think 174 is wanted for Mir crashes (from what I read on #phablet)
[11:00] <lool> didrocks: you can untick the INIMAGE #90 to see it in the main sheet
[11:00] <asac> right
[11:00]  * popey reflashes
[11:00] <asac> didrocks: do we know whats going on with landing 131
[11:00] <asac> that one is big RED still :)
[11:01] <lool> bbiab school
[11:01] <didrocks> asac: I first want to get the scope thing under control (and no other landing), wait a minute :p
[11:01] <asac> didrocks: sounds good.
[11:04]  * ogra_ twiddles thumbs while the kernel builds 
[11:04] <ogra_> so exciting !
[11:07] <davmor2> ogra_: ah sword fighting practice time?
[11:07] <ogra_> dpkg-deb: building package `linux-image-3.0.0-3-maguro:armhf' in `../linux-image-3.0.0-3-maguro_3.0.0-3.18_armhf.deb'.
[11:07] <ogra_> :D
[11:09] <asac> kerne build?
[11:09] <asac> why another one
[11:09] <didrocks> sil2100: not seeing the pings? ;)
[11:09] <ogra_> asac, testing the ultimate fix for the maguro driver ;) it will be a lot more performant with this i suppose
[11:09] <asac> ok... put in a landing ask though
[11:10] <ogra_> asac, once i know it works :P
[11:10] <asac> ah ok
[11:10] <asac> thought it was already in archive :)
[11:10] <ogra_> thats just my local build ...
[11:10] <ogra_> nah, i would never do that
[11:11]  * ogra_ reboots and crosses fingers
[11:16] <ogra_> bah, black screen :(
[11:17] <ogra_> hmm, SF works
[11:17] <ogra_> with one frame per second :(
[11:20] <asac> sounds like a failed landing attempt
[11:20] <Mirv> a tip from Savi_q that service stop powerd before trying to test unity8
[11:20] <ogra_> asac, sounds like Mir doesnt do what i was told it does too though
[11:20] <Mirv> trying that with my http://pastebin.ubuntu.com/6217575/ to see if some success occurs
[11:21] <asac> ogra_: never believe what people tell you :) only believe in code
[11:21] <ogra_> asac, well, according to the Mir guys they dont use the VSYNC uevent ...
[11:21] <ogra_> the patch i'm trying moves VSYNC from uevent to a sysfs node
[11:22] <ogra_> SF still starts ... Mir doesnt
[11:23] <ogra_> aha
[11:23] <ogra_> W/SurfaceFlinger(  659): Timed out waiting for hw vsync; faking it
[11:23] <ogra_> so SF knows how to fake it :P
[11:35]  * ogra_ guesses he needs rsalveti to take a deeper look
[11:44] <fginther> dpm, lool, automatic upstream merger was disabled for apps which have failing tests after the switch to mir. The list was sent to ubuntu-touch-coreapps@lists.launchpad.net
[11:46] <dpm> fginther, thanks. Just came back from a trip and it took me a while to catch up on e-mails. I've just now seen the e-mail and indeed the clock branch is one of the ones being still disabled.
[11:47] <lool> fginther: thanks
[11:48]  * fginther will be back in an hour
[11:49]  * Mirv got sort-of 7/22 success with Unity8 on mir with http://pastebin.ubuntu.com/6217659/
[11:49]  * ogra_ is sad ... i had high hopes for that patch :/
[11:51] <alecu> hi didrocks, lool, asac
[11:51] <alecu> I'm following two bugs that you mentioned above:
[11:51] <alecu> one, icons missing from more suggestions
[11:52] <alecu> two, installed apps being hidden and reshown for a few seconds
[11:52] <didrocks> Mirv: still a start :p
[11:52] <didrocks> alecu: excellent! I think we have a good understanding on both, but please track them :)
[11:52] <Mirv> yep, that's a start
[11:52] <didrocks> alecu: so, mhr3_ told me the second one will be fixed in switching to latest scope-click?
[11:53] <alecu> didrocks: yes, dobey worked on a fix for that. Let me fetch the bug numbers, to see if we are talking about the same.
[11:53] <lool> didrocks: I forgot to highlight this in the meeting, but mediascanner FTBFS in PPA and the previous version was too but differently
[11:54] <lool> will ping thost-r
[11:54] <didrocks> lool: ok, thanks! (but get some rest first ;))
[11:54]  * didrocks is going to handle the clicky scope thing himself as sil2100 is still not around :/
[11:54] <didrocks> popey: free for some tests with me?
[11:55] <popey> ya
[11:55] <lool> didrocks: you want to try landing click stuff?
[11:55] <didrocks> lool: the click scope for fixing the more suggestion
[11:55] <lool> right
[11:55] <didrocks> popey: let me check the status of what's in the ppa, uno momento
[11:56] <lool> there are various small regressions since some unity8 updates that triggers more refreshes I think
[11:56] <popey> didrocks: do i need a RW phone for this?
[11:56] <didrocks> popey: latest image + RW yeah
[11:57] <didrocks> popey: ok, the idea is to remove unity-lens-application from your phone
[11:57] <didrocks> popey: and add ~ubuntu-unity/daily-build ppa, installing unity-scope-click
[11:57] <didrocks> (to uprade to latest version)
[11:57] <didrocks> then reboot
[11:57] <popey> ok
[11:58] <alecu> didrocks: I don't think the latest scope fixes "more suggestions". That's a server issue
[11:58] <didrocks> popey: for the tests, I wrote those I think that are useful (line 175 in https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc#gid=0)
[11:58] <didrocks> alecu: oh? mhr3_? ^
[11:58] <alecu> didrocks: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1237834
[11:58] <didrocks> alecu: there are 2 things
[11:58] <didrocks> icons not showing up
[11:58] <didrocks> (yeah, seems to be server-side)
[11:58] <popey> didrocks: kk
[11:58] <didrocks> and whole "more suggestions" not appearing
[11:58] <alecu> didrocks: the latest scope fixes another thing, which is momentarily disappearing installed apps
[11:58] <didrocks> (the category itself)
[11:58] <mhr3_> didrocks, that's about the icons
[11:59] <mhr3_> didrocks, it will fix the "flickering"
[11:59] <didrocks> mhr3_: flickering being, no "more suggestions" at all, right?
[11:59] <mhr3_> didrocks, it disappears, reappears... etc etc
[11:59] <alecu> didrocks: no: flickering means half the apps (the click ones) dissapearing for a second, then reappearing
[12:00] <didrocks> hum, seems different then
[12:00] <didrocks> 12:49:54   didrocks | mhr3_: more seriously, it seems that between image 89 and 90, we have "more suggestions" category randomly
[12:00] <didrocks>                     | disappearing
[12:00] <didrocks> 12:50:00   didrocks | (for the apps)
[12:00] <didrocks> popey: it's what you saw as well, right? ^
[12:00] <popey> i put a video on the bug showing what I saw ☻
[12:00] <lool> this is what I'm seeing too; some pieces of the UI disappear and appear fairly often
[12:00] <popey> the camera never lies
[12:01] <lool> and I get some display glitches, but feel more like presentation / logic issues than low level mir stuff
[12:01] <popey> same here lool
[12:01] <popey> not seen graphical glitches as I'd define them
[12:02] <alecu> popey: what's the bug you put that on?
[12:02] <lool> popey: I lack a name for that, but basically I'm sometimes seeing graphical elements overlap
[12:02] <popey> bug 1237886
[12:02] <lool> that shouldn't be
[12:03] <popey> bah
[12:03] <sil2100> I was on lunch, super early today
[12:03] <popey> https://www.youtube.com/watch?v=QnW5fkqZpKc alecu
[12:03] <alecu> thanks
[12:03] <sil2100> didrocks: the qtorganizer stuff is tested and ready to go, I didn't publish it as I didn't get the consensus if we should publish anything non-mir-fixing or not
[12:04] <didrocks> sil2100: no, hold on on that one (but great to have it staged though! ;))
[12:04] <didrocks> we only take mir-fixing stuff first
[12:04] <sil2100> didrocks: is it breaking anything ;p ?
[12:04] <sil2100> Ah
[12:04] <didrocks> sil2100: I don't care, it's a risk :p
[12:05] <sil2100> btw. anyone else encountering https://bugs.launchpad.net/unity8/+bug/1237838 ?
[12:05] <alecu> didrocks, popey bug is what dobey was working on yesterday. We suspected it was the old "infinite loop" bug, so we reopened that: https://bugs.launchpad.net/unity-scope-click/+bug/1233756
[12:06] <didrocks> alecu: I'm still worried on rev 72 though
[12:06] <didrocks> why refactoring so close to the release?
[12:06] <didrocks> sil2100: already opened, server-side issue (and under fix)
[12:06]  * alecu looks
[12:07] <mhr3_> didrocks, the more suggestions disppear, reappear from popey's video is fixed with 73, the icons missing is server issue (when more suggestions is actually there), anything else is yet another bug
[12:07] <didrocks> mhr3_: yeah, I didn't see it at all for several seconds, so unsure
[12:09] <alecu> didrocks: ah, by rev 72 you mean the moving of the old app scope to inside the click scope.
[12:10] <didrocks> yeah
[12:10] <asac> do we see more unity8 crashes beyond in webbrowser?
[12:10] <didrocks> it seems quite a risky move few weeks before the release
[12:10] <alecu> didrocks: yes, it's a huge change, but afaik it has already landed, right mhr3_?
[12:10] <didrocks> alecu: it didn't
[12:11] <didrocks> well, it's in trunk
[12:11] <didrocks> but not in archive/image
[12:11] <asac> hud is still crashing in 91
[12:11] <didrocks> what does this fix? can we back that out and do that next cycle?
[12:11] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/91:20131010.1:20131010/4658/share-app-autopilot/
[12:11] <mhr3_> alecu, it's not in the image yet
[12:11] <mhr3_> afaik
[12:11] <popey> my phone is flickering like mad now..
[12:11] <mhr3_> alecu, it is in the daily ppa though
[12:11] <didrocks> thostr_1: hey, hud is still crashing in 91: http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/91:20131010.1:20131010/4658/share-app-autopilot/
[12:11] <didrocks> popey: with the changes?
[12:12] <sil2100> didrocks: so, can I help with something? ;)
[12:12] <didrocks> sil2100: I'm trying to decipher if we do that scope transition or not TBH ^ :)
[12:12] <thostr_1> didrocks: ok, looking into it right now
[12:12] <popey> didrocks: yeah
[12:13] <didrocks> mhr3_: mind helping popey? ^
[12:13] <didrocks> if it's due to the code change, I would say, let's back out rev 72
[12:13] <mhr3_> popey, video pls :)
[12:13] <didrocks> it doesn't seem to be the best time for those changes
[12:14] <mhr3_> it won't have anything to do with 72
[12:15] <popey> mhr3_: uploading
[12:16] <Saviq> ev, ping
[12:16] <ev> Saviq: pong
[12:16] <Saviq> ev, hey, is it normal I had to comment out -proposed and -updates ddebs and add deb-src for the retraces with daisy?
[12:17] <Saviq> ev, retracer would complain about 404s and no sources otherwise
[12:17] <ev> oh interesting
[12:17] <popey> mhr3_: it's like running a 60 hz game on a 50hz telly
[12:17] <ev> there is a bug when -updates is used too early, but this doesn't sound like it
[12:17] <ev> which ones were 404ing?
[12:18] <didrocks> sil2100: do you mind trying this as well?
[12:18] <cjwatson> popey: funny, that's what the software-center icon has always reminded me of
[12:18] <didrocks> sil2100: apt-get install unity-scope-click on latest image from the ppa
[12:18] <didrocks> sil2100: removing u-l-a + reboot
[12:18] <cjwatson> I genuinely thought the lines across the middle of it were a graphical glitch for the longest time
[12:18] <sil2100> didrocks: is 90 the latest?
[12:19] <popey> mhr3_: https://www.youtube.com/watch?v=Vqq7ag7QxDg - can't see it
[12:19] <popey> hah
[12:19] <didrocks> sil2100: 91 is the latest, but I think 90 is fine enough
[12:19] <popey> bah, stopped flickering now
[12:20] <didrocks> popey: I always see your videos as marketing one with your voice :p
[12:20] <popey> haha
[12:20] <popey> i have about 50 videos which only show bugs
[12:20] <popey> they're all unlisted otherwise my channel would look like youtubes best ubuntu haters channel
[12:21] <sil2100> didrocks: trying, rebooting now
[12:23] <mhr3_> popey, hmmmm, don't think it's in any way related to the click
[12:23] <popey> yeah
[12:23] <mhr3_> mir thing?
[12:23] <popey> no idea, could be
[12:24] <sil2100> popey, mhr3_: once I get my phone booted up again I'll inform if I get the same flickering
[12:24] <mhr3_> popey, can you rep it with each reboot?
[12:24] <Saviq> ev, -updates and -security ddebs
[12:27] <sil2100> popey, mhr3_: on image 90 with u-l-a removed an u-s-c 0.1+13.10.20131010-0ubuntu1 installed I see no flickering
[12:27] <sil2100> didrocks: ^
[12:28] <didrocks> sil2100: ok, can you please try launching an app/installing/removing, see previews, check that all apps (especially defaults one that are .deb are shown?)
[12:28] <ev> Saviq: when was this? They were missing, but slangasek pointed it out and pitti fixed it this morning.
[12:28] <Saviq> ev, yesterday
[12:28] <ev> (I'm presuming this is 13.10 armhf)
[12:28] <ev> ah right, do try again :)
[12:28] <Saviq> ev, so that might be fixed already :)
[12:28] <ev> whoop
[12:28] <sil2100> didrocks: ok, so testing the click scope altogether? Sure thing, doing
[12:29] <Saviq> ev, btw, feels like this email could go to ubuntu-phone at least - if not ubuntu-devel even
[12:30] <ev> Saviq: asac asked me to dup it to ubuntu-phone and I did yesterday
[12:30] <didrocks> sil2100: please
[12:31] <Saviq> ev, you're ahead of me...
[12:31] <ev> :D
[12:32] <popey> mhr3_: can't repeat it now
[12:34] <mhr3_> popey, so... mir :)
[12:34] <popey> probably
[12:35] <popey> didrocks: seems okay here. rebooted a few times, installed apps, icons still there, apps still run
[12:35] <didrocks> popey: and default apps are shown?
[12:36] <didrocks> (the one which are still .deb)
[12:36] <popey> yes, i see browser, camera, contacts, dialler, file manager, friends, gallery, messaging, music, system settings, terminal, update manager, stock ticker, sudoku, dropping letters... etc
[12:36] <sil2100> didrocks: it seems fine here, installing and uninstalling works - it seems to be a bit flacky, but as everything with Mir enabled ;/
[12:37] <sil2100> didrocks: by 'flacky' I mean, sometimes I need to scroll the screen up and down to see 'More suggestions' category ;p
[12:37] <didrocks> popey: sounds good! sil2100 confirmining seeing those? ^
[12:38] <didrocks> sil2100: seems more Mir-related, right? it was already the case?
[12:40] <sil2100> No application seems missing
[12:45] <didrocks> sil2100: ok, great!
[12:45] <didrocks> sil2100: let's get that scope click in please ;)
[12:45] <didrocks> psivaa: ok, next issue, it seems that we still have webbrowser-app tests results being as low as we had before
[12:45] <sil2100> didrocks: just the click scope for now, or the whole click stack? ;)
[12:45] <didrocks> psivaa: can you work on that/check with Saviq?
[12:46] <didrocks> 14:45:33      Saviq | didrocks, ok, I did stop powerd, running now with powerd runnin
[12:46] <didrocks> for context ;)
[12:46] <didrocks> sil2100: what we tested, meaning click scope
[12:47] <didrocks> ogra_: I'm uploading the seed transition for it FYI, nothing else was pending?
[12:47] <ogra_> not from my side
[12:48] <fginther> morning
[12:50] <Saviq> didrocks, psivaa, that's mako, mind you
[12:50] <didrocks> Saviq: it is
[12:50] <lool> didrocks: are you also taking ask 135 with the seed change?
[12:51] <didrocks> lool: yeah, I'm talking about that one
[12:52] <vila> didrocks, lool: https://code.launchpad.net/~vila/cupstream2distro/star-log/+merge/188875 can get some love ;)
[13:01] <sil2100> didrocks: u-s-c in proposed \o/
[13:01] <lool> vila: ack
[13:01] <lool> vila: approved but not top approved as I can't really run the tests
[13:01] <didrocks> sil2100: great!
[13:04] <psivaa> didrocks: Saviq: was talking to tvoss in #phablet, in the webbrowser-app test runs in mako we see unity8 crash :
[13:04] <psivaa> http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/91:20131010.1:20131010/4658/webbrowser-app-autopilot/
[13:06] <didrocks> let's see what Saviq will say
[13:16]  * psivaa needs to pop put for an some time.. will be back a bit later
[13:25] <ogra_> lool, didrocks, erm, could you guys drop the duplicated "stop on" line ?
[13:25] <ogra_> (that seems to be a merge error from some time before ... the bottom one needs to go)
[13:26] <ogra_> lool, didrocks (talking about the maliit upstart job change)
[13:27] <lool> Good news everyone
[13:27] <lool> tvoss confirmed we could start keyboard *after* unity8 and this fixes the maliit-server crash in my testing!
[13:27] <lool> Fix uploaded
[13:27] <lool> will build an image with it once in archive to get cleaner results
[13:27] <lool> ogra_: Oh right
[13:27] <lool> ogra_: it seemed bogus to me too
[13:28] <didrocks> ogra_: urgh, I need coffee as well
[13:28] <lool> ogra_: I've already uploaded, but please send a mp for it and I'll approve it
[13:28] <lool> ogra_: stop on stopping unity8 is enough IMO
[13:28] <lool> ogra_: other good news: dropped a sleep 1  :-)
[13:28] <ogra_> lool, can i just upload without MP
[13:28] <ogra_> yay !
[13:28] <lool> ogra_: let's not upload right now but let that one go through quickly
[13:28] <didrocks> yeah, delighted with that one :p
[13:28] <lool> ogra_: but once it's in archive, please do
[13:28] <ogra_> k
[13:29]  * ogra_ wishes hs omapfb change would work better 
[13:29] <ogra_> all my hopes ... trashed ...  life is so mean
[13:30] <dobey> huh
[13:30] <sil2100> didrocks, Mirv, jibel: nvidia hanged up again...
[13:31] <sil2100> Will try to terminate the job and see if things move on
[13:31] <didrocks> sil2100: hum "again"? I probably missed an episod :p
[13:31] <didrocks> or is it the lxc issue that was discussed?
[13:31] <didrocks> (I think jibel is looking at the issue)
[13:31] <sil2100> didrocks: we still seem to be having DNS issues from time to time again
[13:31]  * didrocks *sighs*
[13:31] <sil2100> didrocks: well, it hanged up just as it did in the past, not sure what's the currently most trendy way of things hanging up :D
[13:32]  * sil2100 likes trendy hang-ups
[13:32] <didrocks> ev: do you think we can really have all those done as a priority? ^ (as it started near our sprint in Boston), even if things are better, seems it's not fully fixed
[13:32] <Mirv> didrocks: sil2100: it's not time to time but every time since Tuesday morning, although last night with the lxc fix it seems to have changed
[13:33] <Mirv> didrocks: I think I CC:d you on the e-mail that was the latest on the topic, basically the new errors seen after the lxc fix went in
[13:33] <ev> didrocks: the DNS issues?
[13:33] <didrocks> Mirv: yeah, when sil2100 told about nvidia hang, I thought this was specific to nvidia (so another issue)
[13:33] <Mirv> so it's somewhere between apparmor <-> dbus <-> lxc, apparmor and dbus saw big uploads Mon-Tue night
[13:33] <Mirv> ev: well I don't think there anything left that's actually a DNS issue
[13:34] <didrocks> ok, so those issues are not DNS-related?
[13:34] <bfiller> asac, plars : are we sure we're unlocking the greeter before running the tests? omer did some debugging and found the messaging-app failure due to greeter not being unlocked
[13:34] <didrocks> sil2100: do you have the trace?
[13:34] <Mirv> this http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=qa-nvidia-gtx660/2494/console is about the X not starting
[13:34] <didrocks> indeed, the whole DNS resolution happened
[13:34] <Mirv> and the lightdm log was http://pastebin.ubuntu.com/6216936/
[13:34] <didrocks> sil2100: why did you talk about DNS issues?
[13:35] <bfiller> asac, plars : can't stop unity8 anymore like we used to, but assuming you know that already. greeter needs to be unlocked before running tests
[13:35] <ogra_> bfiller, we are sure that there are hacks to unlock the screen in utah that work with SF ...
[13:35] <asac> bfiller: we had that discussion just a few minutes ago
[13:35] <ogra_> wether they still work in Mir is another story
[13:35] <asac> bfiller: we always unlocked greeter
[13:35] <asac> bfiller: for all app tests
[13:35] <plars> bfiller: yes, we unlock the greeter but not for unity8
[13:35] <asac> bfiller: at least for a couple month :)
[13:36] <ogra_> asac, are we sure that still works after the Mir switch
[13:36] <asac> the "stop unity before app tests", never worked well
[13:36] <asac> ogra_: we had that discussion as well
[13:36] <plars> ogra_: yes
[13:36] <ogra_> k
[13:36] <asac> plars just triple checked afaik
[13:36] <asac> also i see the same numbers locally after unlocking
[13:36] <asac> that we see on the dashboard
[13:37] <bfiller> asac: specifically with the messaging-app tests we're only able to get it to fail locally when greeter is locked, just one data point
[13:38] <asac> bfiller: with mir?
[13:38] <asac> bfiller: i think messaging-app was not one of the flaki ones
[13:38] <asac> plars: did we have problems with messaging-app and needed to retry that?
[13:38] <sil2100> didrocks: right, it's not DNS, been too quick with judgement
[13:38] <didrocks> ok
[13:38] <bfiller> asac: yes with mir
[13:38] <didrocks> sil2100: please read logs :p
[13:38] <sil2100> Mirv: what's up with X not starting? I might have missed some e-mails, but now intel is stuck it seems on the same thing
[13:38] <bfiller> asac: and all the autolanding jobs are failing the same with that
[13:38] <sil2100> Mirv: for platform stack
[13:38] <asac> hmm
[13:39] <asac> bfiller: let me try as well
[13:39] <asac> plars: can you quadruple check?
[13:39] <plars> asac: if we did it would have been earlier, psivaa-afk might know but I can look and see if it was restarted
[13:39] <asac> would be nice to see that it unlocks in the log
[13:39] <asac> bfiller: is messaging app converted to click?
[13:39] <bfiller> asac: no
[13:39] <asac> kk
[13:40] <Mirv> sil2100: so if you haven't followed, all check jobs have failed since Tuesday morning (just look at http://10.97.0.1:8080/job/autopilot-saucy-daily_release/). you were CC:d in the "Re: cu2d check job failure"
[13:40] <asac> plars: so where is the script that unlocks the phone? how can i run it locally?
[13:40] <fginther> plars, are you seeing any problems with the screen unlock code? It looks like all the upstream merger tests are failing due to what looks like a failure to introspect unity8
[13:40] <asac> fginther: thats what i want triple checked
[13:40] <sil2100> Mirv: I quietly thought that's fixed already ;p
[13:40] <asac> fginther: can you find that code and see if it works?
[13:40] <fginther> asac, working on it now
[13:41] <sil2100> Mirv: then the only way is to just abort the jobs for now, yes?
[13:41] <asac> fginther: thanks... keep us posted. very importrant to know 100% that we are doing it right
[13:41] <Mirv> sil2100: yes, currently that's the only way (timeout after 2h as well)
[13:41] <sil2100> Bummer
[13:42] <plars> asac: looks like the messaging tests worked on maguro, just not on mako. It had not been restarted but I'll restart it now, and also try it locally so I can watch what it's doing on mako
[13:42] <plars> bfiller: ^
[13:42] <asac> bfiller: so running it twice makes it fail
[13:42]  * asac reboot
[13:42] <asac> plars: ok. still more and more people report that we might not have unlocked
[13:42] <asac> so we should take that super serious :)
[13:42] <asac> at best using the camera in the lab to observe
[13:43] <plars> asac: I just ran a test with friends-app (because it's quick) and watched it unlock just fine here
[13:43] <asac> plars: run it 20 times :)
[13:43] <plars> asac: I am
[13:43] <asac> plars: how do you run it?
[13:43] <plars> asac: locally? I'm running it with the same script we use in the lab
[13:43] <asac> and are you 100% sure that the code you try locally is the same as in the lab
[13:43] <plars> from the lp:ubuntu-test-cases/touch branch
[13:43] <asac> ok
[13:43] <plars> asac: 100%
[13:44] <asac> without looking? :)
[13:44] <plars> asac: with or without - I'm running from the exact same branch
[13:44] <asac> k
[13:45] <plars> asac: there could, of course, be some corner case where it doesn't unlock - if we believe messaging app has shown this, I'll run the messaging app test lots of times in a loop here... that's what I'm doing now
[13:45] <plars> asac: and I'll watch while it's doing it
[13:46] <asac> yeah
[13:46] <asac> plars: i am not sure... dashboard says 4 tests, with 2 fail 2 succeess
[13:46] <asac> locally i get 2 success and 0 fail i think
[13:46] <plars> asac, bfiller: messaging app passed on the retry for mako
[13:46] <asac> plars: with 2 success?
[13:46] <asac> or 4?
[13:47] <asac> otherwise we have a dashboard bug i think
[13:47] <asac> messaging-app-autopilot 2013/10/10 11:37 4 2 2 0 2 50%
[13:47] <plars> asac: 4 - 2 of those are systemsettle
[13:47] <plars> asac: where are you looking? I don't think it's shown up for maguro yet
[13:48] <asac> looking at last run:
[13:48] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/91:20131010.1:20131010/4658/
[13:48] <asac> didnt know that we have 2 for ss
[13:48] <asac> thats fine then and makes sense
[13:48] <plars> asac: that's the old run
[13:48] <plars> asac: and on mako
[13:48] <plars> asac: those failed both of the messaging tests indeed
[13:49] <plars> asac: but the rerun that I just did, they all passed fine
[13:49] <rsalveti> ogra_: for the vsync one disabling in upstart is fine, isn't it?
[13:49] <asac> plars: do we see crashes int he rerun too>
[13:49] <rsalveti> it was already disabled
[13:49] <lool> didrocks: any objection for me to kick an image build when session enters release pocket?  (some minutes)
[13:49] <plars> asac: same at home, but I'll keep trying to reproduce some case where it does not unlock
[13:49] <didrocks> lool: no objection as well, I guess the seed change is already in (didn't check)
[13:49] <plars> asac: yes, still crashes on unity8 and maliit-server
[13:49] <didrocks> let me look still
[13:49] <didrocks> ah unity-scope-click | 0.1+13.10.20131010-0ubuntu1 | saucy-proposed/universe | source, amd64, armhf, i386
[13:49] <ogra_> rsalveti, well, its a gross hack ... and we need the same for udev ...  and the traffic will still be there and put load on the system, even if we hide it
[13:50]  * didrocks looks
[13:50] <lool> didrocks: seems so
[13:50] <didrocks> lool: the seed change is, not the scope
[13:50] <lool> didrocks: ah no, I dont see your upload
[13:50] <lool> didrocks: where's the seed change?
[13:50] <rsalveti> ogra_: right, but I believe that's fine anyway
[13:50] <ogra_> rsalveti, i found a patch for the espresso arch that switches from uevent to a sysfs node ... this works fine on the kernel side but i cant get the userspace to make use of it
[13:50] <rsalveti> well, binary blobs :-)
[13:50] <lool> didrocks: dont see an ubuntu-touch-meta upload
[13:51] <ogra_> rsalveti, i can get SF to start but it falls back to faking vsync
[13:51] <didrocks> lool: I didn't dput, but I wanted to see the scope in the archive first
[13:51] <rsalveti> ogra_: right
[13:51] <ogra_> rsalveti, and Mir doesnt start at all
[13:51] <didrocks> lool: let me look at why it's not in
[13:51] <didrocks> sil2100: did you track it?
[13:51] <ogra_> rsalveti, you dont think we could somehow make it read from sysfs instead of uevents ?
[13:51] <didrocks> unity-scope-click/i386 unsatisfiable Depends: libunity-protocol-private0 (>= 7.1.2+13.10.20131010)
[13:51] <didrocks> lool: were we under any transition?
[13:51] <rsalveti> ogra_: nops
[13:51]  * didrocks looks
[13:52] <ogra_> hmpf :(
[13:52] <didrocks> mhr3_: hum, you did add a new symbols and used it? ^
[13:52] <ogra_> xnox, so we will need your udev filter
[13:52] <ogra_> seems there is no way around
[13:52] <lool> didrocks: Bad!  unity-scope-click/i386 unsatisfiable Depends: libunity-protocol-private0 (>= 7.1.2+13.10.20131010)
[13:52] <sil2100> Right!
[13:52] <rsalveti> how much cpu is udev consuming?
[13:52] <sil2100> Shit, it needed libunity, just now I remember it pulled it in
[13:52] <ogra_> rsalveti, constantly 5-10% while the screen is on
[13:53] <sil2100> But we'll have to do more tests for that I guess
[13:53] <didrocks> sil2100: you should have seen that when apt-get install :/
[13:53] <rsalveti> ogra_: right, when rendering stuff in there
[13:53] <sil2100> Let me upgrade the desktop
[13:53] <ogra_> rsalveti, what bothers me a bit that this hasnt been an issue before
[13:53] <didrocks> didn't it force it?
[13:53] <lool> didrocks, asac: That said, it will just drop the number of crashes on dashboard, it will not help any of the AP runs I think
[13:53] <lool> since maliit respawned immediately
[13:53] <didrocks> lool: don't you think things timed out?
[13:53] <rsalveti> ogra_: did you try filtering in udev to see what happens in the userspace side?
[13:53] <xnox> ogra_: ack.
[13:53] <ogra_> rsalveti, and i dont know when it started ... i used to be able to use my maguuro for a day without running out of RAM ... bow its like 20-30min max
[13:54] <didrocks> lool: maybe there is a long tail of cause->consequence?
[13:54] <rsalveti> well, the uevent was always there
[13:54] <rsalveti> who is leaking memory now?
[13:54] <ogra_> rsalveti, but was it always exposed ?
[13:54] <rsalveti> always
[13:54] <ogra_> rsalveti, upstart is ...
[13:54] <lool> didrocks: possibly
[13:54] <lool> didrocks: if the test starts real quick
[13:54] <lool> but I kind of doubt it
[13:54] <rsalveti> ogra_: it wasn't before we flipped the container
[13:54] <popey> didrocks: landing asks has a fix for EDS from renato.. is that likely to land?
[13:55] <popey> in the image
[13:55] <lool> we will see I guess
[13:55] <rsalveti> ogra_: still?
[13:55] <ogra_> rsalveti, well, upstart collects it and doesnt free it, jodh works on fixing the freeing
[13:55] <rsalveti> oh, ok
[13:55] <ogra_> but he doesnt work on fixing the root cause
[13:55] <didrocks> popey: not today
[13:55] <popey> didrocks: tomorrow?
[13:55] <rsalveti> let's try to filter it in udev and see
[13:55] <didrocks> popey: probably, there is still this Mir blocking everything
[13:55] <ogra_> rsalveti, well, i dont think it was there when we flipped
[13:55] <popey> right, will that be final last?
[13:56] <ogra_> rsalveti, it definitely only caused issues for me since a week or two
[13:56] <rsalveti> ogra_: it was always there :-)
[13:56] <rsalveti> the uevent
[13:56] <rsalveti> it might be because we got a newer upstart along the way
[13:56] <ogra_> was it always on the system dbus ?
[13:56] <didrocks> popey: depends, it's hard to know when things are getting fixed and getting ETAs TBH :)
[13:56] <ogra_> or in udev ?
[13:56] <ogra_> udevd didnt consume much CPU for me in the past
[13:57] <rsalveti> well, I assume udev was getting all the events in there
[13:57] <popey> didrocks: trying to figure out our absolute deadline for core apps updates ㋛
[13:57] <didrocks> sil2100: so, you are installing that on your laptop and testing quickly?
[13:57] <ogra_> rsalveti, could it be that hybris shielded it before ?
[13:57] <rsalveti> can't, it comes from the netlink
[13:57] <ogra_> so that we didnt actually see it on the ubuntu side
[13:57] <ogra_> weird
[13:57] <rsalveti> so kernel -> udev was always there
[13:58] <didrocks> popey: the earliest is tomorrow, but plan Monday
[13:58] <rsalveti> now what happens via udev -> upstart is what caused it
[13:58] <ogra_> well, upstart/udev/bridge isnt so new either
[13:58] <rsalveti> we got a newer udev and upstart since we flipped
[13:58] <ogra_> *upstart-udev-bridge
[13:58] <sil2100> didrocks: did that already, both desktop and phone are fine, preparing things for release and double checking
[13:58] <rsalveti> ogra_: we were using the old udev before
[13:58] <rsalveti> then we switched over to use the systemd based one
[13:58] <ogra_> hmm
[13:58] <rsalveti> from the same source and such
[13:58] <sil2100> No packaging changes
[13:58] <ogra_> we always used the systemd one in saucy though
[13:58] <rsalveti> and we got a new major version of upstart
[13:59] <ogra_> it switched very early in the cycle
[13:59] <rsalveti> right
[13:59] <didrocks> sil2100: ok, please do it now
[13:59] <ogra_> and i'm sure udevd wasnt always under the top consumers in top
[13:59] <ogra_> it now is
[14:01] <asac> lool: right. as expected
[14:01] <asac> lool: i believe its still due to something weird
[14:01] <asac> like: what fixes the webbrowser APs for saviq
[14:01] <asac> unity8 crashing while running certainly could be one reason
[14:02] <asac> but he also has those crashes
[14:02] <sil2100> didrocks: it's in the unapproved queue now
[14:02] <asac> so i believe there is more into it
[14:03] <ogra_> rsalveti, what i find strange is that  CM10.2 on espresso seems to use that sysfs change just fine (though i assume they have a newer PVR or whatever in espresso)
[14:03] <lool> can someone update me on latest trickses to run unity8 testsuite?
[14:03] <didrocks> sil2100: great! pinging the release team?
[14:03] <lool> I'd like to test socket removal here
[14:03] <rsalveti> ogra_: just different pvr
[14:03] <rsalveti> pvr is a mess
[14:03] <ogra_> k
[14:06] <dpm> fginther, how can we get this branch for clock merged? -> Can we enable the Jenkins merger or do we do it manually?
[14:06] <dpm> https://code.launchpad.net/~rpadovani/ubuntu-clock-app/09Oct2013/+merge/190139
[14:07] <fginther> dpm, one moment
[14:10] <fginther> dpm, clock is passing in the latest image, I'll turn automatic merges back on
[14:19] <dpm> perfect, thanks fginther
[14:21] <Saviq> asac, when I had 100%, nothing crashed - or at least not unity8 or maliit-server
[14:22] <Saviq> asac, confirmed jibel's crash in maliit-framework https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1237870
[14:24] <asac> Saviq: ok. so the crashes will most likely fix it
[14:24] <asac> then lets focus on the unity8 crashes... do you see that?
[14:25] <asac> Saviq: can you reproduce the unity8 crashes that we see during AP tests?
[14:28] <Saviq> asac, yeah, some - we're on it
[14:28] <Saviq> asac, unity8 crashes - send them to me
[14:28] <Saviq> asac, got any .crash files?
[14:33] <vila> lool: thanks for the review, yes the tests expect you to sudo
[14:34] <vila> lool: ask didrocks for rationale but roughly the integration tests needs to really exercise pbuilder
[14:38] <ricmm_> asac: dude
[14:39] <ricmm> asac: http://people.canonical.com/~ricmm/powerd_0.13+13.10.20131009-0ubuntu1_armhf.deb
[14:39] <ricmm> try with that
[14:48] <lool> Saviq: is there a bug for the top/bottom + left/right scrolling creating UI glitches
[14:48] <Saviq> lool, first time I've heard of it
[14:55] <bfiller> asac, fginther : we believe many of the failed tests are caused by this bug https://bugs.launchpad.net/mir/+bug/1238062
[14:56] <bfiller> this is only occuring under mir and not SF
[14:56] <sil2100> didrocks: do we have to skip arm64 builds manually in cu2d?
[14:56] <bfiller> something causing toolbar to think it's still animating after 10 seconds
[14:56] <didrocks> sil2100: oh right, I didn't have the time to workaround this
[14:56] <sil2100> didrocks: since I see indicators is blocking on arm64 right now
[14:56] <sil2100> I'll skip it for now
[14:57] <didrocks> sil2100: yeah, please skip :)
[14:57] <didrocks> remind me tomorrow about it
[14:57] <sil2100> Sure :)
[14:58] <asac> bfiller: awesome... letrs fix it!!
[14:58] <asac> what do you need to fix it?
[14:58] <asac> any poneys?
[14:58] <bfiller> asac: think that's a question for the mir/autopilot guys :) not a problem in the apps or their tests
[14:58] <bfiller> at least not for those failures
[14:58] <bfiller> something in the input stack maybe?
[15:03] <bfiller> asac, fginther : can we turn auto merge back on for messaging-app and webbrowser-app?  all of messaging-app failures due to this bug and most of browser's due to this bug and https://bugs.launchpad.net/webbrowser-app/+bug/1237472
[15:04] <bfiller> we have a bunch of MR's that need to land in each
[15:05] <asac> well, i expect that app developers are looking in the stuff up and down
[15:05] <asac> so i hoped they could just go there and fix it
[15:05] <asac> if that doesnt work then we can wait
[15:05] <asac> didrocks: so lets take the powerd bandaid by ricmm
[15:05] <fginther> bfiller, at the moment nothing is running correctly on mako in upstream merger, appears to be an issue with unlocking the screen
[15:06] <fginther> bfiller, I know that doesn't answer your queston :-(
[15:06] <asac> bfiller: they dont pass the tests
[15:06] <bfiller> fginther: haha, just tell me you'll enable them :)
[15:06] <asac> bfiller: if you dont want tests, you can directly push to trunk
[15:07] <asac> but we cant land stuff easily anyway
[15:07] <bfiller> asac: we can?
[15:07] <asac> wello, you can whatever you want. i dont recommend it
[15:07] <asac> if the apps thejn fail APs at the staging state we will not land them
[15:07] <asac> bfiller: wait till the tests are fixed and help getting them fixed
[15:07] <asac> thats the best way i swear
[15:08] <bfiller> asac: we're trying to help fix them, believe me. but we have real app critical bugs that need to be fixed as well
[15:08] <asac> bfiller: make MP ready, discuss those with us individually then
[15:08] <asac> bfiller: the upstream merger will not succeed
[15:08] <asac> it will always fail
[15:08] <asac> so it doesnt help you
[15:08] <bfiller> ok
[15:08] <asac> you will jsut retry till forever or force it into the trunk
[15:10] <sil2100> brb, modem restart
[15:18] <asac> didrocks: can you work ricmm
[15:18] <asac> powerd bandaid into the landing plan?
[15:18] <asac> it will allow unity8 AP to run
[15:18] <didrocks> asac: yeah, I read it, still on the HO with lool first
[15:18] <asac> with failures, but at least we will see it
[15:18] <didrocks> (and checking why britney isn't running)
[15:18] <asac> didrocks: ok sorry.
[15:20] <didrocks> no worry
[15:22] <cjwatson> sorted
[15:24] <didrocks> thanks cjwatson
[15:25] <didrocks> ricmm: ok, ready now
[15:25] <didrocks> ricmm: so, do you have your powerd package handy?
[15:26] <didrocks> let's get that in the incoming image
[15:26] <lool> Saviq: asac told me you knew about it because it was alreayd there in the past  :-)
[15:27] <lool> Saviq: so you pull down home scope, and while it's slowly getting up (elastically?) you swipe left/right
[15:27] <lool> Saviq: than there are visual glitches in the scope
[15:27] <asac> Saviq: it is the same issue that we had 2-3 month ago while i was still in miami :)
[15:27] <asac> Saviq: e.g. pull the screen up or down beyond and while it bounces back move it to the next homescfreen
[15:27] <asac> if you go back its corrupted
[15:28] <asac> like elements floating over each other etc.
[15:28] <ogra_> asac, heh, still busy with your pet bug ?
[15:28]  * ogra_ can confirm it btw 
[15:29] <asac> its not my pet bug :)
[15:29] <asac> it just came up today as being annoybing and folks couldnt reproduce it
[15:29] <asac> so i showed one way how :)
[15:29]  * didrocks still thinks we have bigger issues today :p
[15:30] <ogra_> we have issues  ?
[15:30] <didrocks> asac: do you know where ricmm's code is?
[15:30] <asac> didrocks: ask him
[15:30] <didrocks> ogra_: I heard of an ungreen dashboard :p
[15:30] <asac> ricmm: where is your bandaid code?
[15:30] <ogra_> didrocks, that can be easily fixed
[15:30] <ricmm> https://code.launchpad.net/~ricmm/powerd/suspend-if-mir-alive/+merge/190173
[15:30] <cjwatson> final: bip,gccxml,glew,kubuntu-debug-installer,kubuntu-firefox-installer,kubuntu-patched-l10n,libisoburn,libpwquality,pnm2ppa,ubuntu-touch-meta,x11-apps,x11-session-utils,x11-xfs-utils,xinetd,xorg,zsh
[15:30] <ogra_> using CSS
[15:30] <didrocks> asac: what I did here several minutes ago, trying to speed this up while he's away ;)
[15:30] <cjwatson> (that'll need another publisher run of course)
[15:31] <asac> didrocks: https://code.launchpad.net/~ricmm/powerd/suspend-if-mir-alive ? maybe?
[15:31] <asac> hmm.
[15:31] <asac> seems thats an old one
[15:31] <didrocks> asac: we have the link now :)
[15:31] <asac> oh its not merged
[15:31] <asac> didrocks: good
[15:31] <didrocks> ricmm: nobody reviewed/tested?
[15:31] <asac> i installed it
[15:31] <ogra_> see #phablet
[15:31] <asac> and it fixes unity8 AP
[15:32] <ogra_> it was tested over there
[15:32] <asac> err fixes that it runs
[15:32] <asac> not suceeds
[15:32] <didrocks> ricmm: mind pushing that to trunk so that we win some cycles?
[15:32] <didrocks> ricmm: I approved it logically
[15:32] <didrocks> then, let's handle a build with it
[15:33] <didrocks> asac: it's an improvment
[15:33] <Saviq> asac, lool, can we have a bug pleae?
[15:34] <ricmm> didrocks: can you do that for me please im really neck deep in Mir code right now
[15:34] <didrocks> ricmm: sure, doing then
[15:35] <lool> Saviq: not my discovery, happy to file on
[15:35] <lool> Saviq: (could you reproduce?
[15:35] <asac> Saviq: for what?
[15:35] <asac> Saviq: you can file bugs on your own. we test and tell you. and we constantly see it on dashboard
[15:36] <asac> if we feel the ball gets dropped with use bugs for escalation
[15:36] <didrocks> asac: powerd fix in trunk and preparing in the ppa
[15:36] <asac> nice
[15:36] <asac> Saviq: i dont even know what you want a bug about
[15:36] <asac> still no luck on webbrowser?
[15:36] <asac> or unity8 having test failures
[15:37] <lool> Saviq: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1238094
[15:37] <lool> asac: ^
[15:37] <asac> ahj that one
[15:37] <asac> well there a bug makes sense
[15:37] <asac> jfunk should have this on his list i think
[15:51] <sil2100> didrocks: I still see u-s-c in -proposed :|
[15:51] <didrocks> sil2100: autopkgtest for deja-dup 27.3.1-0ubuntu1: RUNNING (Jenkins: public, private)
[15:51] <didrocks> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libunity
[15:51] <sil2100> Ah, autopkgtest I see
[15:51] <didrocks> did you look at this?
[15:52] <sil2100> Yes, looked at this, but still makes me wonder why it takes so long!
[15:52] <plars> asac, Saviq: http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/91:20131010.1:20131010/4658/unity8-autopilot/ was the best run I could get with unit8
[15:53] <Saviq> plars, whoa!
[15:53] <asac> didrocks: do you know where landing 174 is currently?
[15:53] <Saviq> plars, that's better than expected!
[15:53] <didrocks> sil2100: backlogging? britney was done
[15:53] <asac> didrocks: is that inflight or inarchive and do we plan to take it?
[15:53] <plars> Saviq: yeah, I've seen it pass a lower amount also
[15:54] <didrocks> asac: I didn't get ping about it, I think it's pending next image, lool didn't get positive results this morning about it
[15:54] <asac> plars: yeah. but doesnt unity normally hav more tests?
[15:54] <didrocks> asac: also, not merged to trunk yet
[15:54] <asac> didrocks: can we put it to WAITING FOR CODE or something?
[15:54] <didrocks> asac: done already
[15:54] <asac> INFLIGHT previously meant someone is working on landing it :)
[15:54] <asac> ah cool
[15:55] <plars> asac: I don't think so
[15:55] <asac> indeed
[15:55] <asac> nice one
[15:56] <plars> asac: I'm going to retry webbrowser in ci - running locally with doanac's change to turn the display on earlier I'm getting a pass on webbrowser
[15:57] <asac> plars: turn display on is also missing?
[15:57] <didrocks> powerd in UNAPPROVED
[15:58] <asac> Saviq: how can we ensure that the display is on? can we add that in autopilot?
[15:58] <didrocks> (well, in 2 minutes)
[15:58] <plars> asac: it was normally turned on in the unlock code, but we think that was happening too late and sometimes failing
[15:58] <asac> plars: can you try the two hacks with other autopilots?
[15:58] <asac> plars: maybe loads now go green?
[15:58] <Saviq> asac, I thought was possible through powerd-cli ?
[15:58] <plars> asac: which two hacks are you talking about?
[15:58] <ogra_> hmm, lool i think we should land the mallit stop on fix too, it produces crash files for me on shutdwon without it
[15:58] <asac> plars: i cant see a pass though with powerd stopped and the screen is surely on while i start the test
[15:59] <asac> plars: powerd hack and screen on
[15:59] <asac> Saviq: yeah, but can you call that from the test?
[15:59] <lool> didrocks: I'm positive about the change, but it wasn't affecting maliit
[15:59] <asac> Saviq: its aweful to add that to utah, because then people will debate and not be able to reproduce exactly what is done
[15:59] <asac> awful
[16:00] <plars> asac: let me finish trying webbrowser in the lab on mako with the display on code moved up, iirc we discussed earlier that that's really all that should be needed
[16:00] <plars> asac: and that seems to be doing well for me when I tried locally
[16:00] <asac> plars: right
[16:00] <asac> plars: go fo rthat and run a few other apps as well that fail
[16:00] <plars> asac: if that works, and if there's enough time before the next build, sure we can kick off the whole thing again and see what happens
[16:00] <Saviq> asac, no idea
[16:00] <lool> I can not type an SMS in messaging-app anymore
[16:00] <asac> plars: those that regreessed and were stable before
[16:01] <Saviq> asac, if I can call powerd to turn display on, sure - but as lool mentioned it sometimes happens during long boot
[16:01] <Saviq> asac, so we really just need to fix the underlying bug
[16:01] <asac> plars: i think we have a couple hours to play with this
[16:01] <lool> Saviq: there is a fix in powerd in the pipe to do the right thing?
[16:01] <asac> Saviq: but whats the underlying bug? I think i haven't heard what the real, real fix would be
[16:01] <Saviq> lool, asac, in that case we don't need to do anything
[16:01] <sil2100> didrocks: meeting? ;)
[16:02] <lool> Saviq: maybe try it out
[16:02] <lool> Saviq: it's in PPA I think
[16:02] <asac> lool: i dont knoow this addresses that
[16:02] <lool> Saviq: powerd build
[16:02] <Saviq> lool, I'm trying out 50 things at any given time...
[16:02] <asac> ricmm: does your powerd also help for cases where the screen needs to be forced on etc.?
[16:02] <lool> Saviq: and you complain about a 2% difference in the number of things you're trying!  :-)
[16:02] <Saviq> yes!
[16:02] <asac> lool: afaiui the powerd fix just ensures that we can start unity8-autopilots after we kill unity
[16:05] <lool> asac: joining?
[16:06] <asac> why not :)
[16:12] <ricmm> asac: the powerd MR just makes powerd *prevent* suspend if the display server is unavailable
[16:12] <ricmm> for the Mir case
[16:17] <ogra_> https://code.launchpad.net/~mterry/session-manager-touch/socket/+merge/186391
[16:24] <lool> ogra_: I commented on the branch
[16:24] <ogra_> thx
[16:25] <lool> == Building platform-api (platform stack) ==
[16:25] <lool> ogra_: It's kind of great and sad that mterry was already preparing a fix to not use /tmp!
[16:26] <lool> too bad we dropped the ball there
[16:26] <ogra_> yeah
[16:26] <ogra_> should we upload the second half of the maliit fix ?
[16:26] <ogra_> so it goes into thei image too
[16:26] <ogra_> *this
[16:36] <kenvandine> asac, i just added an item to the landing asks sheet for bugs fixes related to online accounts... but none of it can be tested on Mir images because signon-ui doesn't work on Mir yet, greyback is looking at that
[16:37] <kenvandine> asac, but i'd rather not wait to land these, they've been tested thoroughly on SF and the packages in the current image don't work either because of the same Mir issue
[16:42] <alecu> didrocks: was "unity-lens-application" removed from 92, when adding the new scope?
[16:42] <didrocks> alecu: yeah, I didn't dive into the detail, but that was handled
[16:42] <alecu> great
[16:42] <didrocks> so no duplicate :)
[16:42] <didrocks> (normally :p)
[16:46] <ogra_> didrocks, hand is on the trigger, should i shoot ?
[16:46] <didrocks> ogra_: please do!
[16:47]  * ogra_ pulls the index finger
[16:47] <ogra_> *BOOM*
[16:47] <rsalveti> lool: adding another land request for ofono, bugfixes
[16:47] <ogra_> (building)
[16:47] <rsalveti> lool: multimedia is still not ready to go, blocked by a bug on mako
[16:47] <didrocks> sil2100: FYI, so landing 179 and 180
[16:48] <fginther> didrocks, I think I'm missing something. I'm looking here for pending merge-backs but don't see any: https://code.launchpad.net/~ps-jenkins
[16:50] <didrocks> fginther: unity8 at least should have one?
[16:52] <fginther> didrocks, there was one merged 8 hours ago, should there be a newer one?
[16:52] <asac> kenvandine: sounds like not ready :)
[16:52] <didrocks> fginther: oh, if it was merged, my bad then; well, good then! :)
[16:53] <asac> thx! once the rest is there we can tackle it
[16:53] <asac> kenvandine: we might also take it after we go out of special mir-only fix mode
[16:53] <asac> hopefully tomorrow
[16:53] <asac> but better get the complete thing in so you can tell us what to expect and we can avoid bad landings that dont work
[16:53] <kenvandine> asac, i'm mostly worried about the fixes in signon-ui and the archive freezing
[16:54] <kenvandine> asac, since it's in the desktop too
[16:54] <ogra_> didrocks, "unity-scope-click transition (currently moving to the release pocket)  to handle debs and click packages "
[16:54] <ogra_> didrocks, debs ?
[16:54] <kenvandine> the rest is touch only
[16:54] <asac> kenvandine: when is it freezing?
[16:54] <kenvandine> tonight
[16:54] <didrocks> ogra_: yeah, the click scope is handling debs file
[16:54] <didrocks> ogra_: fine :p
[16:54] <ogra_> ugh
[16:54] <didrocks> and fun
[16:54] <asac> i dont think that should mipact our ability to land stuff properly
[16:54] <asac> kenvandine: we have to try get a FE then
[16:54] <asac> you might want to start doing that :)
[16:54] <asac> or check with folks before
[16:54] <asac> maybe they give you a day :)
[16:55] <asac> (without paperwork)
[16:55] <kenvandine> asac, you know how things are with respins
[16:55] <didrocks> ok, will be back a little bit before 10pm
[16:55] <kenvandine> landing it will cause respin and extra work for iso testing
[16:55] <kenvandine> i hate doing that to folks
[16:55] <asac> kenvandine: i dont anticipate that there will be no respin
[16:55] <asac> kenvandine: also we could upload it to saucy-updates if you dont need it on the desktop image
[16:55] <kenvandine> asac, basically i saying it doesn't make things any worse than it is... it's completely broken now
[16:56] <kenvandine> asac, ok, lets hope greyback makes some progress quickly :)
[16:56] <asac> no pressure :)
[16:56] <asac> lol
[16:56] <kenvandine> hehe
[16:56] <asac> tell him the deadline
[16:56] <asac> that will help
[16:56] <asac> !!
[16:56] <asac> at least he might defer his dinner
[16:57] <kenvandine> greyback, ^^ that signon-ui problem on Mir is blocking a bunch of fixes :)
[16:57] <kenvandine> greyback, any leads yet?
[16:58] <asac> lets hope greyback isnt working on a critical mir crash :)
[16:59] <greyback> kenvandine: I'm working on something else right now, but this is a workaround for unity-mir you could try: http://pastebin.ubuntu.com/6218843/
[17:00] <greyback> I'm working on something else right now, so that's all I can contribute at the moment
[17:00] <kenvandine> greyback, ok, i'll give it a try
[17:01] <greyback> kenvandine: the correct fix is much more invasive, so that workaround might have to do until >1.0
[17:01] <greyback> .../probably/ much more...
[17:02] <greyback> and I suspect that workaround has bad consequences
[17:02] <lool> asac: do we promote #91?
[17:03] <asac> lool: not sure
[17:03] <asac> lool: is it strictly better? i guess given the dashboard we need QA input
[17:03] <asac> jfunk: can you assess if 91 is strictly better (in some terms :)) on manual testing side yet?
[17:03] <asac> than #90
[17:04] <asac> plars: did you rerun webbrowser with the "hacks"?
[17:04] <asac> its still at 7.7% ... just wondering
[17:04]  * asac guesses he is still prepping things for this trial
[17:04] <plars> asac: yes - on mako it all passes, not on maguro
[17:05] <asac> ok so waiting for dashboard propagation?
[17:05] <plars> asac: you probably missed the message when I was going out of the landing call
[17:05] <asac> yeah
[17:05] <asac> i dropped out also pretty quick
[17:05] <lool> asac: it's IMO strictly better
[17:06] <lool> asac: ping Oliver and Alan to confirm if you want to promote
[17:06] <asac> right. i believe the best team to say not-imo is QA :). lets see if they can give us more unbiased data
[17:06] <plars> asac: no, they are on the dashboard
[17:06] <asac> lool: that might also work
[17:06] <asac> but... :)
[17:06] <asac> i think we are at a point where we want more organized sign offs
[17:06] <asac> plars: oh i see now
[17:06] <asac> lool: lets check in #qa etc. if anyone is around
[17:07] <lool> plars: Could you drive the ubuntu-keyboard testsuites from veebers into landing and add them to the dashboard?
[17:07] <lool> plars: or would you expect he knows how to do it?
[17:07] <lool> plars: Oh you didn't get it
[17:07] <lool> plars: fwding
[17:08] <plars> lool: I haven't had a chance to take a look yet, but I saw the mail and the merge proposal, I think it was just waiting on review signoff which I can't do
[17:08] <lool> plars: sent
[17:08] <asac> plars: who can do?
[17:09] <asac> is there anyone != new zealand?
[17:10] <Mirv> if someone suddenly has sudden outbreak of free time (yeah, right) and knows how to launch an app from command line under mir, please update bug https://launchpad.net/bugs/1238031 so that me and bzoltan have something to start from in the morning for the SDK
[17:11] <plars> asac: I can change the tests locally and give it a try for me, but I can't topapprove the patch so that it lands
[17:11] <plars> asac: it doesn't give me an option
[17:12] <plars> asac: someone needed from phablet team I would guess
[17:14] <seb128> sil2100, still around?
[17:17] <seb128> lool, asac: are landing still happening by "stack"? or do we have more granularity?
[17:17] <seb128> e.g indicators, can we land one alone?
[17:17] <asac> sergiusens: plars might need you rhelp
[17:17] <asac> sergiusens: we can land stuff alone if it is technically possible (e.g. can be copied in theory alone)
[17:17] <asac> seb128: ^^
[17:17] <lool> seb128: per source package is possible
[17:18] <thostr_1> sil2100: could you fasttrack https://code.launchpad.net/~indicator-applet-developers/hud/fix-window-stack-crash/+merge/190401
[17:18]  * lool  is  off &
[17:18] <seb128> can we land indicator-keyboard (desktop only)?
[17:18] <thostr_1> sil2100: this is hud crash fix
[17:18] <ogra_> lool, sleep well !
[17:18] <seb128> there is a fix important for saucy desktop in there
[17:18] <ogra_> and dont dare to show up here tonight !
[17:18] <seb128> cyphermox, sil2100, ^ can you get indicator-keyboard landed?
[17:19] <rsalveti> lool: have a good and long night of sleep :-)
[17:19] <lool> thanks
[17:20] <sergiusens> asac, plars help on what?
[17:23] <plars> asac: getting an MP pushed through - https://code.launchpad.net/~veebers/ubuntu-keyboard/update_autopilot_emulators/+merge/190319
[17:26] <asac> sergiusens: what plars says
[17:27] <ogra_> [17:27] <ogra_> (on cdimage ... give system-image a few to pick it up)
[17:29] <sergiusens> asac, plars can you add a mr vote saying that you tested at least?
[17:29] <cyphermox> seb128: sure.
[17:30] <cyphermox> lool: ^ so I'll push the buttons to land indicator-keyboard
[17:30] <plars> sergiusens: I'm just about to give it a try here
[17:31] <seb128> cyphermox, he's off for the evening, but that indicator is not on touch so I doubt they care
[17:32] <cyphermox> ah, good point
[17:32] <ogra_> yeah, fight with the release team over it :)
[17:33] <cyphermox> seb128: 0.0.0+13.10.20131010.1-0ubuntu1 ?
[17:34] <seb128> cyphermox, correct!
[17:34] <cyphermox> alright. we have the go from release team? :)
[17:36] <seb128> cyphermox, well, it's a bug fix, I'm going to nag them for review once it's the queue
[17:36] <seb128> but it's an important fix and it's a trivial change
[17:36] <cyphermox> ok
[17:37] <asac> lool: so i got at least one confirm from QA that 91 is good
[17:37] <asac> ogra_: popey: wanna check if things are bgetter than 90?
[17:37] <asac> and then release?
[17:37] <asac> plars: anything from dashboard that isnt copmlete etc.?
[17:37] <ogra_> asac, so since we only have half the maliit fix in (it will still crash on shutdown) should i upload the second half so we have it in tomorrows image ?
[17:37] <asac> i dont know
[17:38] <asac> i think thats untested as well
[17:38] <asac> so might be still only half
[17:38] <ogra_> well do you want to see .crash files after reboots or not ? :)
[17:38] <ogra_> it was tested by loic and me
[17:38] <plars> asac: there are some things that could use rerunning, but we are about to get another image right?
[17:38] <asac> i dont want to see them, but i dont want to see other stuff
[17:38] <ogra_> (i'm still running it here)
[17:38] <asac> ogra_: which landing entry missed the half?
[17:38] <ogra_> and it was actually introduced by a merge failure
[17:38] <ogra_> asac, maliit.conf has two "stop on" stanzas
[17:39]  * ogra_ looks for the MP
[17:40] <ogra_> asac, trivial but very effective ... https://code.launchpad.net/~lool/session-manager-touch/drop-duplicate-stop/+merge/190373
[17:40] <ogra_> (upstart defaults to use the second one which means maliit stays up after unity is gone and falls over)
[17:41]  * ogra_ would like to have that in, will definitely prevent .crash files on the dashboard
[17:42] <balloons> could I get an account on https://jenkins.qa.ubuntu.com? fginther perhaps you have the power?
[17:42]  * cyphermox -> lunch
[17:43] <ogra_> asac, the first half is landing 177
[17:43] <plars> balloons: not many people do - it would have to be an IS thing most likely
[17:43] <ogra_> asac, it fixes the crashes on startup ..
[17:43] <ogra_> but not the shutdown ones
[17:43] <plars> balloons: if you need something removed or changed though, your best bet it to talk to retoaded or rfowler
[17:43] <seb128> ogra_, asac, fginther: what's the plan to land indicator fixes to the touch image after saucy is hard frozen tonight? (since those are shared sources between desktop and touch)?
[17:44] <seb128> ogra_, asac, fginther: do we plan to land updates as SRUs and build the touch image for -updates or something?
[17:44] <ogra_> seb128, i suspect we need to obey to the release team for these
[17:44] <balloons> plars, yea I kind of figured I was getting into some big fish
[17:44] <ogra_> seb128, no
[17:44] <seb128> :-(
[17:44] <seb128> so basically "we are screwed"?
[17:44] <popey> asac: ogra_ want me to test 91?
[17:45] <ogra_> popey, yes
[17:45] <popey> kk
[17:45] <balloons> popey, are you running -proposed always or no?
[17:45] <popey> balloons: i have more than one device, so yes. and no.
[17:45] <balloons> haha, well said
[17:49] <popey> error: device not found
[17:49] <popey> ERROR:phablet-flash:Command 'adb reboot bootloader' returned non-zero exit status 1
[17:49] <popey> ☹
[17:49] <sergiusens> popey, don't overheat them
[17:50] <sergiusens> popey, where were you on that device when that happened?
[17:50] <sergiusens> popey, recovery?
[17:50] <popey> ubuntu
[17:50] <popey> cpu on the device isnt busy
[17:51] <popey> adb is running
[17:51] <popey> doesn't show up at all
[17:52] <sergiusens> popey, dmesg?
[17:53] <plars> asac, bfiller_afk, sergiusens: well, with the patch at https://code.launchpad.net/~veebers/ubuntu-keyboard/update_autopilot_emulators/+merge/190319 the keyboard tests run ok for me but I get 5 failures (2 passes)
[17:53] <popey> sergiusens: http://paste.ubuntu.com/6219033/
[17:53] <plars> bfiller_afk: is that consistent with what you would expect to see?
[17:56] <sergiusens> popey, from a quick look 90% of those messages are related to your cable/socket
[17:57] <popey> i moved the phone to a different usb port to test
[17:59] <popey> sergiusens: other phone shows up okay
[17:59]  * popey reboots
[17:59] <sergiusens> popey, can you reboot it?
[17:59] <popey> ☻
[18:01] <popey> fine now
[18:19] <lool> cyphermox: <3
[18:19] <lool> ogra_: \o/
[18:19] <popey> in #91 the OSK disappeared when typing the 2fa in U1 and now I can't get it back in any app
[18:20] <ogra_> lool, go away !!! we'll send handcuffs to your wife  so she can tie you up somewhere !!
[18:20] <popey> Where do I sign up for that service?
[18:20] <bfiller> plars: they all passed under SF, haven't tried them on mir
[18:20]  * ogra_ puts on a serious face and points to lool's bed
[18:20] <plars> bfiller: let me try with sf
[18:20] <lool> ogra_: yup
[18:21] <popey> asac: ^^
[18:21] <lool> ogra_: just before I do, did you have a bug for dialer-app doesn't come to front when in a call?
[18:21] <ogra_> popey, just work a few nights in a row and dont stop to work even tough you said you'd do ...
[18:21] <lool> had good dinner and about to watch Borgen and have a good night of sleep  :-)
[18:21] <ogra_> popey, you are into that handcuff thing, eh ?
[18:21] <popey> newp
[18:22] <popey> just thinking I could put the handcuffs on the wife and then come back down here and hack
[18:22]  * ogra_ hugs lool ... enjoy 
[18:22] <popey> system settings wont respond now, all gone white
[18:22]  * popey kills it and restart
[18:23] <popey> yeah, OSK aint coming back.
[18:23]  * popey reboots
[18:25] <plars> bfiller, asac: yeah, they all pass with sf - let me retry with this latest build though
[18:26] <popey> asac: also getting random characters appearing in fields.. had `` in one field and a øø in another
[18:27] <ogra_> popey, yeah, thats there since a while
[18:28] <popey> k
[18:28] <ogra_> try and press the power button when in terminal app ... thats also funny
[18:28] <popey> oh that's always been there
[18:29] <ogra_> really ? i only noticed it recently
[18:29] <popey> heh
[18:29] <asac> popey: are those regressions?
[18:29] <asac> or noise?
[18:29] <popey> noise i think
[18:30] <ogra_> asac, the two chars if you focus a text input field are relatively new
[18:30] <asac> ogra_: relatively is a relative term
[18:30] <asac> :)
[18:30] <ogra_> but not critical
[18:30] <popey> not consistent either
[18:30] <kgunn> asac: since lool is rightly taking the night off....who can kick a ci/merge on unity8 for this https://code.launchpad.net/~nick-dedekind/indicator-network/simunlock.dialog/+merge/185810
[18:30] <asac> ogra_: can you be more specific since when we see this?
[18:30] <ogra_> i think i noticed it for the first time about a week ago
[18:30] <kgunn> asac: thats for sim pin unlock
[18:30] <asac> for instance: before or after mi?
[18:30] <ogra_> before
[18:30] <asac> kgunn: that we pick up tomorrow
[18:31] <kgunn> asac: ok. so do we just manual merge on our own ?
[18:31] <ogra_> it dumps one or two chars in the text field ... you can just use backspace
[18:31] <ogra_> not release critical ... just ugly
[18:31] <asac> kgunn: no levave it as is at best so we can somehow asess and test before landing if needed
[18:31] <ogra_> oh, but it might affect tests ... hmm
[18:31] <asac> and kick off a CI job if possible
[18:31] <kgunn> asac: we've already tested it on a device with a locked sim, its been doubly reviewed
[18:32] <asac> right. not saying its not safe
[18:32] <asac> kgunn: right. thats fine. but we need to really look closely at best and might use CI for the landing manually etc.
[18:33] <kgunn> asac: when does this happen ?
[18:33] <lool> kgunn: autolanding is running on this branch already!
[18:33] <asac> tomorrow morning euro time we will look
[18:33] <asac> is it?
[18:33] <asac> then its autolanding :)
[18:33] <asac> hehe
[18:33] <kgunn> lool: woohoo
[18:33] <ogra_> asac, some phones ahve SIMs in the lab ... we need to make sure they are PIN free
[18:33] <lool> ogra_: so you didn't have a bug?
[18:33] <asac> kgunn: well its because you dont have tests
[18:33] <lool> ogra_: will just log one now thne
[18:33] <ogra_> else that might interfere
[18:33] <ogra_> lool, !
[18:33] <asac> so you are going unprotectd anyway, so it doesnt help to turn your jobs off
[18:33] <kgunn> ....didn't match the list in the ginther mail
[18:33] <ogra_> go to bed
[18:34] <asac> kgunn: the reply included only those that are not getting enabled
[18:34] <lool> yup, off now
[18:34] <asac> thats just two handfull or so
[18:34] <asac> if you are not in there its autolanding
[18:34] <tyhicks> Hello! I have one more dbus upload, which fixes the desktop autopilot tests, that I'd like to land
[18:34] <tyhicks> the debdiff is small (once you look past the quilt refresh churn): http://people.canonical.com/~tyhicks/fixes/dbus/source/dbus_1.6.12-0ubuntu10.debdiff
[18:35] <tyhicks> and I've done extensive manual tests on it: http://paste.ubuntu.com/6219140/
[18:35] <tyhicks> I'm in the process of running a slew of automated tests against it with QRT's test-dbus.py
[18:36] <lool> (added a landing for the sim unlock fix with link to mp. off now)
[18:37] <tyhicks> The lowlevel details are that it, along with a recent lxc upload by stgraber, fixes dbus-daemon inside of an LXC container breakage when /sys/kernel/security/apparmor/ is mounted inside the container
[18:39] <sil2100> Back from shopping
[18:40] <sil2100> lool: should I release HUD?
[18:40] <sil2100> (after testing)
[18:42] <tyhicks> the automated tests in QRT's test-dbus.py passed, so it is safe to say that the code is ready for the dbus upload
[18:46] <tyhicks> lool: when you get a moment, can you give me an ack/nack on the dbus upload?
[18:47] <ogra_> tyhicks, he isnt around (or shouldnt be) asac is the one giving acks/macks tonight
[18:47] <ogra_> *nacks
[18:47] <tyhicks> thanks
[18:48] <tyhicks> asac: Can I get an ack/nack from you on the dbus upload mentioned above?
[18:50] <sil2100> asac: ^
[18:50] <tyhicks> I wrote the kernel code that populates /sys/kernel/security/apparmor/features/dbus/mask, jjohansen (AppArmor kernel maintainer) agreed that this is the right thing to do in dbus-daemon, and jdstrand will be sponsoring the upload
[18:50] <tyhicks> so all of the right people are involved in this change
[18:54] <jdstrand> fyi, I added a landing ask just now
[18:55] <tyhicks> jdstrand: thanks! test-dbus.py passed so you can update column G if you'd like
[18:56] <jdstrand> done
[18:56] <jdstrand> tyhicks: thanks! :)
[19:01] <asac> tyhicks: tyhicks why do you have all those null op changes in the diff?
[19:01]  * asac guesses they didnt apply anymore
[19:01] <tyhicks> asac: I changed a patch that was 3 patches down in the series file
[19:02] <tyhicks> asac: I'm trying to keep all of the apparmor mediation patches in an upstreamable form
[19:02] <tyhicks> asac: so changing that patch meant refreshing the two on top of it
[19:02] <tyhicks> sorry for the ugliness, but I think it is for the best
[19:03] <asac> yeah dont worry, just for manual review its better without refresh
[19:03] <tyhicks> agree, but then the two patches above had line offset warnings
[19:03] <asac> ogra_: so this goes into the android container right?
[19:03] <ogra_> dbus ?
[19:03] <ogra_> no
[19:04] <asac> err
[19:04] <asac> its talking about lxc container in the comment
[19:04] <asac> so wonder if it might impact our side there
[19:04] <ogra_> oh
[19:04] <asac> ogra_: e.g. do we start an lxc container?
[19:04] <asac> :)
[19:04] <ogra_> yes, but not using the standard lxc startup stuff
[19:05] <ogra_> we use the lxc-start command with a preconfigured setup ...
[19:05] <ogra_> tyhicks, jdstrand, can that affect our container ? did someone test on a phone
[19:05] <jdstrand> note this change only affects dbus-daemon
[19:05] <asac> we have dbus-daemon on the phone, rigth?
[19:06] <ogra_> "dbus-daemon, running inside of an LXC container"
[19:06] <jdstrand> yes, but you don't run dbus-daemon in the container, do you?
[19:06] <ogra_> wont affect us
[19:06]  * asac checked and its running a few times
[19:06] <asac> well, just think out loud. ultiamtely checking what impact it might have or not have
[19:06] <ogra_> not in the container
[19:06] <asac> do we have this mask file on our phones?
[19:06] <ogra_> right, the lxc bit should be fine
[19:07] <jdstrand> the change should affect the phone the same as the desktop
[19:07] <asac> ls -la /sys/kernel/security/apparmor/features/dbus/mask
[19:07] <asac> -r--r--r-- 1 root root 0 Jan  1  1970 /sys/kernel/security/apparmor/features/dbus/mask
[19:08] <tyhicks> so instead of stat()'ing /sys/kernel/security/apparmor/features/dbus, we're open()'ing /sys/kernel/security/apparmor/features/dbus/mask
[19:08] <asac> yes i am seeing that
[19:08] <asac> the file seem to exist at least :)
[19:08] <tyhicks> apparmor doesn't mediate stat(), but it mediates open()
[19:08] <jdstrand> /sys/kernel/security/apparmor/features/dbus/mask is part of the apparmor kernel backports in all our touch kernels
[19:09] <tyhicks> dbus-daemon doesn't run confined on the phone or on the desktop, so it will still be able to open() the mask file without any problems
[19:09] <ogra_> right, looks safe to me overall
[19:09] <asac> yeah. i feel its as safe as it can be from reading the code, but as everything we want to see it run on the phone :)
[19:10] <asac> if we pump it in now and tomorrow we have a busted image we loose like 12 hours or so :)
[19:10] <asac> which is probably like 20% of the time left :)
[19:10] <ogra_> asac, and it will be hard to roll back
[19:10] <ogra_> dbus is a package that falls under final freeze
[19:11] <jdstrand> it is
[19:11] <jdstrand> this issue only came to our attention this morning
[19:11] <jdstrand> but the change is stat to open
[19:11] <asac> yeah. if we knew earlier we could have worked in the plan
[19:11] <jdstrand> I started an armhf local compile, but I doubt it'll finish in time
[19:12] <asac> so if we do this i also have to get kenvandine's stuff in
[19:12] <jdstrand> tyhicks: you could toss it in ubuntu-security-proposed
[19:12] <asac> he has the very same argument
[19:12] <sil2100> asac: if testing HUD proves OK, can I release?
[19:12] <tyhicks> jdstrand: will that build an armhf deb?
[19:12] <asac> please now without notice and testing because we have final freeze in a couple minutes
[19:13] <asac> sil2100: HUD is in the plan right?
[19:13] <jdstrand> tyhicks: I hope so-- it is one of our native ppas :)
[19:13] <tyhicks> ok
[19:13] <jdstrand> tyhicks: "yes"
[19:13] <asac> ogra_: what is the latest image we produced?
[19:13] <sil2100> asac: it's mentioned in the Summary e-mail, yes
[19:13] <ogra_> asac, 92
[19:13] <asac> ogra_: btw, #92 still has malit crashes
[19:13] <asac> all the time
[19:13] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/92:20131010.2:20131010/4662/
[19:13] <ogra_> asac, i told you
[19:14] <asac> ogra_: didnt this image pick up the powerd package?
[19:14] <ogra_> it crashes on shutdown without the fix
[19:14] <asac> powerd from 0.13+13.10.20131009-0ubuntu1 to 0.13+13.10.20131010-0ubuntu1
[19:14] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20131010.2.changes
[19:14] <ogra_> yeah
[19:14] <ogra_> its in
[19:14] <asac> plars: can you retry unity8?
[19:14] <asac> plars: that should have worked now with the powerd fixes by ricmm
[19:15] <asac> ricmm: ^^ ... this is the log https://jenkins.qa.ubuntu.com/job/saucy-touch_mir-mako-smoke-unity8-autopilot/15/console
[19:15] <asac> e.g. after powerd we still see not running unity test
[19:15] <asac> plars: doanac: lets check on that... also check how we really run this unity8 testsuite
[19:15] <asac> e.g. which commands to run
[19:17] <asac> kenvandine: where is your debdiff?
[19:18] <asac> kenvandine: you could have linked the important things like code/merges/etc. in the landing ask :)
[19:19]  * ricmm installs unity8-autopilot
[19:19] <ogra_> let it fly
[19:19] <ogra_> ...
[19:20] <ricmm> lol
[19:20] <plars> asac: I am, the job timed out
[19:21] <kenvandine> asac, it's 3 packages, all in trunk already
[19:23] <plars> sergiusens: ok, I approved https://code.launchpad.net/~veebers/ubuntu-keyboard/update_autopilot_emulators/+merge/190319 and got the autolanding job to pass
[19:23] <plars> asac: ^ sergiusens: I see failures with the tests under mir that I don't see with SF, but the point of the patch was to make the tests run at all - which it does
[19:25] <ricmm> give me a concrete failure
[19:25] <ricmm> I dont want to read through a thousand line log
[19:25] <ricmm> with results I dont necesarily understand
[19:25] <ricmm> plars: which one is the weirdest in your opinion?
[19:27] <sergiusens> ogra_, landing please https://code.launchpad.net/~sergiusens/ubuntu-seeds/share-app--/+merge/190452
[19:27] <sergiusens> depends on old hud that needs to be removed from the images
[19:27] <sergiusens> ogra_, description has more ;-)
[19:27] <sil2100> asac: any objections for getting HUD in ;) ?
[19:28] <sil2100> It doesn't seem to crash for now!
[19:28] <plars> ricmm: well, I'm actually somewhat hopeful that the problems I'm seeing are a result of the maliit crashes on mir
[19:28] <ogra_> sergiusens, i think bill added the same MP from ted a few mins ago
[19:28] <plars> ricmm: I see a lot of stuff like this:
[19:28] <plars>     17:50:27.031 INFO testcase:554 - Killing process 2565
[19:28] <plars>     17:50:27.033 INFO testcase:557 - Appears process has already exited.
[19:28] <ricmm> why would autopilot attempt to kill maliit?
[19:28] <sergiusens> ogra_, that's good
[19:28] <ogra_> ricmm, it stops unity
[19:29] <plars> ricmm: I don't know that it's trying to kill maliit, and I haven't looked at the tests
[19:29] <ricmm> ogra_: right
[19:29] <ogra_> asac, can we please upload that maliit fix :P
[19:29] <plars> ogra_, ricmm: I see a unity8 crash with it too
[19:29] <ogra_> then your unity tests will work
[19:29] <ricmm> plars: what line?
[19:29] <ricmm> ah this log has no lines of course
[19:29] <ogra_> plars, can you hack the install ?
[19:30] <plars> ricmm: this was run by hand on my local device
[19:30] <plars> ogra_: if you can tell me what you want?
[19:30] <ricmm> tell me the test then
[19:30] <ogra_> plars, remove the second "stop on" line from the maliit upstart job
[19:30] <sil2100> asac: publishing HUD \o/
[19:30] <ogra_> plars, and then try again
[19:30] <ogra_> i bet it will work
[19:30] <plars> ogra_: ok, just to make sure we are talking about the same thing, are you talking about the unity8 tests or the ubuntu-keyboard tests?
[19:30] <plars> or both?
[19:31] <ogra_> plars, i talk about maliit crashing if it gets stopped ... which i.e. is triggered by stopping unity
[19:31] <plars> ricmm: the mp for the version of the keyboard tests I'm looking at is at https://code.launchpad.net/~veebers/ubuntu-keyboard/update_autopilot_emulators/+merge/190319
[19:31] <plars> ogra_: ok, so we should see it in either one
[19:31] <ogra_> right
[19:32] <ogra_> the job is broken, so it doesnt actually stop
[19:32] <ogra_> but unity does
[19:32] <ogra_> so you pull the floor out underneath
[19:32] <ricmm> unity exiting will have the result of maliit exiting if the keyboard has been invoked once
[19:32] <ricmm> as when Mir exits it asks all of its clients to clean up and die gracefully
[19:33] <ogra_> ricmm, right, but maliit has a "stop on session-end" ... you end up in an incosistent state, upstart thinks it died and tries to respawn it
[19:34] <sergiusens> ogra_, I tested earlier with stop on stopped unity8
[19:34] <ricmm> right
[19:34] <ogra_> with the "stop on stopping unity8" it will just properly shut down
[19:34] <ricmm> so im not so sure about that
[19:34] <ricmm> is autopilot bringing up unity8 with upstart?
[19:34] <ogra_> well, i have no crash files here
[19:35] <ogra_> which i do as soon as i re-add that line
[19:35] <sergiusens> ogra_, ricmm it's not most likely
[19:35] <ricmm> right but thats because you also dont have any maliitrunning
[19:35] <ogra_> right after a shutdown
[19:35] <ricmm> unity8 will not invoke maliit if the keyboard is needed
[19:35] <ricmm> but it will die every time that unity8 goes, if its alive
[19:35] <ricmm> that means that tests that restart unity8 and need keyboard would needto somehow make sure that maliit is running
[19:35] <sergiusens> ogra_, ricmm why not have the start stop logic for maliit in the unity8 test setup?
[19:35] <sergiusens> I saw other apps test like that
[19:35] <ricmm> exactly
[19:35] <ogra_> ricmm, nontheless the upstart job is broken :)
[19:36] <ricmm> ogra_: not saying it isnt
[19:36] <plars> ogra_: where is that job located?
[19:36] <ogra_> /usr/share/upstart/sessions/
[19:36] <ricmm> what im saying is that, even with the fix, ocne maliit dies once it wont come back
[19:36] <plars> thanks
[19:36] <ricmm> so when unity8 is killed, maliit will not return
[19:36] <ricmm> unless manually invoked
[19:36] <ogra_> ricmm, but it doesnt die, it gets propely stopped before unity
[19:36] <ogra_> and it will get started again with unity
[19:37] <ricmm> that'd be true if unity8 autopilot's invokations were happening via upstart
[19:37] <ricmm> but its just running the process manually and then killing by hand
[19:37] <ogra_> err
[19:37] <plars> ogra_: So I'm removing the stop on session-end and leaving the stop on stopping unity8 in place, correct?
[19:37] <ricmm> no?
[19:37] <ogra_> plars, right
[19:37] <ogra_> ricmm, that would be most evil ...
[19:38] <ogra_> ricmm, and the log looks like it is at least stopped via upstart
[19:38] <ricmm> ogra_: the first stop yes
[19:38] <ricmm> ogra_: but the runs actually bring it up manually
[19:38] <ogra_> ugh
[19:38] <ogra_> now thats  super evil
[19:38] <ricmm> evilpilot
[19:39] <ogra_> and i doubt we can solve this without moving autopilot to use upstart
[19:39] <ogra_> asac, ```
[19:40] <ricmm> or adding a startup of maliit-server for tests that need keyboard
[19:40] <ricmm> its all crap
[19:41] <ogra_> yeah
[19:41] <thomi> Hi guy
[19:41] <thomi> s
[19:42]  * thomi sees a lot of 'autopilot' pings from this channel, and wonders what the beef is
[19:44] <sergiusens> thomi, you probably need to start unity8 autopilot tests with upstart for the keyboard stuff to function correctly
[19:45] <sergiusens> thomi, well, veebers has to :-)
[19:45] <thomi> sergiusens: OK, that should be reasonably easy to hack up. veebers should be online in 15 minutes or so
[19:45] <thomi> right :)
[19:45] <thomi> I cna help him though
[19:45] <ogra_> cool
[19:45] <sergiusens> thomi, would be similar to the click stuff we have
[19:45] <sergiusens> thomi, but using a legacy APP_ID
[19:46] <sergiusens> sorry no
[19:46] <sergiusens> ignore that
[19:46] <thomi> sergiusens: oh? not just stop/start 'unity8'?
[19:46] <sergiusens> that's for legacy apps :-)
[19:46] <thomi> haha
[19:46] <sergiusens> thomi, yeah, start/stop unity8
[19:46] <thomi> right
[19:46] <thomi> He'll have to hack it into the test suite, and we can remove it once we start using autopilot 1.4, where we can add this support properly
[19:48] <tyhicks> asac, ogra_: Ok, stgraber has tested on touch: http://paste.ubuntu.com/6219448/
[19:49] <tyhicks> jdstrand and/or I can confirm his results in a few minutes
[19:49] <asac> plars: are we retrying the yellow ones :)?
[19:49] <asac> plars: maybe we can hit 100% with crashes :)?
[19:50] <plars> asac: right now I'm trying something for ogra_ will go back to that in a moment
[19:50] <ogra_> plars, well, if the tests actually not use upstart to start and stop the shell these tests are moot
[19:50] <plars> ogra_: I had some issue with that change - the tests wouldn't even start, but without they behave (modulo the known failures)
[19:50] <didrocks> asac: coming?
[19:51] <ogra_> plars, asac, the issue is that the tests just start up unity and not use the upstart start/stop commmands so maliit never gets started along
[19:52] <asac> didrocks: yep
[19:58] <kenvandine> asac, gerry's work around in unity-mir did solve the signon-ui problem, i've proposed a branch for unity-mir
[19:58] <kenvandine> asac, so it won't require changes in the signon stack to fix
[19:59] <ricmm> kenvandine: did he add the exception I said?
[19:59] <kenvandine> yeah
[19:59] <ricmm> sorry that I forgot
[19:59] <kenvandine> https://code.launchpad.net/~ken-vandine/unity-mir/lp1235337/+merge/190459
[19:59] <kenvandine> ricmm, ^^
[20:00] <ricmm> kenvandine: did you try starting apps with that?
[20:00] <ricmm> as in start signon-ui and then start another app right away
[20:00] <kenvandine> yup
[20:00] <ricmm> is signon-ui actually trying to create a window?
[20:00] <ricmm> even if it isnt displaying anything
[20:00] <kenvandine> no
[20:00] <kenvandine> only on the desktop
[20:01] <kenvandine> not on the phoen
[20:01] <kenvandine> phone
[20:01] <ricmm> the fenceNext troubles me there if its not bringing up anything
[20:01] <ricmm> lemme do some testing before happroving
[20:01] <asac> plars: yeah would be good if we want mir team to look at the regressions still left
[20:01] <asac> or if they are flaki
[20:01] <asac> some flakiness is i think normal with those crashes
[20:02] <plars> asac: well the unity8 ones are not going to get any better than what you see there, but the others are retrying that have 1 or 2 failed tests
[20:02] <kenvandine> ricmm, thx
[20:03] <asac> plars: yeah the rest i mean
[20:03] <asac> unity8 is still failing
[20:03] <ogra_> asac, yes, see backlog
[20:03] <ogra_> the tests will need fixing
[20:04] <ogra_> (and the maliit upstart job needs fixing, else this wont work either)
[20:05] <dobey> can i get someone to add something to a row in the landing asks page?
[20:10] <jdstrand> asac: I can confirm stgraber's results
[20:11] <jdstrand> asac: tyhicks was able to as well
[20:11] <asac> didrocks: thanks
[20:11] <asac> didrocks: wait]
[20:11] <jdstrand> unity8 came up, dbus is running, can launch apps, etc
[20:11] <didrocks> asac: yw ;) thanks to you
[20:11] <didrocks> asac: yeah?
[20:11] <asac> didrocks: so jdstrand wants to land dbus for desktop
[20:11] <asac> didrocks: and wants to do so before the final freeze
[20:11] <didrocks> I guess we need to assess the impact on all AP tests for phone
[20:11] <asac> didrocks: the code is supe minimal
[20:11] <didrocks> is that a risky change?
[20:12] <asac> didrocks: right. from reading code its really zero :)
[20:12] <didrocks> do you have a quick diff?
[20:12] <jdstrand> we change a stat() to an open()
[20:12] <ogra_> didrocks, it has been tested by various people and is a smal fix
[20:12] <asac> didrocks: jdstrand just said that they tested it?
[20:12] <asac> jdstrand: what can stgraber confirm?
[20:12] <asac> can you restate exactly what he did?
[20:12] <didrocks> ok, as long as unity8 AP tests are running (maybe just try an app tests as well?), I'm fine with this
[20:12] <asac> didrocks: http://people.canonical.com/~tyhicks/fixes/dbus/source/dbus_1.6.12-0ubuntu10.debdiff
[20:12] <jdstrand> asac: tyhicks said that stgraber confirmed dbus works. tyhicks and I independently confirmed that
[20:12] <asac> didrocks: a few null op diffs and then a small one
[20:12]  * didrocks looks
[20:12] <asac> didrocks: i checked that the mask file is there ... it has permissions:
[20:12] <tyhicks> here's what all three of us did: http://paste.ubuntu.com/6219415/
[20:13]  * jdstrand did a bit more than that
[20:13] <jdstrand> (but did do that)
[20:13] <asac> didrocks: 21:07 < asac> -r--r--r-- 1 root root 0 Jan  1  1970 /sys/kernel/security/apparmor/features/dbus/mask
[20:13] <asac> didrocks: here is what tyhicks and jdstrand and stgrabver did to ensure its safe: http://paste.ubuntu.com/6219415/
[20:13] <asac> (havent read)
[20:13] <tyhicks> note that there are some typos in the commands, unfortunately, but it shows that dbus-daemon comes up successfully and detects that apparmor is available
[20:14] <asac> tyhicks: you gusy seems to feel resistant of testing it on the phone :)?
[20:14] <asac> its not clear if you tested it on the phone with our touch image
[20:14] <didrocks> yeah, and the code change seems not really risky at all ;)
[20:14] <jdstrand> stgraber's paste doesn't have typos: http://paste.ubuntu.com/6219448/
[20:14] <asac> but
[20:14] <didrocks> I would love just that the AP tests are run on phone for unity8 and one app
[20:14] <didrocks> just to ensure we can still start/connect through AP
[20:14] <asac> didrocks your call. i believe we could let it in with some confirm that our touch image is not busted
[20:14] <jdstrand> asac: grouper isn't enough?
[20:14] <tyhicks> asac: not resistant at all - we were just short on time
[20:15] <asac> jdstrand: grouper isnt existing for us :)
[20:15] <asac> tyhicks: right we are also short in time. if this busts we loose 18 hours
[20:15] <asac> which is 20% of the time left :)
[20:15]  * jdstrand puts it on his avengers device
[20:15] <asac> risk is low, but stake is still high
[20:15] <plars> asac: notes was the first to run, just fininshed and it got worse by one test
[20:15] <asac> plars: retry?
[20:15] <asac> is it flaki?
[20:15] <jdstrand> note, grouper mir with unity in devel-proposed
[20:15] <jdstrand> worked
[20:15] <asac> plars: given how maguro loks i would assume its super lfaki
[20:16] <didrocks> asac: I think grouper for just starting and ensuring dbus connect is fine enough
[20:16] <plars> asac: yeah, I'm talking about mako, and I've already kicked it off to retry
[20:16] <didrocks> jdstrand: but please do run the AP tests
[20:16] <plars> asac: maguro is much farther away
[20:16] <didrocks> as autopilot is connecting through dbus to pilot the app + unity8
[20:17] <jdstrand> didrocks: all of them? it passed all tests on desktop. we had far less barriers for the changes a couple days ago. we just change a stat to an open
[20:17] <jdstrand> didrocks: this bug is blocking autopilot tests on desktop
[20:18] <didrocks> jdstrand: well, autopilot doesn't connect the same way on phone and desktop (for unity8) as from what I got, apparmor is not setup the same way
[20:18] <didrocks> is testing dbus on the phone or grouper is such an issue?
[20:18] <jdstrand> we did test on grouper
[20:18] <didrocks> (I think running both unity8 + let's say notes-app tests is taking 10 minutes in total)
[20:18] <jdstrand> testing on mako is an issue
[20:18] <didrocks> running AP tests?
[20:18] <didrocks> yeah, so running the AP tests on grouper is enough IMHO for this one
[20:19]  * ogra_ adds line 182 to landing asks and goes for dinner
[20:19] <didrocks> does this sound so unreasonable as tests?
[20:20] <jdstrand> didrocks: are AP tests know to work on unity8? I just did a left to right swipe and the display is hosed
[20:20] <jdstrand> sorry, on grouper
[20:20] <didrocks> jdstrand: I don't know on grouper, I would say a before/after would help
[20:20] <didrocks> test*
[20:21] <asac> didrocks: sorry, there is another friend asking for landing something that was not known before :)
[20:21] <jdstrand> tyhicks: I can't do it sorry. I have to go
[20:21] <asac> see -touch
[20:21] <tyhicks> jdstrand: understood
[20:21] <jdstrand> tyhicks: I guess the desktop AP tests will continue to fail until I can test on mako
[20:21] <tyhicks> is this the way to run all of th AP tests: https://wiki.ubuntu.com/Touch/Testing/Autopilot
[20:21] <tyhicks> ?
[20:22] <jdstrand> tyhicks: you can try on grouper-- but I'm guessing it isn't going to work well
[20:22] <thomi> tyhicks: no, that's pretty outdated information
[20:22] <jdstrand> https://wiki.ubuntu.com/Touch/Testing I think is what you need
[20:22] <jdstrand> tyhicks: if you get it done in time, perhaps someone in this channel can sponsor for you
[20:23]  * jdstrand -> appt
[20:23] <tyhicks> ok
[20:23] <asac> slangasek: what do you think about staging nm before the freeze in proposed but wait till we are able to test it tomorrow morning?
[20:23] <jdstrand> tyhicks: sorry I couldn't help more
[20:23] <asac> cyphermox: didrocks: ^^
[20:23] <tyhicks> thomi: can you confirm that https://wiki.ubuntu.com/Touch/Testing is what I need
[20:23] <asac> slangasek: release team hat on i am asking :)
[20:23] <tyhicks> jdstrand: no problem
[20:23] <slangasek> asac: I think that delays us being able to master images for the release
[20:23] <slangasek> and am therefore against it
[20:24] <asac> slangasek: so it would then have to wait for opportunistic landing for a new image?
[20:24] <thomi> tyhicks: yes, that looks *much* better :)
[20:24] <tyhicks> thanks
[20:24] <slangasek> asac: effectively, yes
[20:24] <cyphermox> this is a fix specific for touch so if you don't think you have time to further test it and all, I just won't upload
[20:24] <asac> slangasek: likelyhood of getting a respin by monday is > 80% :)?
[20:25] <asac> didrocks: what happens if this sits in proposed? does this block others from entering?
[20:25] <didrocks> asac: if there is no ABI break, it shouldn't
[20:25] <didrocks> I think staging in proposed is the way to go: at worse, if we don't do any respin (hem hem), this will go in -updates
[20:26] <asac> slangasek: so how likely is it that you might defer building master image later than tomorrow morning from current look?
[20:26] <asac> slangasek: right. or maybe its a candidate for -updates?
[20:26] <asac> didrocks: right.
[20:26] <slangasek> asac: we would not defer it at all, we need to get candidate images out to start the testing
[20:26] <asac> slangasek: right. just thought maybe you fight another blocker still
[20:27] <asac> not asking if you defer it for this
[20:27] <asac> didrocks: i agree. your call. if you know that we can still land other stuff then its good
[20:27] <slangasek> asac: well, we might go in knowing we would need a respin after, but we would still produce images and start testing them
[20:27] <asac> didrocks: cjwatson stated that we can even do things in -updates and pull it into the images
[20:28] <slangasek> but in this case, no, I'm not aware of any late-landing fixes that we're expecting
[20:28] <didrocks> jdstrand: line 217 in landing ask
[20:28] <rsalveti> didrocks: asac: slangasek: got a working gst/hybris for video thumbnail and video playback in the browser, can we still push that today?
[20:28] <asac> right. but if you know you need a respin, you could process it right after the image was build :)
[20:28] <rsalveti> or tomorrow only? don't know the current state of things
[20:28] <asac> hehe
[20:28] <kgunn> slangasek: fyi....merged & ask sheet....https://code.launchpad.net/~vorlon/unity8/lp.1235649/+merge/190443
[20:28] <asac> didrocks: so yeah. lets do that. i think we could even wait with uploading until we have it fully tested
[20:28] <slangasek> kgunn: cheers
[20:28] <didrocks> asac: agreed
[20:29] <asac> didrocks: ok, so noo upload. we will check and upload to proposed for opportunistic landing tomrrow after the first image
[20:29] <asac> and then route it to -updates in case no new image is coming up
[20:29] <didrocks> right
[20:30] <didrocks> rsalveti: same, I guess, stage that to proposed, and we'll try to pick it up tomorrow
[20:30] <didrocks> rsalveti: just ensure with the release team you can pin it
[20:30] <didrocks> rsalveti: we want another mir-fix-only image and then process the rest
[20:30] <rsalveti> gst-plugins-is fine, just need a change in hybris and one android respin
[20:31] <rsalveti> not related with mir this one
[20:31] <rsalveti> didrocks: did we freeze the proposed transition as well?
[20:32] <didrocks> rsalveti: I would love that, let me add a comment in the landing spreadsheet
[20:32] <asac> rsalveti: isnt this exclusively for phone?
[20:32] <rsalveti> asac: it is
[20:32] <asac> if so we can take the same route as we do with network-manager
[20:32] <asac> e.g. we dont need to rush it imo
[20:32] <asac> anyway. didrocks knows :)
[20:33] <rsalveti> don't need to rush, but getting that today would be fine unless you want me to block it
[20:33] <didrocks> rsalveti: please, just ensure it will be staged in proposed, we'll unblock it tomorrow
[20:33] <didrocks> rsalveti: I guess slangasek can hint britney for it
[20:33] <asac> rsalveti: we have a good plan. that will get us a full recovered MIR image tomorrow. after that everyone will land. if proposed staging is good and doesnt block landing everything i agree with didrocks
[20:33] <asac> that you cdan stage it
[20:33] <asac> if the release team is aware to not take it :)
[20:33] <slangasek> what am I hinting?
[20:34] <rsalveti> would need to stage libhybris, gst-plugins-bad1.0 and android
[20:34] <didrocks> rsalveti: you handle the android rebuild as well?
[20:34] <rsalveti> didrocks: yes
[20:34] <sergiusens> fginther, according to your list music should be unblocked, was that a typo? if not https://code.launchpad.net/~sergiusens/music-app/manifest/+merge/190250 is stuck
[20:35] <didrocks> rsalveti: thanks ;)
[20:35] <rsalveti> slangasek: do I need to ask the release team to block the proposed transition of those packages specifically?
[20:35] <rsalveti> or is everything frozen already?
[20:36] <slangasek> rsalveti: things are not frozen in proposed-migration currently, only at archive accept
[20:36] <fginther> sergiusens, yes, that was a typo, it's disabled
[20:36] <sergiusens> ack thanks
[20:36] <didrocks> rsalveti: updated req 148 FYI
[20:36] <rsalveti> slangasek: right, but can I request to freeze the proposed migration for these packages specifically?
[20:37] <rsalveti> as it seems people want stuff to be in proposed til tomorrow
[20:37] <slangasek> rsalveti: yes
[20:38] <didrocks> slangasek: do you prefer me doing it?
[20:38] <didrocks> (the hint)
[20:38] <slangasek> I'm already doing it ;)
[20:38] <didrocks> excellent!
[20:38] <didrocks> thanks slangasek, rsalveti!
[20:38] <rsalveti> slangasek: great, thanks
[20:38] <didrocks> rsalveti: we're getting it in just after the first image tomorrow morning
[20:38] <didrocks> (94 if all goes according to the plan)
[20:39] <seb128> didrocks, can we get a new settings on the image? ;-)
[20:39] <rsalveti> didrocks: great, thanks
[20:39] <didrocks> seb128: tomorrow morning, same image than rsalveti :)
[20:39] <seb128> didrocks, thanks
[20:39] <seb128> well at least this one is universe
[20:40] <seb128> so the release team is not in the way
[20:40] <didrocks> yeah, let's hope that tomorrow's Mir image will be as good as we hope
[20:40] <didrocks> and we can try to catch up
[20:41] <seb128> didrocks, asac: we have fixes that depends on indicator updates, do we plan to build images with SRU updates if needed?
[20:42] <didrocks> seb128: I'm afraid that we need to discuss that one seriously tomorrow now that the archive is frozen
[20:42] <asac> seb128: before the release we might divert uplaods to -updates, but the current thinking is that we focus on T
[20:42] <didrocks> or we can move stuff to -updates until then
[20:42] <asac> heh
[20:42] <seb128> asac, which means releasing 1.0 with those bugs?
[20:42] <asac> seb128: dont worry. things will work fine
[20:42] <didrocks> sounds like the saner plan
[20:43] <didrocks> seb128: I guess we'll have image building with -updates for touch
[20:43] <seb128> asac, well, I don't care much for myself, but we have e.g the "sound keys trigger weird notification" bug in that category
[20:43] <asac> seb128: no, we can build images with things in -updates - if it comes to it - i was told
[20:43] <asac> seb128: so we can land for a bit in the archive and then in -updates and release a great story next wednesday
[20:43] <asac> thats my - potentially overly optimistic - hope :)
[20:44]  * didrocks tries to be overly optimistic as well for once :p
[20:44] <didrocks> anyway, I think it's high time
[20:44]  * didrocks waves good evening :)
[20:44] <seb128> asac, so it means SRUs to get in -updates?
[20:44] <seb128> didrocks, night
[20:44] <asac> didrocks: enjoy and and sleep like a rock :)
[20:44] <asac> ttyt
[20:44] <cyphermox> night didrocks
[20:44] <didrocks> asac: thanks will try! ;)
[20:44] <asac> seb128: no. you just upload to saucy
[20:44] <didrocks> good night seb128, cyphermox ;)
[20:44] <asac> seb128: through CI ... and things will go into -updates in case we dont want to respin a desktop image
[20:45] <asac> (and our touch image picks it up from there before the release)
[20:45] <seb128> asac, how are things going to go to -updates? that's for verified SRUs
[20:45] <asac> seb128: its before the release, so its not a SRU
[20:46] <asac> well, it kind of is. so yeah. you need to do proper testing on desktop
[20:46] <seb128> asac, what happens to those -updates version at release time then? do we wipe them out? or are desktop users getting them as SRUs?
[20:46] <asac> seb128: yes. desktop useres get them on day one
[20:46] <tyhicks> asac: stgraber reports that the unity8 AP tests pass on mako with the updated dbus package
[20:46] <seb128> asac, I doubt slangasek & co are going to move uploads to saucy-updates without following the SRU rules
[20:47] <asac> seb128: right. however, i doubt we want to land anything at this point that doesnt meet the SRU quality standards
[20:47] <asac> seb128: i think you just need to take care that you dont change the desktop UI and that you have rock solid quality on your changes
[20:47] <asac> which is beneficial at this point anyway
[20:47] <seb128> right
[20:47] <asac> tyhicks: unity8 AP pass?
[20:48] <asac> tyhicks: that would good news, because they officially fail :)
[20:48] <asac> lol
[20:48] <tyhicks> I'll relay that to stgraber
[20:49] <asac> yep. asked him
[20:49] <asac> on -touch
[20:50] <sil2100> asac: any objections for landing platform-api?
[20:51] <asac> sil2100: is it in plan? did we validate that it doesnt regress our nice AP ratio here: http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/92:20131010.2:20131010/4662/ ?
[20:51] <asac> sil2100: if both are true, go for it
[20:51] <asac> image 93 is what it needs to be scheduled for
[20:53] <asac> tyhicks: can you just take a phone and test it against latest image please?
[20:53] <asac> i know its tempting to just test it against something undefined, but if we do that its not even worth the time there as we still wont know
[20:53] <tyhicks> asac: I don't have the hardware
[20:53] <sil2100> asac: no idea if we validated that, but I know didrocks poked me about getting that in, as it fixes the maliit-server issues (probably)
[20:55] <asac> sil2100: right. we need to test
[20:56] <asac> thats was the whole idea of poking i am 99.9% sure
[20:56] <asac> tyhicks: ack
[20:56] <sil2100> asac: should I run all the AP tests with it?
[20:56] <asac> thats the problem with having busted tests. i would say unity8, but now we dont know
[20:57] <asac> sil2100: run webbrowser :)
[20:57] <asac> lol
[20:57] <asac> sil2100: what is this trying to fix again>?
[20:57] <sil2100> asac: hehe, but how does it look on a vanilla system? All pass? Smoketesting say so, but is that accurate?
[20:57] <asac> sil2100: mallitt crashes? just run a few APs that have maliit crashes
[20:57] <asac> sil2100: pick 2 here: http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/92:20131010.2:20131010/4662/
[20:58] <sil2100> asac: https://launchpad.net/bugs/1233988
[20:58] <asac> sil2100: all pass means that you can get it to all pass
[20:58] <asac> sil2100: as soon as one fails we cant say that its impossible to get to all pass
[20:58] <asac> thats the dilemma and why we can only shoot for 100%
[20:58] <asac> sil2100: right. so pick a few crashes we see here
[20:58] <asac> sil2100: and confirm that they go away
[20:59] <asac> sil2100: so messaging-app is pretty quick test
[20:59] <asac> seems to produce crashes reliably
[20:59] <asac> sil2100: share app as well
[20:59] <asac> sil2100: and if you are strong run webbrowser app
[21:39] <jdstrand> asac: so, we've tested the code thoroughly, but you want us to run the unity8 tests on mako, but the unity8 tests are known to fail
[21:39] <jdstrand> asac: it doesn't matter now anyway, but this is pretty frustrating esp when we tried to do the right thing and got blocked
[21:40] <tyhicks> stgraber has ran the tests and reported on the results in #ubuntu-release
[21:40] <jdstrand> right, but wasn't he told he had to update to the latest, which is known to fail?
[21:42] <jdstrand> asac: apparently the tests passed
[21:42] <jdstrand> so we've met the criteria "Please run AP tests on phone for unity8 + one app to ensure that the tests still starts and communicate with the app", but the status in the landing plan is TODO, so I don't know if we should upload or not
[21:43] <jdstrand> asac: passed on surfaceflinger (see #ubuntu-release for details)
[22:02] <jdstrand> I might add that the risk assessment is not medium
[22:03]  * jdstrand changes
[22:09] <asac> jdstrand: i thought we already said tis ok etc.
[22:09] <asac> and yu have a landing slot
[22:09] <asac> if you did that
[22:09] <asac> if didrocks said something else then let me know
[22:09] <jdstrand> didrocks gave the landing slot, but there was a TODO
[22:09] <jdstrand> I don't know what that meant. I updated the page
[22:09] <jdstrand> (showing the testing involved)
[22:10] <jdstrand> I guess I'll upload-- it'll be blocked in unapproved and people can ping me about it there
[22:10]  * jdstrand will mention in #ubuntu-release
[23:00] <rsalveti> gst-plugins-bad integration is blocked by bug 1238312
[23:00] <rsalveti> mir specific as well
[23:02] <rsalveti> slangasek: smells like toolchain related ^
[23:02] <rsalveti> only with armhf, and when built natively
[23:02] <slangasek> !
[23:04] <slangasek> rsalveti: could it be an issue with uninitialized memory that happens to wind up initialized differently by the compiler for cross vs. native?
[23:05] <rsalveti> that's what I was thinking as well
[23:06] <slangasek> well, if it's uninitialized memory, then it's not actually a toolchain bug
[23:06] <slangasek> because something should've initialized it :)
[23:06] <slangasek> is libubuntu_application_api_mirclient in the mir source package?
[23:06] <rsalveti> nops
[23:06] <rsalveti> that's part of the platform-api
[23:07] <rsalveti> but links against mirclient
[23:07] <rsalveti> right, it seems affected by the toolchain, but it might indeed be an issue in the mir code itself
[23:14] <slangasek> rsalveti: do you know where the exit handler is set from?
[23:15] <rsalveti> nops
[23:16] <rsalveti> you're not in #ubuntu-mir btw
[23:17] <slangasek> I am in far too many channels already
[23:17] <rsalveti> yeah :-)