[00:06] <thomi> robru: are you able to paste me the link where I can follow that test run please? is it this? http://10.97.0.1:8080/job/autopilot-saucy-daily_release/
[00:07] <robru> thomi, not much to see yet: http://10.97.0.1:8080/job/cu2d-qa-saucy-2.1build/34/console
[00:08] <thomi> robru: awesome, I just wanted to catch it when it ended
[01:17] <thomi> robru: fginther: this job looks stuck to me? http://10.97.0.1:8080/job/autopilot-saucy-daily_release/2126/
[01:17] <thomi> I'm still waiting for that qa stack run to end
[01:18] <robru> thomi, i see a test failure: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-intel/2125/testReport/junit/unity.tests.test_panel/PanelKeyNavigationTests/test_panel_indicators_key_navigation_prev_works_Single_Monitor_/
[01:18] <thomi> robru: but that's the unity tests, I'm after the autopilot tests
[01:31] <robru> thomi, dunno then. it could be stalled. there's been lots of infrastructure issues lately, but I dunno many details. maybe didrocks would be better to answer that question? he'll be on in a few hours
[01:33] <thomi> yeah, I guess I'
[01:33] <thomi> ll wait
[01:33] <thomi> oops
[01:33] <thomi> thanks for your help anyway
[06:03] <didrocks> Mirv: do you have some free slots?
[06:04] <didrocks> good morning btw ;)
[06:06] <Mirv> didrocks: morning! not really right now, I've still not been able to start what I suppoed to start with 2h ago because I was debugging sdk problems (which turned out not to probably be sdk problems)
[06:06] <didrocks> Mirv: ok, good luck then!
[06:06] <Mirv> cu2d would also have some bugs to file, but I'll let it run the next tick first
[06:06] <didrocks> ok
[06:06] <Mirv> libfriends was hanging cu2d since last evening, and will probably do that again so I'll keep an eye on that
[06:07] <didrocks> Mirv: robru didn't kill it?
[06:07] <didrocks> Mirv: I explicitely asked him to kill it
[06:07] <Mirv> didrocks: no, it was still running
[06:07] <didrocks> ok, let's remove libfriends then
[06:07] <didrocks> from the config
[06:07] <didrocks> Mirv: we can't have timeout on building because some builds can lag a lot (not the case recently, was the case in the past)
[06:07] <Mirv> ok
[06:07] <Mirv> that's true
[06:08] <didrocks> robru: removing libfriends, please fix the buildd issue I pointed you at yesterday (and see spreadsheet)
[06:08] <Mirv> didrocks: ah, correction, too many things this morning. it was actually that intel + nvidia jenkins slaves had died..
[06:08] <didrocks> Mirv: both? again? :/
[06:09] <Mirv> didrocks: and that was since yesterday evening, and then only after that libfriends hung
[06:09] <Mirv> didrocks: could we get QA team to somehow have autokicker/monitor/alerting on that?
[06:09] <didrocks> Mirv: let's raise it in this morning call
[06:10] <didrocks> Mirv: libfriends removal deployed
[06:10] <Mirv> didrocks: I just noticed, thanks
[06:11] <didrocks> Mirv: do not hesitate to do that next time btw ;)
[06:11] <didrocks> (as long it's logged somewhere like in the spreadsheet)
[06:11] <Mirv> right..
[06:17] <vila> didrocks, Mirv: Not fully awake yet but a bit of explanation would help ? (Context, I'm ramping up with how the ci engine works so speak slowly ;)
[06:17] <vila> intel + nvidia jenkins slaves ? slave names ?
[06:17] <didrocks> vila: the 2 slaves being the test machines
[06:18] <didrocks> it happens quite often that we have a kernel panic
[06:18] <didrocks> and so the machine is stuck
[06:18] <didrocks> the jenkins node don't work
[06:18] <didrocks> so we can't contact them
[06:18] <vila> kenerl panic seen in the jenkins logs or requiring shell access ?
[06:18] <didrocks> vila: seen in logs (jibel most of the time get those)
[06:18] <didrocks> but before, the machines needs to be rebooted
[06:18] <didrocks> electrically
[06:19] <didrocks> through the CDU
[06:19] <vila> ouch
[06:19] <didrocks> so we would need something monitoring those slaves
[06:19] <vila> yup
[06:19] <didrocks> and if they don't answer for 5 minutes, reboot electrically
[06:19] <vila> probably not jenkins itself but yeah
[06:19] <didrocks> and ensuring the jenkins slave started
[06:19] <didrocks> yeah
[06:19]  * vila nods
[06:19] <didrocks> vila: mind adding that to the TODO? ;)
[06:19] <didrocks> as this is blocking everything when it happens and nobody monitors
[06:20]  * vila 's.head.TODO++
[06:20] <didrocks> (everytime we report to the kernel team, it's "have you tried latest kernel update?")
[06:20] <didrocks> thanks
[06:20] <vila> didrocks: I'm using this channel log as a huge TODO for now :-/
[06:20] <didrocks> heh
[06:21] <vila> "libfriends removal deployed" how ? What does it mean ?
[06:22] <vila> didrocks, Mirv: a commit reference will help me understand how the config work ;)
[06:22] <didrocks> vila: latest commit on lp:cupstream2distro-config
[06:24] <vila> http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro-config/trunk/revision/814?start_revid=814
[06:24] <vila> ok ,that's the how
[06:24] <vila> what does it trigger/stop to trigger ?
[06:24] <didrocks> it doesn't build anymore libfriends
[06:25] <didrocks> in the daily release machinery
[06:25] <didrocks> (basically no prepare-libfriends jobs)
[06:25] <vila> so the last good version is used instead ?
[06:25] <didrocks> right
[06:25] <vila> \o/
[06:26] <vila> which version is that then ? ppa/proposed/archive whichever comes first ?
[06:27] <didrocks> whicherver comes first
[06:27] <didrocks> the highest version
[06:27] <vila> great
[06:27] <vila> and then you trigger a stack build again ?
[06:27] <didrocks> well, it's triggered every 4 hours
[06:27] <didrocks> and we just had a tick
[06:27] <didrocks> so should be fine
[06:27] <vila> haaa, the tick!
[06:28] <vila> any wau to trigger that manually or will that result in a huge mess ?
[06:28] <vila> *way
[06:28] <didrocks> we can, but not needed in that case
[06:28] <vila> ok
[06:28] <didrocks> but when you trigger manually you need to know what's the current dep are
[06:28] <vila> elaborate ?
[06:29] <didrocks> if you have indicators building
[06:29] <didrocks> and you trigger unity
[06:29] <didrocks> maybe you are building against half the new indicators
[06:29] <didrocks> and half the old ones
[06:29] <vila> oh right, bad idea
[06:29] <didrocks> so you don't know which state you are having
[06:29] <vila> any way to abort all in flight builds ? or some of them ?
[06:30] <didrocks> manually in launchpad
[06:30] <vila> or is that too tricky/unreliable ?
[06:30] <didrocks> but again, you are in an unknown state
[06:30] <vila> in lp ???
[06:30] <didrocks> as you maybe have binaries published
[06:30] <didrocks> yeah
[06:30] <vila> oh, the builds happen in lp after you dput to some ppa ?
[06:31] <didrocks> ?
[06:31] <didrocks> that's how the system work
[06:31] <didrocks> or I don't understand the question? ;)
[06:31] <vila> I'm learning so I may miss some obvious things ;)
[06:31] <didrocks> look at my presentation
[06:31] <didrocks> the prepare dput to a ppa
[06:31] <didrocks> then, we monitor the build into that ppa
[06:34] <vila> https://docs.google.com/a/canonical.com/presentation/d/1-1qB0GamQhdvCHFa49fe6x2emqSe0e_LNnITZRiZLuE/edit#slide=id.gf421d6b8_1107 ?
[06:34] <didrocks> vila: right
[06:35] <vila> how do you find the the lp build url ?
[06:40] <jibel> didrocks, vila retoaded could add a nagios check and sned a fence_cdu command if the mahcine doesn't respond after a timeout
[06:41] <jibel> didrocks, 10min is safer than 5 because the mahcines are rebooted every day and if there is an fsck it can take a while
[06:41] <vila> jibel: I understand what you mean but I have no idea on how to make it real :) Does retoaded know enough about that to turn it into a working solution ?
[06:41] <jibel> and in this case there is a risk of boot loop
[06:41] <jibel> vila, yes he knows everything
[06:41] <didrocks> jibel: yeah, making sense :)
[06:42] <didrocks> vila: why do you need it? the build monitors it
[06:42] <vila> jibel: great, will check with him then
[06:42] <didrocks> it only print the launchpad build url in case of failure
[06:42] <didrocks> if you want to play a little bit, look at the mir stack, mir failed on i386
[06:42] <vila> didrocks: I don't  need it *now*, I'm trying to understand what I will do the day I need it ;)
[06:43] <didrocks> vila: really, try poking around in the UI first
[06:43] <vila> me or anybody with the required access, whatever
[06:43] <didrocks> as it seems it's blurry for you ;)
[06:43] <didrocks> with the presentation on the other side
[06:43] <didrocks> I think it will make sense
[06:44] <vila> ok, will try, but if I feel I'm blindly poking around I will come back for more hand holding ;)
[06:45] <didrocks> vila: if you don't remember my presentation you should read https://wiki.ubuntu.com/DailyRelease (and the links under More specific topic)
[06:45] <vila> didrocks: oh, I do remember it, but that doesn't mean I understood it enough ;)
[06:53] <vila> didrocks: starting at http://s-jenkins:8080/view/Mir/job/mir-android-saucy-i386-build/2144/console ?
[06:53] <vila> failed to open trace file: [Errno 2] No such file or directory: '/home/ubuntu/.bzr.log'
[06:53] <vila> is a Bad Thing !
[06:55] <vila> didrocks: may be unrelated but '1 conflicts encountered.
[06:55] <vila> bzr: ERROR: Conflicts from merge' is obscure, is this a common failure ?
[06:55] <didrocks> vila: this is not daily release
[06:55] <didrocks> vila: I don't know that one
[06:55] <didrocks> you have a cu2d view
[06:55] <didrocks> daily releases are there
[06:55] <vila> crap, wrong jenkins server ?
[06:55] <didrocks> to view the chained jobs, you should use the private instance
[06:55] <didrocks> 110.97.0.1:8080
[06:56] <didrocks> 10*
[06:57] <vila> my kingdom for a dns entry !
[07:01] <vila> hmm http://10.97.0.1:8080/view/cu2d/ 3 reds 2 greys, really ? grey as disabled ? Too bad it so looked liked stack directory names :-/
[07:01] <vila> http://10.97.0.1:8080/view/mir/job/cu2d-mir-saucy/14/ is more on track ?
[07:02] <vila> then http://10.97.0.1:8080/job/cu2d-mir-saucy-2.1build/13/console
[07:02] <vila> then https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/5050734 ?
[07:03] <didrocks> vila: right
[07:03] <vila> \o/
[07:04] <vila> a bit weird that it ends up in a failed compilation... could it be that the dev never saw that failure because some update happened after he successfully compiled or are the builds stricter ?
[07:04] <didrocks> vila: doesn't happen on other archs
[07:05] <vila> hmm
[07:05] <vila> but it's not an infrastructure issue right ?
[07:05] <didrocks> no
[07:05] <vila> just something the dev could't reproduce locally so a valid output from the ci engine right ?
[07:06] <didrocks> everything is valid, I pinged upstream, they just investigate
[07:08] <vila> ... from there they fix it however they see fit, land on whatever package's trunk in the mir stack and wait for the next tick ?
[07:08] <didrocks> or we will relaunch it as it's very urgent
[07:08] <didrocks> and block other stacks
[07:08] <vila> oooooook
[07:09] <vila> enough food for thought during shave/shower ;)
[07:09] <vila> didrocks: thanks a ton, sorry for all the silly questions ;)
[07:10] <didrocks> no worry ;)
[07:20] <Mirv> didrocks: ok now platform is stalled because it waits for mir https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/5050812
[07:20] <Mirv> canceling to kick it further
[07:21] <lool> morning guys
[07:21] <lool> didrocks: two questions
[07:21] <vila> didrocks: in http://10.97.0.1:8080/view/mir/job/cu2d-mir-saucy/, where is that '(blocking)' coming from for the subprojects ?
[07:21] <lool> didrocks: first, how's the mir development/experimental branch published?
[07:21] <didrocks> Mirv: yeah, alf is looking at it, you can kill both platform and unity8 stack if you want
[07:21] <Mirv> right
[07:21] <lool> didrocks: that is, are we helping land changes from the dev branch of mir into some PPA, or is that some other setup than cu2d?
[07:22] <didrocks> lool: there is no more experimental branch for Mir
[07:22] <vila> Mirv: care to paste the urls you use to kill ?
[07:22] <didrocks> there is a mode on cu2d for that, a pity you were not at the Boston sprint when I presented it
[07:22] <lool> didrocks: second, I didn't figure out parameters to build just one package out of a stack, or everything but one package; I looked at the configured scripts, but didn't see any input vars, so I guess you might be driving these manually, with the shell?
[07:23] <didrocks> lool: can be done using the shell command, but as well, you have REBUILD_ONLY
[07:23] <didrocks> it's a space separated values of packages
[07:23] <lool> didrocks: I mean ~mir-team/mir/development-branch
[07:23] <didrocks> lool: I don't know about that branch, so no, we don't do anything special with it
[07:23] <lool> didrocks: so I have to set REBUILD_ONLY in the top job, the master control job for a stack, if I wand this to work, correct?
[07:24] <didrocks> right
[07:24] <lool> ok cool
[07:24] <didrocks> it will take the previous state
[07:24] <didrocks> but only rebuild those
[07:24] <didrocks> (if they have things to release)
[07:24] <lool> awesome
[07:24] <didrocks> you have FORCE_REBUILD parameter
[07:24] <didrocks> to tell "please, even if there is nothing new to release, rebuild it"
[07:24] <didrocks> (it will add a new changelog entry with "manual build forced"
[07:25] <didrocks> there are also the skip dest check parameters, but we can discuss that later on
[07:25] <vila> didrocks, Mirv: the '(see spreadsheet)' in http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro-config/trunk/revision/814?start_revid=814 refers to line 5 in https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=3 'Stack status' right ?
[07:25] <didrocks> vila: no, current tab, last item
[07:26] <Mirv> vila: I use the red 'x':s on the stack's build + check subjob pages
[07:26] <Mirv> vila: when logged in to the internal jenkins instance
[07:28] <vila> didrocks: I see
[07:28] <vila> Mirv: page url ?
[07:29] <vila> grr was not logged in couldn't see any running/pending jobs
[07:33] <didrocks> Mirv: don't worry about the unity8 failures
[07:33] <didrocks> Mirv: it's because of unity-mir not being installable
[07:33] <didrocks> because of mir on i386 not producing the -dev
[07:33] <didrocks> and the domino world starts!
[07:35] <vila> 'ping upstream' in '<didrocks> everything is valid, I pinged upstream, they just investigate' ~== mail allan.lesage@canonical.com since he's 'contact_email' for libfriends ?
[07:35] <didrocks> vila: no, pinging #ubuntu-mir on IRC
[07:35] <didrocks> emails is too slow
[07:36] <didrocks> and we are not talking about friends
[07:36] <didrocks> but Mir here
[07:38] <vila> ok, grep 'mir' stacks/saucy/friends.cfg is empty, how do you know it's mir related ? expertise ?
[07:38] <Mirv> vila: http://10.97.0.1:8080/view/cu2d/view/Saucy/view/Platform/ - from there 2.1build and 2.2check. on those pages.
[07:41] <vila> Mirv: damn, why are they all grey in jenkins ? I thought grey meant 'disabled' :-/
[07:43] <vila> is this aborted instead and bubbles up from aborted build to parent jobs ?
[07:45] <vila> *s/parent jobs/ parents jobs or views/
[07:54] <Mirv> vila: they're grey because they were aborted on this tick
[07:54] <Mirv> vila: yep
[07:55] <vila> didrocks: regarding 'it will add a new changelog entry with "manual build forced"', care to point me an url where the changelog is displayed when you come to it ? IIRC, that was one use case were the --multimaint dch fix was required or two entries for were created
[07:55] <vila> Mirv: thanks ! Makes far more sense this way ! Pfew
[07:55] <Mirv> vila: I also aborted unity already before since because of some previous delays this tick wouldn't have started on time otherwise (unity autopilot tests take the longest, about 1h 45min)
[07:55] <didrocks> vila: not now, I'm trying to unblocking production, those are corner cases that don't happen everyday (extra functionality)
[07:55] <didrocks> vila: not sure it will be a good use of your time as well ;)
[07:56] <vila> didrocks: it should be fixed and display a single entry, just want to look if I'm right. If I'm wrong, so be it ;)
[07:56] <didrocks> in fact 2 entries
[07:56] <didrocks> the "manual build forced"
[07:56] <didrocks> + "latest snapshot from rev xxx"
[07:56] <didrocks> (the last one is always present)
[07:57] <didrocks> vila: you do have examples in the testssuite IIRC
[07:57] <vila> didrocks: ok, so there is a corner case I don't understand yet. Good, pushed on stack.
[07:57] <vila> didrocks: ha, vila.TODO++ ^
[08:08] <didrocks> ogra_: hey! how was the image yesterday evening? build went fine?
[08:08] <ogra_> didrocks, yes, but the gallery app test on mako failed badly and had to be restarted
[08:08] <didrocks> second run seems better
[08:08] <ogra_> i didnt want to wait anymore at 1am so its not released yet
[08:08] <didrocks> yeah ;)
[08:09] <Mirv> vila: FYI pressing red 'x' on http://10.97.0.1:8080/view/cu2d/view/Saucy/view/Unity8/job/cu2d-unity8-saucy-2.2check/
[08:09] <ogra_> will do so once someone to announce at avengers is around
[08:09] <didrocks> notes-app regressed?
[08:10] <ogra_> i wouldnt see how it had no update
[08:10] <didrocks> sdk was updated, right?
[08:10]  * didrocks looks for ogra's page
[08:10] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/
[08:11] <vila> Mirv: thanks, so here the reason is in https://launchpadlibrarian.net/151505876/buildlog_ubuntu-saucy-armhf.unity8_7.81.3%2B13.10.20130926-0ubuntu1_FAILEDTOBUILD.txt.gz right ?
[08:11] <vila> Mirv: as well as in https://launchpadlibrarian.net/151506228/buildlog_ubuntu-saucy-amd64.unity8_7.81.3%2B13.10.20130926-0ubuntu1_FAILEDTOBUILD.txt.gz
[08:11] <asac> didrocks: http://people.canonical.com/~ogra/touch-image-stats/20130925.1.changes
[08:11] <asac> there are ui-toolkit changes in that one
[08:11] <ogra_> ah
[08:11] <didrocks> asac: yeah
[08:11] <didrocks> so possibly toolkit regressed those notes-app
[08:12] <asac> maybe we need jibels page also project what a release changelog would look like against last current
[08:12] <asac> :)
[08:12] <didrocks> Mirv: mind poking the sdk guys with that failing tests?
[08:12] <Mirv> vila: true, and handling missing dependencies is not detected at the moment well, it just waits building
[08:12] <didrocks> Mirv: http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4443/notes-app-autopilot/
[08:12] <asac> didrocks: notes app has traditionally been flaky
[08:12] <asac> have you checked with psivaa if he retried?
[08:12] <asac> psivaa: ^^
[08:12] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4443/
[08:13] <Mirv> didrocks: I actually did in the morning, and they analyzed it and came into conclusion that it's not toolkit but everything related to 'tapping' so maybe more low-level
[08:13] <Mirv> didrocks: I then also noticed that in the landing plan it says ui-toolkit landed in 65, while the regressions started in 64
[08:13] <Mirv> so maybe mir upgrade then?
[08:13] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4441/ notes app was still ok on the .1 build
[08:13] <vila> Mirv: thanks, vila.sanity++, sanity is good, we want moar ;)
[08:13] <asac> i really believe its a retry thing
[08:13] <asac> psivaa: ^^ :)
[08:14] <didrocks> Mirv: hum, right
[08:14] <Mirv> asac: not on maguro though
[08:14] <didrocks> or maybe just flackiness, I don't see apart from the lxc config I don't know about, what can impact on 65
[08:14] <Mirv> and there's rssreader failure on both starting from 64, plus calendar failure on maguro starting from 64
[08:15] <popey> ogra_: yo
[08:15] <popey> ogra_: we releasing
[08:15] <popey> ?
[08:15] <ogra_> popey, hey, yeah
[08:15] <ogra_> gimme a sec
[08:15] <popey> kk
[08:17] <ogra_> k, should be publishing
[08:17] <popey> i see it already on my device
[08:17] <popey> 65 right?
[08:17] <popey> and it's auto-downloaded already
[08:17] <popey> man this is great!
[08:18] <asac> what are you looking for?
[08:19] <ogra_> popey, right, 25.2/65 was released
[08:20] <seb128> hey
[08:20] <didrocks> hey seb128
[08:20] <didrocks> sil2100: hey, around? feeling better today?
[08:20] <seb128> can someone add system-settings to the landing board? or do I need to wait on Jason to be up at my end of day,
[08:20] <seb128> ?
[08:20] <seb128> didrocks, hey ;-)
[08:21] <ogra_> we take bribes
[08:21] <seb128> lol
[08:21] <asac> seb128:  you are supposed to have acceess so you can add your own asks
[08:21] <asac> seb128: i shared it with you now
[08:21] <seb128> asac, I didn't, let me try again
[08:21] <sil2100> didrocks: morning, still feeling bad, but not bad enough for coding ;)
[08:21] <didrocks> sil2100: I think we'll need you for some landing today ;)
[08:21] <lool> didrocks: mir >> it's great to see that there are as many changes in code as in tests, but oh $DEITY the amount of code changes  :-)  can't review the ABI changes I'm afraid
[08:22] <seb128> asac, that works now, thanks! ;-)
[08:22] <lool> didrocks: so how do you handle the package renames exactly?  did you preNEW them already?
[08:22] <sil2100> didrocks: please feel free to add me to some tasks, and I'll do those whenever possible ;)
[08:22] <didrocks> lool: package rename? are you on the multimedia stuff?
[08:22] <lool> didrocks: no, mir
[08:22] <vila> oh please someone ! What does preNEW mean ???
[08:22] <didrocks> sil2100: please come to the HO meeting
[08:22] <lool> libmirserver3 -> libmirserver4
[08:22] <didrocks> lool: wait for the meeting, will be easier ;)
[08:23] <didrocks> right now, I'm trying to unblock Mir FTBFS
[08:23]  * lool checks PPA
[08:24]  * lool checks #ubuntu-mir
[08:24] <vila> didrocks, lool: What does preNEW mean ?
[08:24] <popey> ogra_: asac mail sent
[08:24] <vila> it's an irritating blind spot ;)
[08:24] <asac> popey: about what?
[08:24] <popey> 65
[08:24] <asac> why do we release it with regressions?
[08:25] <asac> ogra_: didrocks: ^?
[08:25] <didrocks> yeah, we shouldn't as there is those apps test failing
[08:25] <popey> gah
[08:25] <asac> we dont release with regressions
[08:25] <didrocks> (which mail was sent?)
[08:25] <ogra_> asac, which regressions ?
[08:25] <asac> notes app
[08:25] <didrocks> popey: did you try the notes app AP tests manually?
[08:25] <popey> no.
[08:25] <didrocks> are they flacky tests or reproducible issues?
[08:25] <asac> right
[08:25] <didrocks> can you try that please?
[08:25] <asac> we cant continue until we know
[08:25] <didrocks> so that we can assess
[08:26] <ogra_> gah, sorry
[08:26] <sil2100> vila: preNEW is basically a 'review' that an archive admin needs to do of a new package, ending with a thumbs up from that admin
[08:27] <popey> running now
[08:27] <lool> vila: it's because the automated archive copying we're doing bypasses the normal processes
[08:27] <lool> vila: so when we have new binary or source packages, some archive admin should review them before they get automatically in
[08:28] <vila> lool, sil2100: thanks ! archive or -proposed ?
[08:29] <lool> vila: they get into proposed
[08:29] <lool> but not to binary new
[08:29] <lool> IIRC
[08:29] <vila> lool: thanks, one blind spot down, there are N blin spots on the wall... Hey ho !
[08:29] <lool> vila: normally, new sources and new binaries uploaded by a developer or a human get stuck into the archive NEW queue
[08:30] <lool> but IIRC, the way we're copying them it bypasses binary NEW
[08:30] <vila> lool: archive admin == ubuntu dev ?
[08:30] <lool> no
[08:30] <lool> archive admin is like an über-elite secret club of people that can rm -rf launchpad
[08:30] <lool> j/k
[08:30] <psivaa> asac: sorry just saw the message :), notes is a consistent failure
[08:31] <asac> right
[08:31] <asac> ogra_: so please try to remove the 56 build from release channel
[08:31] <lool> vila: essentially a set of people with deep understanding of how archive works, and with access to special host to do maintenance tasks such as accepting packages, creating new releases etc.
[08:31] <vila> lool: hmm, so, infinity, didrocks, yourself ?
[08:31] <vila> lool: ok, names please ;)
[08:31] <lool> I'm not archive admin
[08:31] <lool> https://launchpad.net/~ubuntu-archive
[08:32] <vila> puuurfect
[08:32] <asac> psivaa: we have 3 failures on mako
[08:32] <asac> psivaa: we have 1 failyre on maguro... doesnt sound very consitant
[08:32] <didrocks> asac: joining?
[08:32] <ogra_> asac, i'm a bit scared that everything explodes then
[08:32] <vila> lool: much much clearer :)
[08:32] <asac> ogra_: well. we have to learn
[08:32] <asac> lets talk in a second
[08:32] <psivaa> asac: yea, i was talking about the info from last night.. let me retry :)
[08:32] <ogra_> yeah
[08:32] <vila> lool: there are a few names I should be able to bride there ;)
[08:33] <lool> vila: it's kind of orthogonal to developer membership, since these are different tasks, but I guess the levels of trust and understanding of archive / packages goes up from MOTU, to core dev to archive admin
[08:33] <vila> lool: received loud and clear, thanks ;)
[08:33] <popey> asac: ogra_ all the tests that failed on jenkins, succeeded on my device locally
[08:34] <ogra_> yeah the notes app ones are really random
[08:34] <ogra_> not the same across the devices
[08:35] <lool> vila: can you do something about upstream merges not being processed for music-app?
[08:35] <lool> vila: https://code.launchpad.net/~lool/music-app/singleton/+merge/187583
[08:36] <cjwatson> lool: not quite right - they still land in NEW, although a bit differently (there are some problems, but I don't think those problems are why preNEW exists)
[08:36] <asac> popey: did all tests succeed?
[08:37] <cjwatson> lool: AIUI the problem is that if cu2d copies something then the workflow expects that it will appear in the archive before *too* long, and things can get a bit confused if it sits there for ages
[08:37] <cjwatson> lool: so preNEW is to try to make sure that the actual NEW check doesn't take too long
[08:37] <popey> asac: ran it 3 times, same result each time http://paste.ubuntu.com/6157852/ http://paste.ubuntu.com/6157871/ http://paste.ubuntu.com/6157875/
[08:37] <cjwatson> lool: (also NEW for copies is harder to review than it ought to be - I have some LP bugs to fix)
[08:37] <lool> ok
[08:38] <vila> lool: not now as I would have to dig to find where somthing can be triggered without knowing if I will have to trigger so -> vila.TODO++ ^
[08:38] <vila> meh
[08:38] <cjwatson> vila: ~ubuntu-archive would be a strict subset of ~ubuntu-core-dev if we hadn't been forced to make it otherwise by past management
[08:38] <popey> asac: (and different from jenkins)
[08:38] <cjwatson> vila: hopefully we'll get back to that again though
[08:38] <vila> lool: not now as I would have to dig to find where something can be triggered without knowing if I will have the right access to trigger so -> vila.TODO++ ^
[08:38] <asac> popey: you have to unlock a screen
[08:38] <cjwatson> hey, actually, maybe it is a subset again now
[08:38] <popey> asac: i did
[08:38] <cjwatson> (aside from the robot)
[08:39] <lool> can we make the robot a core dev?
[08:39] <lool> would help a lot
[08:39] <vila> cjwatson: thanks, also lool's 'kind of orthogonal to developer membership' made sense to me
[08:39] <cjwatson> lool: why?
[08:39] <lool> quite obviously robots are more productive than humans
[08:39] <cjwatson> :-)
[08:39] <lool> they complain less
[08:39] <lool> work crazy hours^W^W^W actually we do that
[08:40] <vila> :-D
[08:40]  * vila goes dark a bit to concentrate on some stuff
[08:41] <popey> asac: and again... same http://paste.ubuntu.com/6157890/
[08:41] <asac> popey: do you manually unlock the screen?
[08:41] <asac> before?
[08:41] <asac> you need to do that for apps
[08:42] <asac> check https://wiki.ubuntu.com/Touch/Testing#Testing_your_Ubuntu_Touch_Code_before_submission
[08:42] <popey> yes
[08:42] <asac> but guess u know
[08:42] <popey> hence 09:38:55 < popey> asac: i did
[08:42] <asac> sry
[08:42] <popey> np ☻
[08:45] <dpm> hi psivaa, it seems that the Jenkins jobs for core apps are not running again. Could you give us a hand reactivating them? Here's one example of a MP where Jenkins is not running https://code.launchpad.net/~vthompson/music-app/fix-spacing-issues/+merge/187659
[08:45] <asac> popey: try rebooting and start from fresh state :)
[08:45] <asac> give us a 100% :)
[08:45] <popey> asac: hah, okay ☻
[08:45] <psivaa> dpm: let me take a look
[08:46] <dpm> thanks :)
[08:55] <popey> asac: http://paste.ubuntu.com/6157927/ different this time ☹
[08:56] <psivaa> dpm: it looks like the jenkins instance itself is down (http://91.189.93.70:8080/). we need retoaded or fginther for that.
[08:56] <psivaa> :(
[08:57] <dpm> psivaa, ok, will have to wait until they come online, then. Thanks for your help
[08:58] <psivaa> dpm: i'll dig in in the mean time if i could  restart that jenkinsm but i doubt if i'll be able to
[08:58] <psivaa> asac: notes app have been tried 4 times now on mako - 2,3,2,2 failures on maguro 1,1,2,1 failures
[08:58] <popey> asac: http://paste.ubuntu.com/6157941/ can't get a 100% pass
[08:58] <dpm> psivaa, perhaps someone on #is could?
[08:58] <psivaa> dpm: good point :)
[09:07] <psivaa> dpm: you might have seen the response from the is about that in #is
[09:10] <dpm> psivaa, yes, thanks for following that up. Would it be possible to give access to the Jenkins instance to someone that's not only in US-like time? It would help us with not having to wait until fginther comes online
[09:10] <psivaa> dpm: agreed, i have the access to jenkins instance but not to the host.. requesting one now
[09:11] <dpm> excellent, thanks!
[09:16] <ogra_> grmbl, my mako is dead
[09:25] <dpm> hi asac, I've got a MP enabling translations for the rss reader app. I've had to rename some files and fix some paths from ubuntu-rssreader-app to rssreader-app, and while at it, I renamed the package too, something pmcgowan asked us to do for all core apps a while ago anyway, but that has been a low priority. This will mean coordinating this change with the package rename in the seeds if I understand it correctly.
[09:25] <dpm> Shall I go ahead with the package name change in the MP + seed change MP, or is it better to just stick to the current package name at this point?
[09:28] <didrocks> Mirv: do you have time now?
[09:29] <didrocks> dpm: can you file a landing asks please (detailing all the changes that needs to be done in coordination)
[09:29] <sil2100> hmmm
[09:29] <didrocks> sil2100: everything's fine on the apps side (and Mir is still building u-s-c)
[09:30] <sil2100> didrocks: regarding webbrowser-app and the other apps that I am to release - what's with SDK?
[09:30] <sil2100> didrocks: since I just wanted to test webbrowser-app on my new image and it wants to pull in qtdeclarative5-ubuntu-ui-extras-browser-plugin from today
[09:30] <didrocks> sil2100: ah, latest sdk is needed?
[09:30] <sil2100> didrocks: webbrowser-app : Depends: qtdeclarative5-ubuntu-ui-extras-browser-plugin (= 0.22+13.10.20130926.1-0ubuntu1)
[09:30] <didrocks> sil2100: ok, can you try the sdk as well then? (and run all AP tests)
[09:31] <sil2100> didrocks: will do
[09:31] <didrocks> thanks ;)
[09:31] <didrocks> sil2100: that way, you will confirm notes-app as well
[09:31] <didrocks> (before and after)
[09:31] <dpm> didrocks, sure, I'm just asking if it makes sense before I do that. But if it's better to just file a landing ask directly, happy to do that
[09:32] <Mirv> didrocks: just tell
[09:32] <didrocks> dpm: yeah, please do, I think we'll target that after the Mir landing
[09:32] <didrocks> Mirv: hangout? will be easier I guess (it's for the renaming they are doing for qtmultmedia)
[09:32] <dpm> didrocks, ok, cool, thanks
[09:32] <Mirv> sil2100: the browser plugin comes from webbrowser-app itself
[09:32] <Mirv> didrocks: ok
[09:33] <didrocks> sil2100: ah, so not latest sdk :p
[09:33] <asac> dpm: check with didrocks
[09:33] <dpm> asac, yep, just done that and will file a landing ask, thanks
[09:34] <didrocks> Mirv: https://plus.google.com/hangouts/_/bfff3f6c1356693567d8fddc5805b21b8a1cff4b?hl=fr
[09:34]  * ogra_ sighs 
[09:34] <ogra_> i cant get my mako installed
[09:37] <dpm> didrocks, could you give me write access to the spreadsheet to file a landing ask?
[09:37] <sil2100> didrocks, Mirv: hm?
[09:37] <sil2100> didrocks, Mirv: so what about SDK then?
[09:37] <didrocks> dpm: sure, doing
[09:37] <didrocks> sil2100: no sdk ;)
[09:37] <didrocks> just apps then
[09:39] <sil2100> didrocks: but webbrowser-app forces SDK upgrade?
[09:40] <Mirv> sil2100: I mean, 'qtdeclarative5-ubuntu-ui-extras-browser-plugin' is not SDK
[09:40] <Mirv> sil2100: it comes from webbrowser-app
[09:40] <didrocks> sil2100: qtdeclarative5-ubuntu-ui-extras-browser-plugin is grabbing Source: webbrowser-app
[09:40] <popey> ogra_: wassup with it?
[09:40] <sil2100> Ah
[09:40] <sil2100> Ah ah
[09:40] <didrocks> does qtdeclarative5-ubuntu-ui-extras-browser-plugin forces latest sdk?
[09:40] <Mirv> sil2100: :)
[09:40] <ogra_> popey, hangs at "< waiting for device >
[09:40] <ogra_> downloading 'boot.img'..."
[09:40] <Mirv> didrocks: no, it doesn't have a version specific dependency on the SDK
[09:40] <sil2100> Ah ah ah
[09:40] <sil2100> ;)
[09:41] <didrocks> ok, we're fine then, red alert down!
[09:41]  * didrocks updates landing plan
[09:41] <didrocks> thanks Mirv, sil2100
[09:42] <sil2100> It seems my head is still not clear enough
[09:42] <didrocks> sil2100: no worry!
[09:43] <didrocks> lool: music-app is a click package, isn't it?
[09:44] <ogra_> sigh sigh sigh
[09:45] <didrocks> ogra_: what's up? don't cry ;)
[09:45] <asac> ogra_: maybe popey can help by downgrading?
[09:45] <ogra_> didrocks, my mako doesnt install anymore :(
[09:45] <asac> popey: we try to find what caused the regression on notes-app... ogra wanted to try downgrading ubuntu-keyboard
[09:45] <didrocks> asac: +1
[09:45] <popey> i can
[09:46] <asac> popey: we feel its caused by one of these: http://people.canonical.com/~ogra/touch-image-stats/20130925.2.changes
[09:46]  * ogra_ still wants his mako back 
[09:47] <didrocks> ogra_: no red light at all?
[09:47] <asac> ogra_: 10 minutes
[09:47] <ogra_> didrocks, it works fine, it just cant transfer boot.img
[09:47] <asac> was the time you need to press the button
[09:47] <ogra_> asac, it runs, i can even boot into the former image 50something that is installed
[09:47] <ogra_> fastboot mode doesnt work
[09:48] <ogra_> or rather transferring anything in fastboot mode
[09:48]  * ogra_ puts it on charger for 1h ... even though its over 50% full
[09:48] <popey> where does ubuntu-keyboard-data come from?
[09:48] <popey> I found ubuntu-keyboard
[09:49] <popey> https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/5035448
[09:49] <asac> popey: no clue :)
[09:49] <ogra_> popey, https://launchpad.net/ubuntu/saucy/+source/ubuntu-keyboard
[09:50] <asac> popey: Source: ubuntu-keyboard
[09:50] <ogra_> just grab it from lp
[09:50] <asac> so its coming from same source
[09:50] <popey> ok
[09:50] <ogra_> bah
[09:50] <ogra_> so i can select stuff on screen in fastboot mode ... but "power as enter" is completely ignored
[09:50]  * asac installs the previous build as we already see a notes-app failure there on maguro
[09:51] <asac> maybe its something still fishy or racy with image production
[09:51] <asac> :)
[09:51] <asac> or how utah uses them
[09:51] <ogra_> http://paste.ubuntu.com/6157994/
[09:51] <popey> got it
[09:51] <ogra_> thats the result i got over and over on maguro
[09:51] <ogra_> (i did 5 runs)
[09:52] <asac> ogra_: did you try 54?
[09:52] <asac> that one failed in utah as well... maybe we look at the wrong changeset
[09:52] <ogra_> 54 runs ?!?
[09:52] <popey> hah
[09:52] <popey> i suspect he means image 54 ☻
[09:52] <asac> popey: worked?
[09:52] <ogra_> heh
[09:52] <ogra_> no, i didnt
[09:52] <asac> 64
[09:52] <popey> asac: just running tests now
[09:52] <asac> ogra_: http://people.canonical.com/~ogra/touch-image-stats/20130925.1.changes is suspicious
[09:52]  * ogra_ still wrangels with his mako
[09:52] <asac> and maguro failing on that is more so :)
[09:53] <asac> it has ui-toolkit
[09:53] <popey> bah, booted with sensorservice eating the cpu
[09:53] <dpm> didrocks, have you had the chance to look at the write permissions for the landing spreadsheet?
[09:53] <ogra_> asac, so you meant 64 above ?
[09:53]  * popey reboots again
[09:53] <ogra_> not 54
[09:53] <didrocks> dpm: sorry, done, refresh now
[09:53] <asac> ogra_: did you add a new landing plan entry?
[09:53] <ogra_> asac, yes 41 iirc
[09:54] <asac> ogra_: didnt we say we do that during meeting?
[09:54] <dpm> looking good, thanks didrocks!
[09:54] <asac> just reminding
[09:54] <asac> thx
[09:54] <ogra_> asac, oh, that was 1h before the meeting
[09:54] <ogra_> i added two last night (already landed) and one this morning before the meeting
[09:55] <asac> all good then. thx
[09:55] <sil2100> didrocks: apps seem fine, can I publish?
[09:56] <didrocks> sil2100: sure, if all AP tests pass, please do! (no packaging change for me to review?)
[09:57] <sil2100> didrocks: I see the apps stack is blinking though!
[09:57] <didrocks> sil2100: argh, rebuilding?
[09:57] <sil2100> didrocks: it seems so, not sure why since platform still didn't run even - waiting on mir o_O
[09:58] <didrocks> sil2100: building or waiting?
[09:58] <sil2100> didrocks: check job blinking
[09:58] <didrocks> sil2100: if it's waiting, you can publish the previous state
[09:58] <sil2100> didrocks: it's doing autopilot tests on it
[09:59] <popey> asac: ogra_ http://paste.ubuntu.com/6158106/  100% pass with downgraded ubuntu-keyboard and ubuntu-keyboard-data
[09:59] <ogra_> popey, so seems we have the bad package :)
[09:59] <asac> popey: awesome
[09:59] <asac> didrocks: ^^
[09:59] <sil2100> didrocks: aaaand the AP machines are stuck...
[09:59] <asac> popey: can you run three times please?
[09:59] <asac> :)
[09:59] <didrocks> sil2100: ok, please check the diff ;)
[09:59] <popey> already doing ☻
[09:59] <didrocks> asac: popey: \o/
[09:59] <asac> popey: then we back out
[09:59] <asac> popey: maybe do it a second time... just to be sure :)
[10:00] <didrocks> sil2100: for the new stuff if new commits entered while you were testing
[10:00] <asac> that we are not on a lucky streak
[10:00] <asac> oh wait plz
[10:00] <asac> for my test on 64
[10:00] <asac> thats where we had notes-app failures on maguro as well
[10:00] <sil2100> didrocks: actually I was testing the new version already ;p So it's fine
[10:00] <sil2100> I'll abort the check job
[10:00] <didrocks> sil2100: ah great! ;)
[10:00] <asac> but i guess we can already backout ubuntu-keyboard if popey can confirm
[10:00] <ogra_> so how do we do that ?
[10:00] <ogra_> :)
[10:00] <didrocks> asac: do you have the 64 failing link?
[10:01] <sil2100> didrocks: http://10.97.0.1:8080/job/cu2d-apps-saucy-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_webbrowser-app_0.22+13.10.20130926.1-0ubuntu1.diff <- a REALLY cosmetic change ;)
[10:02] <popey> http://paste.ubuntu.com/6158115/ second 100% pass
[10:02] <asac> didrocks: http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4442/
[10:02] <asac> didrocks: might be just flakiness on that one... trying to check that
[10:03] <didrocks> asac: yeah, not the same value (and we saw that test failing in the past IIRC, but not 100% sure)
[10:03] <asac> i guess its a flaki one
[10:03] <didrocks> sil2100: +1
[10:03] <asac> its the same we saw on 65
[10:03] <asac> and i couldnt repro that locally
[10:03] <didrocks> sil2100: a cosmetic but good one :p
[10:03] <asac> but it always happens in utah, which is scary
[10:03]  * asac dist-upgrades phablet-tools
[10:03] <asac> maybe phablet-tools upgrade yesterday broke it :)
[10:03] <asac> lol
[10:03] <didrocks> revert phablet-tools!
[10:03] <asac> sounds unlikely :)
[10:03] <didrocks> ;)
[10:05] <popey> http://imgur.com/lgXFGg3  <- asac right now
[10:05] <ogra_> haha
[10:05] <asac> lol
[10:05] <asac> kick out everything
[10:05] <asac> no more bugs to worry about
[10:05] <didrocks> ok, let's revert
[10:05] <asac> lets start with all those core apps that look so unhappy on the dashboard
[10:05] <asac> hehe
[10:05] <asac> didrocks: gogogog
[10:05] <asac> :)
[10:05] <asac> push
[10:05] <asac> kill
[10:05] <asac> :)
[10:06] <didrocks> popey: meanwhile, do you mind opening a bug?
[10:06] <didrocks> so that I reference it for them?
[10:06] <asac> didrocks: remember to file a bug and send it to bfiller
[10:06] <popey> http://paste.ubuntu.com/6158123/ booo had a failure
[10:06]  * popey reboots and tries again
[10:06] <asac> i did that for backouts... people hated us if we do that without a bug and notification and i agree thats pretty harsh :)
[10:06] <didrocks> asac: pffff, you are so slowwwww ;)
[10:06] <popey> didrocks: sure thang!
[10:06] <asac> didrocks: already done?
[10:06] <asac> :)
[10:06] <asac> ah
[10:06] <didrocks> asac: 12:06:02 didrocks | popey: meanwhile, do you mind opening a bug
[10:07] <asac> didrocks: yeah. but please send it explicitly to bfiller by a mail
[10:07] <asac> important enough to ensure he knows
[10:07] <didrocks> will do
[10:07] <lool> didrocks: music-app is built as a click package somewhere, but isn't yet a click package in the image
[10:07] <didrocks> I'll reference in the commit as well
[10:07] <lool> didrocks: there was a breakthrough on the way to making it one though
[10:07] <asac> just make a default candidate: "Heads up about your backout of ubuntu-keyboard"
[10:07] <didrocks> lool: ok
[10:07] <asac> err default template
[10:07] <asac> :)
[10:07] <lool> didrocks: for now, it's from the coreapps-drivers PPA
[10:07] <didrocks> lool: that's why I didn't find it
[10:08] <ogra_> can someone trigger a build for mtp ?
[10:09] <asac> ogra_: so... where is the lightdm change?
[10:09] <asac> you think we can see if we have all the pieces together for the afternoon?
[10:09] <ogra_> asac, on my testing plan for today
[10:09] <asac> as an option if MM is not coming along
[10:09] <didrocks> I planned it for build 67
[10:09] <lool> ogra_: looking
[10:09] <didrocks> not 66 ;)
[10:09] <ogra_> beyond that lightdm is in proposed
[10:09] <asac> right
[10:09] <asac> didrocks: 66 is the next we cut after recovery of ubuntu-keyboard and mir, right?
[10:09] <ogra_> didrocks, heh, thats optimistic
[10:09] <asac> didrocks: 67 is the one we start prepping in the afternoon
[10:09] <asac> right?
[10:10] <didrocks> asac: yep
[10:10] <asac> ogra_: yeah... get your act totgether on teseting that
[10:10] <ogra_> asac, thats what i planned for today :)
[10:10] <asac> ogra_: i think thats the single biggest contribution you can do for th eworld on this thursday :) lol
[10:10] <didrocks> asac: 66 will have apps as well
[10:10] <didrocks> (safe things)
[10:10] <popey> didrocks: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1231356
[10:10] <lool> ogra_: it seems to be in PPA already
[10:10] <lool> ogra_: r33
[10:10] <ogra_> lool, what exactly ?
[10:10] <ogra_> oh, mtp
[10:10] <didrocks> thanks popey
[10:10] <asac> ogra_: then why are you still answering my pings :)? lol
[10:10] <asac> ok thanks
[10:10]  * didrocks opens thunderbird compose
[10:10] <ogra_> awesome
[10:11] <ogra_> so mtp can go into 66 ... i'll upload lxc-android-config too with the upstart fixes
[10:12] <lool> didrocks: and for coreapps, who's running the bzr trunk -> PPA stuff?
[10:12] <lool> didrocks: (I guess the upstream merger part stops when it's in bzr trunk)
[10:12] <didrocks> lool: I don't know TBH
[10:13] <lool> lol
[10:13] <lool> never thought I'd read that
[10:13] <didrocks> lool: I think it's a dholbach thingy
[10:13] <lool> ok
[10:13] <didrocks> ahah, sorry to disappoint you ;)
[10:13] <asac> lool: thats a separate jenkins
[10:13] <asac> afaik
[10:13] <lool> asac: of course!  why not!  it's not like we have enough jenkinses!  :-)
[10:14] <asac> lool: it is a security concern things
[10:14] <asac> thing
[10:14] <didrocks> ogra_: hum, 67 is set for mtp, let's try to not push too much on 66
[10:14] <lool> fair enough
[10:14] <asac> lool: its painful... i think we need to introduce at least another layer
[10:14] <ogra_> didrocks, well, i'd like to keep 67 as clean as possible for MM stuff
[10:14] <asac> so we can at least stage and guard those things
[10:14] <lool> asac: one jenkins to rule them all?
[10:14] <lool> and in the darkness bind them?
[10:14] <asac> they currentlyfly in completely untested
[10:14] <didrocks> ogra_: yeah, but maybe we'll rebuild 66 before the end of beta freeze
[10:15] <lool> asac: yeah, well if they become click the problem "goes away" in a way
[10:15] <didrocks> infinity: do you have any estimate on the end of the beta freeze?
[10:15] <ogra_> didrocks, MM isnt affected by beta freeze
[10:15] <ogra_> thats why i wanted it in today so all the proposed cruft is left out
[10:15] <didrocks> ogra_: right, but we'll have a flow of things coming in after the beta freeze
[10:15] <asac> lool: right. but even there we dont have a real CI story. we just know there is a staging place where we review and wherew we could run these test,  but remember that fixing the future will never fix the present :-P.
[10:15] <didrocks> if we can get an image before with those fixes + Mir
[10:15] <lool> ogra_: is qtmultimedia itself in alreadY?
[10:15] <asac> :)
[10:15] <infinity> didrocks: Very soon.
[10:15] <didrocks> that would be great
[10:15] <ogra_> didrocks, exactly
[10:16] <lool> ogra_: that's used by kubuntu
[10:16] <didrocks> hum, ok, I think it's going to be a fail then, to only have fixes + Mir ;)
[10:16] <didrocks> infinity: ok, thanks
[10:16] <infinity> didrocks: I pre-published already, but won't commit for sure until I'm ready to push all the flavours.
[10:16] <ogra_> lool, -touch ... -touch :)
[10:16] <ogra_> lool, it is forked, nobody uses it
[10:16] <lool> ogra_: well they also wanted to update qtmultimedia after all
[10:16] <didrocks> infinity: ok, thanks for the head's up
[10:16] <lool> ogra_: we do
[10:16] <didrocks> so I guess that will change our plan for image producing
[10:16] <ogra_> lool, nobody but us
[10:16] <didrocks> sil2100: how is the Mir thing going?
[10:16] <lool> ogra_: qtmultimedia is used by kubuntu
[10:17] <ogra_> lool, yes, and ? the changes aare in since days
[10:17] <asac> yeah. we need to coordinaqte with them i guess :/
[10:17] <infinity> didrocks: If you're holding up on landing things in proposed though, please do upload freely, so all your autopackagetesting and such happens.  Then it'll all just slide in when I remove the blocks.
[10:17] <ogra_> lool, there is nothing to upload for qtubuntu
[10:17] <asac> so yeah. go all in on lightdm, i feel this mm thing will take longer than a couple hours :-P
[10:17] <ogra_> err
[10:17] <ogra_> qtmultimedia
[10:17] <asac> isnht?
[10:17] <lool> ogra_: no, qtmultimedia is still at 5.0.2
[10:17] <asac> ok... thats better
[10:17] <ogra_> lool, err
[10:17] <didrocks> infinity: we are not holding up at all, we are just trying to mitigate with the flowed of things from -proposed and what we upload
[10:17] <asac> still waiting for rsalveti to show up and tell us that its all good to go
[10:18] <ogra_> lool, i dont think qtmultimedia was planned to be anything else
[10:18] <didrocks> qtmultimedia stays as it is
[10:18] <ogra_> lool, only touch will use 5.1
[10:18] <didrocks> we have the forked version then
[10:18] <ogra_> right
[10:18] <lool> a couple of days ago I read in email that we wanted to update it to 5.1 too
[10:18] <ogra_> the most ugly package i have seen in years
[10:18] <lool> so that qtmultimeda-touch and qtmultimedia have the same base version
[10:19] <didrocks> lool: they won't, I checked again with Mirv
[10:19] <lool> BTW keep in mind we build against qtmultimedia and we run against qtmultimedia-touch
[10:19] <ogra_> lool, we do ... -touch is 5.1 and diverts all .so files of 5.0
[10:19] <lool> didrocks: ok; seems risky both ways
[10:19] <lool> ogra_: yeah, but that was considered risky a couple of days ago
[10:19] <asac> did we revert yet :)?
[10:19] <lool> but I guess they didn't get the FFE for 5.1 qtmultimedia
[10:19]  * lool lunch &
[10:19] <seb128> hum
[10:19] <ogra_> lool, i wasnt involved with the packaging, i just knmow whats to land :)
[10:19] <didrocks> lool: it's not, qt 5.1 basically breaks unity8
[10:20] <asac> https://launchpad.net/ubuntu/+source/ubuntu-keyboard
[10:20] <didrocks> nobody succeeded in fixing all those in a month
[10:20] <didrocks> so, let's move on ;)
[10:20] <seb128> didrocks, asac, ogra_: the content-hub udpate from yesterday seems buggy, is that a known issue? we can't select a background in system settings anymore (it works if content-hub is downgraded)
[10:20] <ogra_> seb128, no, not known
[10:20] <seb128> shrug
[10:20] <ogra_> asac, ^^^
[10:20] <asac> seb128: we can better protect you if you automate that test
[10:21] <asac> lets see
[10:21] <ogra_> seb128, seems we're missing a system-settings-autopilot test here
[10:21] <didrocks> seb128: not known, was explicitely tested by sil2100 IIRC
[10:21] <seb128> asac, noted, having more tests is overdue anyway
[10:21] <asac> its super important
[10:21] <seb128> ogra_, indeed
[10:21] <asac> because of this reason
[10:21] <seb128> well, suck to be us
[10:21] <seb128> we are a few guys who didn't know about qt or the toolkit a few months back
[10:21] <seb128> with nobody to help us to set up testing or anything
[10:22] <seb128> so we do what we can, but we still learn/struggle
[10:22] <asac> seb128: maybe you can try to keep an eye on content-hub commits etc.? guess ken could also ask your team to give peer review on merges
[10:22] <seb128> having help from somebody in QA to get us started would be nice
[10:22] <asac> seb128: also... maybe help ogra prepping and checking the lightdm thing
[10:22] <asac> if thats good enough for you
[10:22] <seb128> I'm happy to do that
[10:23] <asac> no need to wait till its in the image before going back to mterry about bugs
[10:23] <asac> ogra_: can you prep some debs so that other people can tests?
[10:23] <seb128> right
[10:24] <seb128> I wanted to test that today
[10:24] <asac> didrocks: ogra_: who is doing the backout :)? /me checks if there was a landing plan entry giving ownership
[10:24] <seb128> but I also need to /etc ro mess to be fixed for the tz selection
[10:24] <didrocks> asac: it's building
[10:24] <ogra_> asac, didrocks
[10:24] <didrocks> I'll handle it
[10:24] <didrocks> let me add it to the landing plan
[10:24] <asac> ok cool. add alanding entry i gues as well.. just as good practice :)
[10:24] <asac> nice
[10:25]  * didrocks waits for sil2100 on Mir ;)
[10:29] <seb128> didrocks, ogra_, asac, sil2100: opened https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1231368 about the regression (and pinged gusch, Ken on vac for a few days)
[10:29] <didrocks> seb128: ok, thanks, keep us updated
[10:29] <asac> who beyond ken is working on content-hub?
[10:30] <didrocks> asac: gush, as seb128 mentionned
[10:30] <didrocks> gusch*
[10:30] <asac> so wehave a new content-hub staged?
[10:30] <asac> oh no.
[10:30] <asac> not
[10:31] <ogra_> http://people.canonical.com/~ogra/ubuntu-touch/lightdm/
[10:31] <ogra_> for anyone wanting to test the lightdm session
[10:31] <asac> seb128: ^^
[10:31] <asac> ogra_: what do i do?
[10:31] <ogra_> install these two packages and reboot
[10:32] <seb128> ogra_, asac: ok
[10:32] <asac> ok forgot the other thing i was going to do
[10:32] <asac> ogra_: can i also install that on top of 64?
[10:32] <asac> i went back to check the notes-app again
[10:32] <ogra_> asac, shouldnt cause issues
[10:32] <asac> ok i can try right after then
[10:33] <vila> asac: ping, hangout time ;)
[10:35] <sil2100> ACK
[10:38] <didrocks> Mirv: did you advance on the service front?
[10:41] <Mirv> didrocks: (telephony-service, phone stack) no because it failed to build against latest platform, so I was waiting for the stack to proceed to a needed level
[10:42] <didrocks> Mirv: I reran the stack for the keyboard publication
[10:42] <Mirv> hmm, why does 10.97.0.1 not open for me
[10:42] <didrocks> it does here
[10:42] <Mirv> ok, now did, took 25s
[10:42] <sil2100> Sometimes it takes some time
[10:43] <retoaded> psivaa, the jenkins at http://91.189.93.70:8080 is not within the QA lab itself and is not one of the instances I maintain/administer.
[10:43] <didrocks> hey retoaded!
[10:43] <retoaded> didrocks, howdy
[10:44] <didrocks> retoaded: so, we had 2 issues tonight. Seems we still get some DNS issues (Mirv I think can provide some links). It's still address not being recheable from the test machines
[10:44] <didrocks> retoaded: second one is that sometimes the autopilot machine don't have a jenkins slave started
[10:44] <didrocks> retoaded: anyway we can brute force that? To ensure they are always ready and not hanging all the automated process?
[10:45] <Mirv> retoaded: DNS http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-intel/2137/ + http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=qa-nvidia-gtx660/2137/
[10:45] <retoaded> didrocks, ack. am almost finished with the replacement dns/dhcp services; just need to make sure the pxeboot options on the dhcp server are set correctly.
[10:45] <didrocks> retoaded: ok, and on the jenkins slave side? (if a node is down)
[10:46] <sil2100> ogra_: how can I make sure that I'm running Mir on my device?
[10:46] <retoaded> didrocks, as for the jenkins slave not being started, which slaves are not starting properly?
[10:46] <didrocks> retoaded: the autopilot machines mostly
[10:46] <retoaded> didrocks, all three of them?
[10:47] <didrocks> retoaded: well, the 2 we are using the most (intel and nvidia)
[10:47] <retoaded> didrocks, ack
[10:47] <didrocks> retoaded: we have 6 of them btw (3 saucy and 3 raring)
[10:48] <didrocks> sil2100: touch /home/phablet/.display-mir
[10:48] <didrocks> and reboot
[10:48] <ogra_> sil2100, ps ax| grep surface
[10:49] <ogra_> sil2100, that shouldnt return surfaceflinger :)
[10:49] <retoaded> didrocks, ack but only three with autopilot in the hostname correct
[10:49] <ogra_> wow
[10:49] <ogra_> i can select german language with logind working now
[10:49] <sil2100> ogra_: empty, so good ;) But is that good that I can't turn off my screen when using mir?
[10:49] <ogra_> sil2100, known issue
[10:49] <ogra_> poerd
[10:49] <ogra_> *powerd
[10:49] <ogra_> its on the landing plan
[10:49] <didrocks> retoaded: yeah, look at http://10.97.0.1:8080/, the 3 qa-… are autopilot ones as well
[10:50] <retoaded> didrocks, ack
[10:50] <ogra_> lol
[10:50] <ogra_> so switching to german makes the settings app german ... but not the rest of the UI
[10:53] <psivaa> retoaded: ack, so fginther it is then :)
[10:53] <retoaded> psivaa, may be. I can't say for sure since I know nothing about that instance.
[10:54] <Mirv> didrocks: can you pre-ack http://10.97.0.1:8080/view/cu2d/view/Saucy/view/Phone/job/cu2d-phone-saucy-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_telephony-service_0.1+13.10.20130926.1-0ubuntu1.diff so that I can publish it when I've done enough testing?
[10:54] <Mirv> adding of libusermetricsinput1, and both telephony-service and it are in universe
[10:54] <didrocks> Mirv: +1 on preACKing ;)
[10:55] <psivaa> retoaded: ack
[10:55] <ogra_> asac, so in manual testing it seems lightdm improves everything, runnning the test suites now
[10:55] <Mirv> didrocks: thx
[10:55] <didrocks> yw
[11:05] <sil2100> didrocks, ogra_: somehow I'm unable to run unity8 tests when Mir is running
[11:05] <sil2100> ogra_: do I need to do something different?
[11:05] <didrocks> sil2100: phablet-test-run doesn't work?
[11:05] <ogra_> phablet-test-run -n -p unity8-autopilot unity8
[11:06] <ogra_> sil2100, did you use -n ?
[11:13] <didrocks> sil2100: working better that way?
[11:15] <didrocks> seb128: how do I select the timezone?
[11:16] <didrocks> seb128: I pushed "manually", then entered Lyon, I see some results and the keyboard, but pressing the results doesn't do anything?
[11:16] <didrocks> (even hiding the keyboard)
[11:16] <ogra_> didrocks, you cant yet
[11:17] <ogra_> thats still in flight
[11:17] <didrocks> ok, I get no feedback when pressing the cities, that's expected then?
[11:17] <ogra_> pitti and stgraber are still discvussing the best options
[11:17] <didrocks> ok, making sense, thanks :)
[11:17] <sil2100> ogra_: I get a black screen
[11:17] <ogra_> sil2100, ouch
[11:17] <sil2100> ogra_: unity8 gets killed and then the phone remains black :|
[11:18] <ogra_> it should start a new instance
[11:18] <ogra_> in test mode
[11:19] <sil2100> Not this time
[11:19] <sil2100> :D
[11:19] <ogra_> i fear you have to ask in #uubuntu-mir for more details, i dont know if anything special is required in the Mir case, the above used to work
[11:19] <didrocks> Saviq: did you try running the AP test with unity8 running on Mir? ^
[11:19] <didrocks> sil2100: the other tests passed? (the apps ones)
[11:19] <Saviq> didrocks, no, can do now
[11:20] <didrocks> Saviq: please ;) (preferably with the mir version in the daily-build ppa)
[11:20] <Saviq> didrocks, everything from daily-build or just mir?
[11:20] <sil2100> didrocks: some yes, others still running - there's a lot of those
[11:20] <didrocks> so mir + unity-mir + platform-api for touch
[11:20] <didrocks> Saviq: just pick those, you never know what's else in it :)
[11:20] <didrocks> what*
[11:21] <Saviq> didrocks, k, let me just go for a run under surfaceflinger first
[11:21] <didrocks> ok
[11:22] <seb128> didrocks, sorry, I was at lunch
[11:22] <didrocks> seb128: no worry, ogra answered!
[11:22] <seb128> didrocks, yeah, the action doesn't success and you get no feedback
[11:22] <seb128> didrocks, I saw
[11:22] <seb128> didrocks, we should be better at telling what happens though
[11:22] <didrocks> ok, I was just pushing like crazy :)
[11:23] <ogra_> the tz setup uses symlinks ... the ro image setup doesnt really support that
[11:23] <ogra_> so it cant be set on a low level
[11:24] <sil2100> I see now that the other tests have problems as well
[11:24] <didrocks> sil2100: lots of failures?
[11:25] <bregma> so my unity desktop daily failed today because some unit tests failed on the PPC arch -- since when in tarnation did we start building for PPC again?
[11:26] <sil2100> Tests not starting, this is strange but I see dbus-daemon getting defunct
[11:26] <ogra_> hwy is the gallery app test installing Ui toolkit documentaion ?
[11:27] <didrocks> bregma: we never stopped for desktop AFAIK
[11:27] <didrocks> sil2100: did you see some tests passing at least?
[11:28] <sil2100> didrocks: actually, looking at the logs now, it seems he didn't run any of the tests :| All of the test suites failed starting! I'll poke on ubuntu-mir, eh
[11:30] <bregma> didrocks, everything passed except some TestScopeProxy tests, which are known to fail randomly on i386 (sounds like some scope back end fails to run)
[11:30] <bregma> could we rerun the unity build?
[11:30] <didrocks> bregma: in the daily-build ppa?
[11:31] <bregma> yes
[11:31] <didrocks> bregma: it will run again in 2h30
[11:31] <bregma> or force the daily check run despite the PPC failure?
[11:31] <didrocks> bregma: well, if it didn't build, it won't pass -proposed anyway (and will rebuild there)
[11:31] <didrocks> bregma: so better having it in a good shape in the ppa
[11:32] <bregma> we really need the -check logs as soon as possible so we don't waste another day wonder what fresh hell confronts us
[11:33] <didrocks> bregma: the ppc failure didn't block the -check AFAIK
[11:33] <didrocks> bregma: as the -check runs in parallel than the build
[11:33] <didrocks> so if you build passed on i386, you have the -check results
[11:33] <bregma> well, the check didn;t run because the build was marked as failed, and the only failure was the PPC build
[11:33] <didrocks> bregma: are you sure? I doubt about it
[11:33]  * didrocks looks
[11:34] <didrocks> so, -check runs at the same time than bulid
[11:34] <didrocks> build
[11:34] <didrocks> as I was telling
[11:34] <didrocks> and the AP run was http://10.97.0.1:8080/job/autopilot-saucy-daily_release/2138/
[11:34] <didrocks> and it's when we did have the autopilot machine busted
[11:35] <didrocks> but it's not because of the ppc failures
[11:35] <didrocks> (it's when timo killed unity tests)
[11:37] <didrocks> sil2100: ok, confirming
[11:38] <didrocks> ogra_: Saviq: do you know if anyone trying to run those tests with Mir already?
[11:38] <ogra_> didrocks, i weould expect the Mir team to do that before asking for landings
[11:38] <lool> didrocks: qtmultimedia 5.1 breaks unity?
[11:39] <didrocks> lool: qt 5.1 broke unity8
[11:39] <didrocks> that's why we don't land it
[11:39] <lool> didrocks: the original idea was just qtmm, not all of qt (indeed all of qt 5.1 was too much)
[11:39] <lool> hmmm
[11:39] <didrocks> lool: but they went to diverge it as we discussed yesterday
[11:39] <didrocks> for the touch part
[11:39] <didrocks> right?
[11:39] <lool> I'm sure it will come up in the sync HO later today
[11:39] <sil2100> ;/
[11:40] <ogra_> didrocks, and you need the -touch packages to have it working
[11:40] <ogra_> the plain 5.1 packages will indeed break
[11:40] <didrocks> ogra_: I know, I think we had a good plan
[11:40] <didrocks> and we have enough work to do
[11:40] <ogra_> right, we still do
[11:40] <didrocks> not sure why we need to revisit all that again
[11:41] <didrocks> (we have other battles that seems more worrying)
[11:41] <ogra_> not sure why you are testing it
[11:41] <didrocks> ogra_: qt 5.1? I don't
[11:41] <didrocks> sil2100: so, no answer from the Mir team, right?
[11:43] <lool> it's a bit early to give kgunn_ a heads up
[11:43] <lool> but we can in 75 mn or so
[11:44] <sil2100> didrocks: none... but at least they investigate
[11:44] <didrocks> ok, this thing is not on by default
[11:44] <didrocks> it seems that we can play with Mir enabled
[11:44] <didrocks> (manually poking)
[11:44] <sil2100> Will poke around
[11:44] <didrocks> sil2100: a 2 minute one is enough I guess
[11:44] <didrocks> I think it's fine from what I'm trying
[11:45] <didrocks> so, what we need to do, IMHO is:
[11:45] <didrocks> 1. ping/ensure that the Mir team is on this (anyway, that will be a criteria for Mir by default)
[11:45] <didrocks> and 2. publish the current mir+u-s-c+unity-mir+platform-api stacks
[11:45] <didrocks> sil2100: sounds good to you? (can you do that?) ^
[11:46] <sil2100> didrocks: will do! Still playing manually ;)
[11:47] <didrocks> ogra_: ok, ubuntu-keyboard revert is in the release pocket
[11:47] <didrocks> ogra_: what do you think about poking an image? as I guess we won't have next one in the incoming hour
[11:47] <ogra_> should i re-spin ?
[11:47] <didrocks> yeah ;)
[11:47]  * asac installs lightdm finally
[11:47] <Saviq> didrocks, <facepalm> of course I tried to run them
[11:47] <didrocks> Saviq: :p
[11:48] <Saviq> didrocks, https://bugs.launchpad.net/mir/+bug/1226227 and
[11:48] <didrocks> Saviq: so, same than for us?
[11:48] <ogra_> didrocks, asac, lool, image building
[11:48] <Saviq> https://bugs.launchpad.net/qtubuntu/+bug/1226234
[11:48] <didrocks> Saviq: ok, at least, we have a start of tracking
[11:48] <didrocks> thanks ogra_!
[11:48] <ogra_> didrocks, hmm, we should probably have rolled back content-hub too
[11:48] <ogra_> since it has an undetected regression we know about
[11:49] <lool> ogra_: cool
[11:49] <didrocks> ogra_: well, we don't have any tests impacted by that, so, let's see, the feature just went in and reverted
[11:49] <lool> sadly, no music-app, oh well
[11:49] <ogra_> well, not having tests but knowing there is a regression is pretty similar to failing tests imho :)
[11:49] <lool> ogra_: hmm so not waiting for unfreeze?
[11:49] <didrocks> I agree, but upstream is investaging
[11:50] <didrocks> lool: let's get a good image first
[11:50] <ogra_> lool, asac and didrocks wanted to back out the keyboard
[11:50] <lool> oh yeah
[11:50] <lool> +1
[11:50] <didrocks> with notes-app passing
[11:50] <didrocks> then, we will have the one with unfreeze (and I hope mir)
[11:50] <asac> so we have click regression
[11:50] <lool> I didn't have time to look at all into the lightdm thing
[11:50] <asac> some apps dont launch
[11:50] <asac> anyone knew what we landed?
[11:50] <asac> or what is in pipeline?
[11:50] <ogra_> asac, to late ... image builds already
[11:50] <asac> sure
[11:50] <asac> dont want to hold
[11:50] <asac> its not visible in our testing because there are zero tests.
[11:51] <ogra_> yeah
[11:51] <ogra_> same as for content-hub
[11:53] <didrocks> waow, the mir you are using mir, the slower it is it seems
[11:53] <didrocks> sil2100: do you get that impression as well? ^
[11:53] <didrocks> (like opens a bunch of apps and play with them)
[11:54] <sil2100> didrocks: sadly...
[11:55] <sil2100> didrocks: even closing apps doesn't help
[11:55] <didrocks> sil2100: confirmed
[11:55] <didrocks> sil2100: anyway, let's publish it
[11:55] <didrocks> as it doesn't impact the main experience
[11:55] <didrocks> and it's still an improvment to previous Mir
[11:56] <didrocks> (no more flickering indeed)
[11:56] <ogra_> sadly not on maguro
[11:56] <didrocks> ogra_: you do have huge flickering still with latest?
[11:57] <ogra_> maguro never flickered
[11:57] <didrocks> (they mention that some will still be in, not sure about the same)
[11:57] <ogra_> but it got about 50% slower
[11:57] <didrocks> ogra_: mako is slower as well (apart on the first minute of boot)
[11:57] <ogra_> (and it was more than 50% slower than mako before already)
[11:57] <didrocks> at least, people will be able to try it and see
[11:57] <didrocks> so, it's an improvment :p
[11:57] <ogra_> well, scrolling the UI up and down is close to a slideshow
[11:58] <ogra_> before it actually scrolled ... despite being slow
[11:58] <ogra_> and indeed it still crashes the phone hard after 10min
[11:58] <didrocks> I have focus issues on closing apps as well
[11:59] <ogra_> hmm, my lightdm testing doesnt look so well either
[11:59] <ogra_> :(
[11:59] <didrocks> (everytime I close an app another app is coming to the front)
[11:59]  * ogra_ ponders sto restart from scratch 
[12:00] <ogra_> unity8 passes, but i didnt have a single app that passed all tests yet
[12:00] <lool> didrocks: will you send an invite for qtmm sync?
[12:02] <sil2100> didrocks: final ACKs: http://10.97.0.1:8080/view/cu2d/view/Saucy/view/Platform/job/cu2d-platform-saucy-3.0publish/20/artifact/packaging_changes_platform-api_0.19+13.10.20130926.1-0ubuntu1.diff
[12:02] <sil2100> didrocks: the unity8 stack is still running, so I'm not sure if it's safe to publish unity-mir...
[12:02] <didrocks> lool: yeah, I'm trying to see when ricardo will be around, let's see in a couple of hours
[12:02] <sil2100> didrocks: it seems unity8 is building and such
[12:03] <didrocks> sil2100: why is that still running? you did install it without unity-mir?
[12:03] <didrocks> sil2100: ack on platform-api
[12:04] <Saviq> didrocks, so the two bugs above are still valid, so no way to run AP tests on unity8 under Mir
[12:04] <didrocks> Saviq: ok, thanks for the feedback!
[12:11] <ogra_> asac,
[12:11] <ogra_> unity8          - pass
[12:11] <ogra_> mediaplayer-app - 2 failures
[12:11] <ogra_> gallery-app     - 22 failures
[12:11] <ogra_> webbrowser-app  - 31 failures
[12:11] <ogra_> friends-app     - 1 failure
[12:11] <ogra_> camera-app      - 7 failures
[12:12] <ogra_> i think i'll start over with a re-flash
[12:12] <ogra_> asac, thats with lightdm session ... i suspect mterry and cwayne only tried the unity tests
[12:12] <didrocks> urgh, yeah, doesn't look good
[12:13] <ogra_> well, looks good for unity :)
[12:13]  * ogra_ tries to think positive :)
[12:13] <didrocks> heh ;)
[12:14] <didrocks> you should just have pasted the first line!
[12:14] <ogra_> didrocks, the prob here is that the session change enabled polkit
[12:14] <ogra_> didrocks, and nothing ships pkla files to allow *anything*
[12:14] <didrocks> yeah, so a lot of apps are failing against it, surely
[12:14] <didrocks> yep
[12:14] <ogra_> all the apps would have to ship them
[12:14] <ogra_> for what they need to access on dbus
[12:15] <ogra_> not sure how we can solve that without having breakage in for a few days
[12:15] <ogra_> or at least provide an image with the breakage so people have something to work on top
[12:15] <didrocks> hum, because you think that people can't add the plka file without seeing the breakage?
[12:15] <didrocks> like we can have apps shipping the plka files one  by one
[12:16] <didrocks> and once it's all there
[12:16] <didrocks> switch to new lightdm?
[12:16] <ogra_> because it makes it easier to work on it if the system is in the condition it will be after the landing
[12:16] <didrocks> would be nice if we can stage lightdm in a ppa
[12:16] <didrocks> and build a special image for them with that
[12:16] <didrocks> telling "you have 3 days to ship the needed plka files"
[12:16] <ogra_> its already sitting in proposed and wont harm us
[12:17] <didrocks> there is a hint to block it?
[12:17] <ogra_> beta freeze
[12:17] <ogra_> we dotn ship it
[12:17] <ogra_> so dont worry
[12:17] <didrocks> ah, it's just a seed change then
[12:17] <didrocks> (once it landed)
[12:17] <ogra_> ubuntu-touch-session has a dep with the change
[12:17] <ogra_> no seeding needed
[12:18] <didrocks> ok, so shipping this ubuntu-touch-session in a ppa
[12:18] <didrocks> and building an image with that
[12:18] <sil2100> didrocks: hehe, forgot about this one for ACKing before pushing buttons: http://10.97.0.1:8080/view/cu2d/view/Saucy/view/Unity8/job/cu2d-unity8-saucy-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-mir_0.1+13.10.20130926.2-0ubuntu1.diff
[12:18] <didrocks> speaking of polkit… :p
[12:18] <didrocks> sil2100: ok, looking good! +1
[12:19] <ogra_> didrocks, well, once lightdm is in the archive it boils down to a single package ... probably overkill to have a whole image for that
[12:19] <didrocks> ogra_: so giving just instructions to people?
[12:19] <ogra_> (on second thought)
[12:19] <didrocks> like apt-get install lightdm
[12:19] <didrocks> reboot
[12:19] <didrocks> and "please fix"
[12:19] <didrocks> :)
[12:19] <ogra_> right, something like that
[12:19] <didrocks> that sounds good to me
[12:19] <Mirv> asac: didrocks: FYI the previously postponed autopilot has now a fix for its own tests and would be publishable. it's in the landing plan's list after the "end of plan"
[12:20] <didrocks> ogra_: we should plan that, let's discuss it in the HO
[12:20] <ogra_> wget both packages from http://people.canonical.com/~ogra/ubuntu-touch/lightdm/ ... dpkg -i and reboot
[12:20] <didrocks> Mirv: ok, thanks! I'll assign it then
[12:20] <didrocks> Mirv: the fix is in trunk, or it's already in the ppa?
[12:20] <didrocks> ogra_: installing random binaries from random people? ;)
[12:20]  * didrocks runs
[12:21] <ogra_> haha
[12:21] <ogra_> didrocks, when did you plan the meeting this afternoon, i have to pick up a parcel on the other side of the city and need to be out for a bit
[12:22] <didrocks> ogra_: I was thinking at 4PM, is that good for you?
[12:22] <didrocks> let me schedule it
[12:22] <Mirv> didrocks: in trunk and built in daily PPA, ie. qa stack is ready
[12:22] <ogra_> yeah, thats fine
[12:22] <didrocks> Mirv: excellent, just need validation then
[12:22] <ogra_> just need to know when i have to be back again
[12:23] <didrocks> invitations sent
[12:23] <ogra_> great
[12:24] <didrocks> sil2100: all published now?
[12:24] <sil2100> didrocks: ossu! Yes
[12:24] <didrocks> \o/
[12:25] <didrocks> sil2100: free to do this AP one?
[12:25] <didrocks> (run 67)
[12:26] <didrocks> sil2100: I guess it's going back to surfaceflinger (you will enjoy the speed improvment ;)) and running all AP tests
[12:26] <asac> Mirv: check with didrocks how to resurrect it and where
[12:26] <didrocks> sil2100: it's request 10
[12:26] <didrocks> asac: you mean the autopilot run?
[12:26] <asac> right
[12:26] <ogra_> sergiusens, poke
[12:26] <sergiusens> ouch
[12:27] <didrocks> asac: already handling it ^
[12:27] <ogra_> sergiusens, seems i cant flash any of my devices anymore
[12:27] <asac> :)
[12:27] <ogra_> INFO:phablet-flash:Booting /tmp/tmp_Ntl3S/partitions/recovery.img
[12:27] <ogra_> < waiting for device >
[12:27] <ogra_> downloading 'boot.img'...
[12:27] <ogra_> hangs there forever
[12:27] <ogra_> on both devices
[12:27] <sergiusens> ogra_, and you said you always used sudo too? so not a perm problem?
[12:27] <ogra_> yeah
[12:28] <ogra_>  sudo phablet-flash ubuntu-system --channel saucy-proposed -d maguro --no-backup
[12:28] <ogra_> thats what i use
[12:28] <sergiusens> ogra_, when you flash, there should be small text on the device screen
[12:28] <ogra_> respectively with -d mako
[12:28] <ogra_> yes
[12:28] <ogra_> i see a blue sripe at the bottom
[12:28] <sergiusens> ogra_, any errors there?
[12:28] <ogra_> "fastboot status ....)
[12:29] <ogra_> doesnt look like errors
[12:29] <ogra_> "fastboot status - download  08682888
[12:29] <ogra_> thats what i have written at the bottom
[12:30] <didrocks> ok, exercising a little bit, back in ~1h
[12:31] <ogra_> sergiusens, this is on raring with latest phablet-tools btw ... worked fine yesterday (at least on maguro, didnt flash mako)
[12:31] <sergiusens> ogra_, strange is that all that is doing is fastboot boot /tmp/tmp_Ntl3S/partitions/recovery.img
[12:32] <ogra_> yeah, that wone works
[12:32] <ogra_> the next step is failing i think
[12:32] <sergiusens> ogra_, yeah, not related to phablet-tools, I haven't touched that in ages
[12:32] <sergiusens> ogra_, oh... the message from fastboot is confusing ;-)
[12:33] <sergiusens> ogra_, if you tell it to boot something it calls it boot image from then on (downloading 'boot.img')
[12:33] <ogra_> ah
[12:33] <ogra_> well, it doesnt proceed ... and there are no errors anywhere
[12:33] <ogra_> tricky one :(
[12:33] <sergiusens> ogra_, and we are not writing to disk anywhere there either
[12:34] <sergiusens> ogra_, what about syslog or cable errors?
[12:34] <ogra_> well, the same cable worked for weeks i always use the same
[12:34] <ogra_> but i can try another one
[12:34] <asac> didrocks: so 66 was the image before the MIR landing ?
[12:35] <asac> oh i think mir failed to land because of build failures etc.?
[12:35] <ogra_> asac, 66 was the keyboard rollback
[12:35] <didrocks> asac: run 66 is the image before the MIR landing, right
[12:35] <didrocks> asac: builds failures on mir is fixed
[12:35] <asac> right. we did that before MIR intentionally
[12:35] <asac> goodie
[12:35]  * didrocks is afraid about run 67 with all the stuff that's going to fly in
[12:35] <ogra_> asac, well, semi good ... lightdm doesnt look good
[12:35] <asac> good
[12:35] <asac> :)
[12:36] <asac> well ... good we found before
[12:36] <ogra_> though until i have done a new test from scratch i'm willing to blame my device
[12:36] <didrocks> anyway, really going on exercising now
[12:36] <asac> ok ... i will get there too soon
[12:36] <ogra_> asac, well, it will be *really hard* to coordinate the fixes
[12:36] <asac> didrocks: anything important in flight etc.?
[12:36] <ogra_> asac, it isnt lightdm thats breaking here, its all the apps not shipping the right permission files for polkit
[12:36] <asac> ogra_: why? we tell mterry how to reproduce and he will fix it :)
[12:36] <ogra_> he cant fix it
[12:37] <didrocks> asac: nothing not in proposed, I gave the resurrected AP to sil2100
[12:37] <ogra_> the individual apps need to ship pkla files for managing dbus access
[12:37] <asac> didrocks: kk
[12:37] <asac> thx
[12:37] <didrocks> yw
[12:37] <ogra_> asac, that will be a pain to coordinate :(
[12:37] <seb128> ogra_, how did those work before have working polkit?
[12:37] <asac> sil2100: be extra careful about autopilot changes... those can have lethal effects
[12:37] <ogra_> seb128, polkit wasnt used at all
[12:37] <seb128> ogra_, why is it getting used?
[12:37] <ogra_> seb128, logind didnt register etc
[12:37] <asac> seb128: we had turned polkit off... i guess we could just set polkit to _all allowed_ policy
[12:38] <asac> while we fix it :)
[12:38] <seb128> hum
[12:38] <ogra_> seb128, because ightdm enables logind and polkit gets usable (as it should)
[12:38] <asac> well, i would have preferred a world without polkit :)
[12:38] <seb128> ogra_, asac: what I don't get is that without logind, polkit calls would fail for system settings ... why would they work for others and not us?
[12:38] <asac> but seems everyone agrees we need it, so i stopped questioning that :-P
[12:39] <seb128> it seems like things should not work without the acl control
[12:39] <seb128> rather than magically work
[12:39] <ogra_> asac, we shoiuld have started developemnt only after having the base image ready :P
[12:39] <ogra_> but it is how it is :)
[12:39] <asac> the base image is heavily influenced by the continuously evolving requirements of those that develop on top
[12:40] <cjwatson> seb128: at least in several places we have policy overrides to just allow everything for now
[12:40] <cjwatson> which is crap
[12:40] <ogra_> ++
[12:40] <cjwatson> seb128: but e.g. packagekit-plugin-click ships such an override
[12:40] <seb128> cjwatson, I see
[12:40] <ogra_> NM even ships two
[12:40] <asac> but why would we regress on this if those overrides are in place?
[12:40] <ogra_> for both cases
[12:40] <asac> cant we land lightdm in first steps while keeping those unchanged and then clear the image after?
[12:40] <seb128> asac, right, I don't understand how a working polkit can makes things go backward
[12:40] <ogra_> asac, no, the tests all fail
[12:40] <cjwatson> yeah, I'm not sure why apps previously worked
[12:41] <seb128> it should just allows extra stuff to work
[12:41] <asac> ogra_: because you maybe try to enable polkit?
[12:41] <asac> maybe dont do that part
[12:41] <ogra_> most of the dbus accesses fail
[12:41] <asac> i dont knmow what you are doing, so i cant say
[12:41] <ogra_> asac, i cant, logind enables it
[12:41] <asac> i believe its something simple as seb128 points out
[12:41] <ogra_> lightdm registers with liogind
[12:41] <asac> seb128: can you help checking that? This story sounds too odd :/
[12:41] <ogra_> anyway, i have to go now
[12:41] <asac> yeah cu later :)
[12:42] <ogra_> back for the call
[12:42] <seb128> asac, yes, we are looking at it
[12:42] <seb128> asac, ogra_: for the record, Laney just managed to change the device time with those updates
[12:42] <seb128> (that and a fix to a pka)
[12:42] <asac> ogra_: is it that all tests are failing?
[12:42] <asac> if so it might be something with autopilot and policykit
[12:43]  * asac restarts with lightdm
[12:44] <seb128> asac, polkit was not working before, things using it should have just failed
[12:44]  * asac shrugs
[12:44] <seb128> I don't get how making it handle requests can create autopilot issues
[12:44] <asac> i will see in a second if all just fails now
[12:44] <seb128> seems like a redherring to me
[12:47] <asac> notes-app succeeded :)
[12:47] <asac> how can i figure if use lightdm?
[12:47] <asac> seb128: any idea?
[12:47] <seb128> asac, run loginctl and see if you have a seat for your user
[12:48] <asac> ok will do after unity8 tests finish
[12:48] <asac> seb128: do you have this on your mako already?
[12:48] <seb128> asac, no, I've been trying on my grouper because I needed to do build and I had the build-deps installed there
[12:48] <asac> kk
[12:48] <seb128> (system settings builds)
[12:49] <seb128> I can try on mako in a bit
[12:49] <seb128> asac, Laney has been testing on mako though
[12:49] <seb128> he got the system settings to do changes through polkit
[12:49] <asac> sergiusens: do you still have the utah thing set up?
[12:49] <seb128> so it's looking good from that side at least
[12:49] <asac> sergiusens: can you take the latest image, punt the lightdm stuff onit and run all autopilots?
[12:49] <asac> and see if thats bad?
[12:50] <sergiusens> asac, I don't have devices to test avail
[12:50] <asac> sergiusens: lightdm stuff == http://people.canonical.com/~ogra/ubuntu-touch/lightdm/
[12:50] <asac> seb128: ogra said it breaks all tests
[12:50] <asac> i dont see it on maguro, but i need someone to confirm on mako... but dont worry
[12:50] <seb128> k
[12:51] <sergiusens> asac, I have a very custom setup for qtmultimedia now that I'm testing
[12:51] <asac> sergiusens: what happened to them?
[12:51] <asac> ok
[12:51] <asac> dont worry
[12:51] <sergiusens> asac, oh, I don't have mako
[12:52] <asac> sergiusens: whats the state of MM?
[12:53] <sergiusens> asac, mediaplayer is ready ready
[12:54] <sergiusens> asac, others, testing testing
[12:54] <asac> so thumbnails are working in mediaplayer again or did we cut that feature now?
[13:15] <lool> adding a landing entry for unity-scope-click
[13:18] <asac> some entries on spreadsheet have been set to DONE even though they are targetted for 66
[13:18] <asac> 34 for example
[13:18] <asac> didrocks: ^^
[13:19] <lool> didrocks: did you reach some Mir folks for the issue on mako?
[13:19] <lool> didrocks: if not, I think it would be good to give a heads up to kgunn_ now
[13:19] <asac> didrocks: issue?
[13:19] <asac> err lool :)
[13:20] <asac> didrocks: also 66 is imo INIMAGE
[13:20] <asac> (ubuntu-keyboard backout)
[13:20] <lool> asac: Mir's testing by sil2100 resulted in some graphical problems (but flickering is gone)
[13:21] <asac> yeah. we should let kgunn_ and jfunk know and maybe file a bug so they have a place to discuss this
[13:21] <asac> sounds like a general improvement though... so not blocking
[13:22] <lool> sil2100: do you have a bug for the Mir issue(s)
[13:32] <sil2100> lool: I filled in for the AP issues in Mir, kgunn_ said he'll fill in for the slowdowns
[13:32] <sil2100> lool: https://bugs.launchpad.net/mir/+bug/1231452
[13:32] <sil2100> didrocks: ACK! (sorry for answering now, missed the ping while coding)
[13:40] <rsalveti> morning
[13:40]  * rsalveti checking backlog
[13:47] <ogra_> re
[13:49] <rsalveti> didrocks: lool: qtmultimedia 5.1 doesn't break anything, but anyway, no FFe for us :-)
[13:50] <lool> rsalveti: aha, thanks for confirming, I remained on the (sound) idea of updating qtmultimedia-opensource-src
[13:51] <lool> rsalveti: well it's better in this direction than the other one at least
[13:51] <lool> (ie not building against 5.1 and running against 5.0  :-)
[13:51] <rsalveti> yes
[13:51] <rsalveti> it's fully compatible with qt 5.0
[13:52] <rsalveti> didrocks: lool: we can land the media stack
[13:52] <rsalveti> as of now
[13:52] <rsalveti> just mediascanner and mediaplayer-app
[13:52] <didrocks> rsalveti: there is a meeting in 8 minutes about it
[13:52] <lool> didrocks: So I was about to ping Francis or Nicholas on getting https://code.launchpad.net/~lool/unity-scope-click/lp-1231393/+merge/187766 merged, but rather than that, is it ok if I just merge it manually?
[13:52] <didrocks> let's discuss it there
[13:52] <lool> hmm maybe I cant though
[13:52] <didrocks> and let me finish my scrollback first ;)
[13:52] <ogra_> rsalveti, what about qrvideo-node ?
[13:52] <ogra_> *qt
[13:52] <rsalveti> didrocks: well, I can already tell you the meeting results here :P
[13:53] <rsalveti> we're not using gst-hybris by default yet, as it breaks mediascanner
[13:53] <lool> haha
[13:53] <didrocks> asac: yeah, because the image is built, right?
[13:53] <didrocks> asac: re line 34 DONE
[13:53] <rsalveti> we're still investigating, but jim is off, so will probably be on hold until tomorrow
[13:53] <didrocks> lool: I've already pinged the mir guys, yeah
[13:53] <didrocks> asac: not sure about your syntax diff between INIMAGE and DONE ;)
[13:54] <didrocks> asac: there are bugs
[13:54] <didrocks> asac: for the mir stuff
[13:54] <lool> didrocks: I gave a heads up to kgunn_ when he connected 30mn ago or so, with all the issues (fixed FTBFS, testsuite, AP tests, graphical glitches, slowness)
[13:55] <didrocks> rsalveti: would be nice to have a good plan, let's discuss in 5
[13:55] <lool> rsalveti: so we're not seeding gst-hybris, but otherwise it works with software decoding?
[13:55] <lool> and minus sceneselector
[13:55] <didrocks> lool: hum, so 4 people pinged hum about this in //
[13:55] <didrocks> lool: not a real good use on IRC :p
[13:55] <rsalveti> just saying we need jim to discuss the proper plan
[13:55] <lool> didrocks: I think that's good  :-)
[13:55] <didrocks> rsalveti: is he around? ;)
[13:55] <rsalveti> didrocks: as I said, he's off today, back tomorrow
[13:56] <didrocks> rsalveti: ok, let's move the discussion to tomorrow then?
[13:56] <didrocks> lool: ok as well?
[13:56] <rsalveti> lool: yup, the update for mediaplayer-app is to remove sceneselector and remove any dependency on gstreamer
[13:56] <lool> rsalveti: oh so you don't even want to land the ready parts, but wait til jim is back?
[13:56] <rsalveti> lool: so it works already using software decode, that's why we can land it already
[13:56] <lool> yes
[13:56] <lool> I'd rather we land that updated part today
[13:57] <didrocks> I think it should at least be part of build 68
[13:57] <didrocks> not 67
[13:57] <lool> didrocks: happy to have a chat with jim tomorrow instead or on top of today's
[13:57] <didrocks> we have quite a lot of stuff going in
[13:57] <rsalveti> no, I just want to put qtvideo-node and seeding gst-hybris by default on hold
[13:57] <didrocks> ok, let's discuss in 3 min, it seems it's needed
[13:57]  * didrocks will grab some water
[13:58] <lool> didrocks: actually that's the time I can't make
[13:58] <lool> didrocks: but you guys go ahead
[13:58] <lool> I dont see why we'd seed gst-hybris if it's known borken, but I'm sure rsalveti has a good reason   :-)
[13:58] <rsalveti> I'd just move the meeting for tomorrow, invite jim, and land the media stack today
[13:59] <ogra_> lool, gst/hybris is fine
[13:59] <ogra_> its the stuff using it that isnt
[13:59] <lool> 15:53 < rsalveti> we're not using gst-hybris by default yet, as it breaks mediascanner
[13:59] <ogra_> so we can seed but not use it
[13:59] <rsalveti> it's just that once gst-hybris is in, playbin selects it by default
[13:59] <didrocks> rsalveti: I don't want to land the media stack before we discuss it :)
[13:59] <rsalveti> breaking some use cases, such mediscanner
[13:59] <lool> ogra_: I'm not sure we can
[13:59] <didrocks> rsalveti: especially with the churn we have right now in the image
[13:59] <ogra_> lool, ah
[13:59] <rsalveti> didrocks: that's the discussion, but we can do a meeting if you prefer
[13:59] <rsalveti> so can say the same thing via hangout
[13:59] <lool> you guys meet without me
[13:59] <rsalveti> :-)
[14:00] <didrocks> rsalveti: yeah, let's jump in a hangout
[14:00] <lool> and land as you can today
[14:00]  * ogra_ relocates
[14:00] <didrocks> ogra_: rsalveti: https://plus.google.com/hangouts/_/8353ddd0558b39c4a5d6c701ddd04b156bda1e67
[14:01] <bfiller> popey: what's the deal with the notes-app tests and why do you think it's related to ubuntu-keyboard?
[14:02] <popey> bfiller: I didnt. I was just doing as told by ogra_ and didrocks ☻
[14:02] <popey> bfiller: they asked me to run the tests locally, then suggested we try downgrading the ubuntu-keyboard, which I did, and the tests passed once I did
[14:03] <ogra_> bfiller, rolling back to the former kbd version made the test errors go away
[14:03] <bfiller> ogra_: by chance
[14:03] <bfiller> ogra_: has nothign to do with the u-k changes, none are functional
[14:03] <ogra_> bfiller, http://people.canonical.com/~ogra/touch-image-stats/20130925.2.changes
[14:03] <ogra_> thats the changes
[14:03] <bfiller> ogra_: only tests and schema file since previous version
[14:03] <ogra_> nothing on it that could influence tests
[14:04] <bfiller> ogra_: no really can't see anything
[14:04] <ogra_> bfiller, well if there is a nanosecond delay in the kbd coming up we might hit a race in a timing critical test
[14:04] <ogra_> the tests are all pretty shaky
[14:04] <ogra_> and poften timing critical
[14:04] <bfiller> ogra_: right, we need to fix the stupid notes-app tests
[14:04] <ogra_> *often
[14:05] <ogra_> agreed ...
[14:05] <bfiller> think we need to put the keyboard back or else it's autopilot tests will fail (:
[14:05] <ogra_> asac, ^^^
[14:12] <asac> bfiller: keyboard regressed notes-app
[14:12] <asac> can we fix that tests first or at same time?
[14:13] <bfiller> asac: I think that is a mis-diagnosis
[14:13] <asac> bfiller: its not. downgrading fixed the notes-app test
[14:13] <bfiller> asac: by luck
[14:14] <asac> bfiller: popey ran it a few times and it always fails
[14:14] <asac> he downgraded and it succeeded twice in a row
[14:14] <bfiller> it's a timing issue, no changes were made in the keyboard other than addding tests and schema files, look at the diff :)
[14:14] <bfiller> it's shit notes-app tests
[14:14] <asac> right. so we are trying what we can
[14:14] <asac> bfiller: can you work on getting the notes-app test fixed?
[14:15] <lool> didrocks: could you add me to the team that has commit access to unity-scope-click?
[14:15] <asac> this is something that we would block the line on if we cant get it under control
[14:15] <asac> so far we continued because we thought we have figured that backing out helped
[14:15] <Saviq> fginther, otto runner pretty backed up again today?
[14:15] <bfiller> asac: yes will work on the notes-app tests
[14:15] <didrocks> lool: I can add you to ~ubuntu-unity, getting access to everywhere as a consequence
[14:16] <ogra_> asac, did you run lightdm tests (i cant flash anything here anymore and am not sure my install was clean before testing)
[14:16] <lool> didrocks: up to you
[14:16]  * ogra_ tries to downgrade phablet-tools
[14:17] <didrocks> lool: as you wish, if you prepare only upstream access, you need to ask to the team directly, I'm not an admin of that team
[14:17] <lool> didrocks: would like to merge lp:~lool/unity-scope-click/lp-1231393 manually because upstream merger didn't pick it up yet
[14:17] <lool> and we need it tonight
[14:17] <didrocks> juts tell me ;)
[14:17] <didrocks> lool: ah, it's the one you added directly on the spreadsheet?
[14:17] <lool> didrocks: so each time I want to use this to commit, I ping upstream?
[14:17] <lool> didrocks: that's fine
[14:17] <ogra_> whats happening tonight ?
[14:17] <didrocks> lool: no, I meant, ping upstream so that they add you to the team
[14:17] <ogra_> click party ?
[14:17] <lool> didrocks: ah
[14:17] <didrocks> lool: I don't have that access :p
[14:17] <fginther> Saviq, looks like two earlier tests got stuck and took the full 2 hours to timeout
[14:17] <lool> didrocks: ok
[14:18]  * didrocks hides his backdoor plugged in LP
[14:18] <lool> alecu: Ping
[14:18] <Saviq> fginther, ah, ok thanks
[14:18] <Saviq> fginther, so it should clear up soon
[14:18] <didrocks> ogra_: a click*y* party ;)
[14:18] <ogra_> :)
[14:18] <lool> alecu: Could you either a) give me write access to unity-scope-click, or b) merge lp:~lool/unity-scope-click/lp-1231393 manually, or c) do both?  :-)
[14:18] <didrocks> sil2100: were are we with autopilot?
[14:18] <lool> alecu: the upstream merger is too slow, I want us to pick this up as to land it in a soon to be built image
[14:19] <ralsina> lool: you *should* have write access already
[14:19] <fginther> Saviq, yes. a couple runs have already finished, but I'll keep an eye on it.
[14:19] <Saviq> fginther, thanks
[14:19] <lool> ralsina: bzr: ERROR: Cannot lock LockDir(chroot-73675664:///%2Bbranch/unity-scope-click/.bzr/branch/lock): Transport operation not possible: readonly transport
[14:19] <lool> when pushing to unity-scope-click
[14:19] <asac> bfiller: previously it wasnt very hard... i need your help to understand this notes-app
[14:19] <sil2100> didrocks: testing apps, got a few failures here and there, not sure if there were failures when running the old autopilot - do we have some results from people on the clean image?
[14:19] <ralsina> lool: grrrrr dobey? ^
[14:20] <didrocks> sil2100: mako is looking like that: http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4453/
[14:20] <didrocks> we have the only flacky test on notes-app that we know of
[14:20] <didrocks> bfiller: FYI ^
[14:21] <didrocks> bfiller: compared to http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4443/
[14:21] <didrocks> (which had always < 90%)
[14:21] <sil2100> didrocks: re running, since for instance there were 5 test failures on gallery-app
[14:21] <didrocks> sil2100: ok, please note those failing so that if we reject autopilot again, upstream can work on those
[14:21] <didrocks> (if they fail reliably)
[14:22] <ogra_> sil2100, yeah, gallery-app was acting up yesterday too
[14:22] <ogra_> second run worked, first one failed badly
[14:22] <sil2100> ogra_: with the new autopilot? Or the old one still?
[14:22] <alecu> lool: ack
[14:22] <sil2100> Ok, checking how it runs now
[14:22] <ogra_> sil2100, whatever plars runs on utah, no idea
[14:23] <didrocks> sil2100: so old one
[14:23] <dobey> hmm
[14:23]  * didrocks doesn't have any ice, omg…
[14:23] <ogra_> didrocks, whiskey on the rocks before 5 ?
[14:24]  * ogra_ shakes head ... frenchies
[14:24] <sil2100> Oh god
[14:24] <didrocks> ogra_: how do you think I can work so long? :p
[14:24] <ogra_> haha
[14:24] <sil2100> ;)
[14:24] <didrocks> ogra_: no, I just need to lower the temperature on the pressure that asac puts on us, so ice is needed :p
[14:24] <plars> sil2100: we don't update autopilot
[14:24] <ogra_> move into a fridge then :)
[14:25] <plars> sil2100: we don't update or install anything on the images now, except the -autopilot packages
[14:25] <sil2100> plars: ok
[14:25] <didrocks> ogra_: already considered that ;)
[14:25] <sil2100> ogra_, didrocks: second run - 6 failures on gallery-app itself
[14:25] <didrocks> urgh :/
[14:25] <sil2100> No idea if it's related to the new autopilot ;/
[14:26] <ogra_> try a third :)
[14:26] <lool> alecu: mind pinging me when it's merged or I can merge?
[14:26] <sil2100> ogra_: checking webbrowser-app now, since I at least know it passed on the old one
[14:27] <dobey> lool: it is merged
[14:27] <dobey> alecu, ralsina: ^^
[14:28] <lool> dobey: thanks
[14:28] <sil2100> hmmmmm
[14:28] <lool> didrocks: ok for me to run click-package stack?
[14:28] <lool> didrocks: would like to pick up the bzr change for unity-click-scope into PPA
[14:28] <sil2100> ogra_: ohshit, 35 failures on webbrowser-app!
[14:29] <ogra_> awesome :P
[14:29] <didrocks> lool: yeah, +1
[14:29] <sil2100> didrocks: I would -1 autopilot for now... ;p
[14:29] <alecu> dobey: thanks
[14:29] <didrocks> sil2100: ok, please, just log them, open a bug, ping upstream and let's flush autopilot for now
[14:29] <sil2100> Not sure if that's related to AP update, but hmmm
[14:29] <ogra_> ogra@chromebook:~$ grep webbrowser tests.txt
[14:29] <ogra_> webbrowser-app	- 31 failures
[14:29] <asac> sil2100: webbrowser is sometimes acting very funny here
[14:29] <lool> building
[14:29] <asac> when rerunning its better
[14:29] <sil2100> In the past it was gool
[14:29] <didrocks> sil2100: well, downgrade it maybe
[14:29] <ogra_> hmm, that makes me wonder if my local lightdm testing by chance used the new stuff
[14:29] <lool> alecu: Would you mind testing the binaries from the PPA once they appear?
[14:29] <didrocks> and retry running some tests?
[14:30] <ogra_> sil2100, is that in the archive already ?
[14:30] <asac> i think it has to do with accurately unlocking the screen before starting
[14:30]  * asac reruns webbrowser withg lightdm as well
[14:30] <alecu> lool: sure
[14:30] <ogra_> asac, how much more accurate that seeeing the home lens should it be ?
[14:31] <asac> i havent figured out
[14:31] <ogra_> heh
[14:31] <asac> its what we try to solve by having a single tool that always does the right thing for each test
[14:31] <sil2100> ogra_: new autopilot?
[14:31] <ogra_> when i test the device is usually unlocked for a while already and i touch the screen before firing off the cmd in terminal
[14:31] <ogra_> sil2100, yeah
[14:31] <sil2100> ogra_: or webbrowser-app?
[14:32] <lool> alecu: should appear here any minute: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages?field.name_filter=unity-scope-click&field.status_filter=published&field.series_filter=saucy
[14:32] <ogra_> i wonder if that taints my testing too
[14:32] <ogra_> sil2100, autopilot
[14:32] <didrocks> ogra_: downgrade autopilot
[14:32] <didrocks> oupsss
[14:32] <didrocks> sil2100: ^
[14:32] <didrocks> stop breaking me!
[14:32] <didrocks> ;)
[14:32] <ogra_> pfft
[14:32] <plars> thostr_: I guess those unity updates didn't land? I'm still seeing the crash on unity tests
[14:32] <sil2100> ogra_: autopilot no, I was just testing it - downgrading now so that I can see what's up
[14:32] <lool> alecu: building: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/5051859
[14:32] <ogra_> sil2100, hmm, k
[14:32] <sil2100> But today I tested webbrowser-app with the old AP and it was ok
[14:33] <thostr_> plars: nooooo, can you verify that?
[14:33] <plars> thomi: yeah, looks like not yet http://people.canonical.com/~ogra/touch-image-stats/20130926.changes
[14:34] <ogra_> the last unity8 update landed in 24.1
[14:34] <plars> thostr_: ok, found it I think, it's slated for 68 - "For image 68	libunity, unity-scope-home"
[14:34] <ogra_> from 7.81.3+13.10.20130919.3-0ubuntu1 to 7.81.3+13.10.20130924.2-0ubuntu1
[14:35] <ogra_> thostr_, plars, i think thats one of the packages held back by beta freeze
[14:36] <ogra_> hmm, no
[14:36] <thostr_> ogra_: do I actively need to do anything here or just wait?
[14:36] <ogra_> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html doesnt have it
[14:36] <didrocks> not libunity, unity-scope-home, (not done yet, it's targeted, probably tomorrow morning), but would have been blocked by the beta freeze anyway
[14:36] <didrocks> thostr_: just wait
[14:36] <thostr_> didrocks: ok
[14:36] <ogra_> thostr_, if it is in the landing plan sheet it is being taken care of
[14:36] <didrocks> thostr_: or if you do the testing, we can fasttrack it
[14:36] <didrocks> thostr_: running the unity on desktop AP tests
[14:36] <didrocks> and the unity8 on phone
[14:36] <didrocks> with those installed
[14:37] <didrocks> and ensuring there is no regression
[14:37] <didrocks> then, we can publish
[14:37] <didrocks> thostr_: do you have anyone able to do that? ^
[14:37] <thostr_> didrocks: testing is easy... without that fix test crash, with the fix everything is ok :)
[14:37] <didrocks> (so that you don't block on our current bandwidth)
[14:37] <ogra_> didrocks, please also request at least one app test in such cases
[14:37] <lool> alecu: note that there are other changes staged in the PPA (your pkcon remove change, and a couple of fixes by dobey)
[14:37] <didrocks> thostr_: I mean, you need to ensure that you don't regress other AP tests ;)
[14:37] <didrocks> thostr_: so you are up for that?
[14:37] <ogra_> didrocks, i.e. lightdm passed unity8 on both arches ... but all apps fail
[14:38] <lool> alecu: the goal is to make sure that the updated package fixes the regression and is overall good to go; if we need to revert the other changes, let me know  :-)
[14:38] <didrocks> ogra_: I doubt libunity/home-scope affects apps, but sure, we can add that to the package :p
[14:38] <thostr_> didrocks: I'll quickly rerun unity8 AP on saucy-proposed
[14:38] <ogra_> imho we should always ask for one app test
[14:38] <ogra_> randomly picked
[14:38] <didrocks> thostr_: you need to add the package from the daily-build ppa
[14:39] <sil2100> didrocks: downgraded autopilot and webbrowser-app tests seem to be working...
[14:39] <didrocks> thostr_: both the unity7 one on desktop and unity8 on touch
[14:39] <didrocks> thostr_: there are some intructions on https://wiki.ubuntu.com/Touch/Testing#Testing_your_Ubuntu_Touch_Code_before_submission
[14:39] <sil2100> Maybe I forgot upgrading something..?
[14:39] <thostr_> didrocks: ok
[14:39] <didrocks> sil2100: so apt-get install directly the binary packages for libunity & home-scope
[14:40] <didrocks> sil2100: no, I think that's enough info, just log that in a bug, poke thomi about those and let's move on ;)
[14:40] <didrocks> sil2100: can you paste me the ref on the bug so that I write it for the landing plan?
[14:41] <sil2100> didrocks: doing!
[14:43] <sil2100> didrocks: https://bugs.launchpad.net/webbrowser-app/+bug/1231492
[14:44] <ogra_> sergiusens, err ... http://launchpadlibrarian.net/151320727/phablet-tools_1.0%2B13.10.20130919.3-0ubuntu1_1.0%2B13.10.20130924.1-0ubuntu1.diff.gz  ... isnt there a mkdir missing ?
[14:44]  * ogra_ still cant flash, i downgraded two versions already
[14:45] <didrocks> sil2100: perfect! mind doing system-settings now? (an easy one :p)
[14:45] <didrocks> sil2100: let's still it from robru and give robru the media stack
[14:46] <lool> alecu: it built; could you confirm it passes your testing?  https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/5051859  thanks!
[14:46] <sergiusens> ogra_, hmmm, doanac ^^
[14:46] <lool> dobey: Did you want to test unity-scope-click binaries for next image too?  https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/5051859
[14:47] <sergiusens> ogra_, should be harmless if it's not there though... let me try
[14:47] <doanac> plars: you have something set up that can do this on ashes? ^^
[14:47] <ogra_> sergiusens, well, it will do harm on readonly tests (which we dont do yet) since it will just stay in /
[14:48] <sergiusens> ogra_, oh, for readonly tests the prev tool sets it up
[14:48] <ogra_> ah
[14:48] <sergiusens> ogra_, phablet-click-test-setup
[14:48] <ogra_> k
[14:48] <sil2100> didrocks: ACK ;)
[14:48] <didrocks> sil2100: see #ubuntu-devel, you have some free slots until then I guess ;)
[14:49] <sergiusens> ogra_, naming it 'click' could be wrong in the future as we can also test unity8 and the sdk with that
[14:49] <didrocks> sil2100: tracking with seb128 the revert?
[14:49] <ogra_> well, you can always rename
[14:49] <didrocks> (for content-hub + settings)
[14:49] <plars> doanac: what, upgrading autopilot but not other stuff?
[14:49] <dobey> lool: some specific tests? i've been testing it from trunk as i've been working on fixes.
[14:50] <lool> dobey: smoketesting that it didn't regress there, when built against the other components
[14:50] <doanac> plars: actually, i'm confused.
[14:50] <lool> dobey: perhaps a good thing to test would be with new download-manager in the PPA
[14:51] <doanac> sergiusens: you want us to just install that .deb and run its own tests, or do a full smoke run on an image + this deb?
[14:51] <lool> dobey: top of http://people.canonical.com/~platform/cu2d/results
[14:51] <didrocks> lool: are you going to land the download manager at the same time?
[14:51] <sergiusens> doanac, I didn't request anything, if it seemed so, sorry
[14:52] <lool> didrocks: I don't know
[14:52] <doanac> oh - okay
[14:52] <lool> didrocks: is there an entry for it?
[14:52] <lool> didrocks: it seems to be low priority fixes
[14:52] <lool> didrocks: might be needed to help system-image, but didn't hear a request about it
[14:52] <sergiusens> doanac, just pointed you to ogra_ 's comment, but I think it's not a bug, just not elegant
[14:52] <ogra_> doanac, http://launchpadlibrarian.net/151320727/phablet-tools_1.0%2B13.10.20130919.3-0ubuntu1_1.0%2B13.10.20130924.1-0ubuntu1.diff.gz misses a mkdir ... sergiusens was just pointing to my line above
[14:52] <didrocks> lool: yeah, I'm surprised, slangasek told me system-image would need the download-manager
[14:52] <didrocks> lool: system-image is going to land?
[14:52] <lool> didrocks: I think we already got the new one in
[14:52] <didrocks> ah ok
[14:53] <lool> didrocks: system-image is getting ready, but dont think it's landing yet
[14:53] <dobey> lool: is there a list of tests in a document or wiki page somewhere, to run?
[14:53] <didrocks> lool: ok
[14:54] <doanac> sergiusens: oh - i was looking at the wrong comment. yeah, that should probably be fixed
[14:54] <lool> dobey: no; I'd say: test the features / fixes you're landing (network for instance) and test basic operations: installing a click from store, searching for clicks, opening preinstalled clicks (e.g. dropping letters)
[14:54] <lool> there's a new remove click feature apparently in this one  :-)
[14:55] <doanac> sergiusens: a simpler thing would be to simply call it lik with PYTHONPATH, eg: PYTHONPATH=/home/autopilot autopilot run ....
[14:55] <doanac> then no mkdir is needed
[14:55] <alecu> lool: yes: you can uninstall clicks now, though there's a dash bug that prevents the UI from showing that the uninstall was successful
[14:55] <dobey> lool: is there a unity8 update that supports results invalidation?
[14:56] <alecu> lool: so, you click on "uninstall", the click is uninstalled, but the ui still shows the "uninstall" button
[14:56] <alecu> it's supposed to close the preview
[14:57] <sergiusens> doanac, well it's not needed since the ';' doesn't care if the prev command was successful
[14:57] <lool> didrocks: I see system-image "please plan for image 67"
[14:58] <sergiusens> doanac, but we can do that
[14:58] <doanac> sergiusens: ah - even better. swallow the error :)
[14:58] <sergiusens> doanac, exactly, it's a nop
[14:58] <doanac> i wish i could say that was my original intent now :)
[15:02] <lool> didrocks: (pocked barry to get a system-image update, will report back once I know more)
[15:02] <didrocks> thanks lool
[15:04] <alecu> lool: I'm able to start franglish with the package in the ppa
[15:05] <lool> alecu: cool; did you do other tests?
[15:05] <lool> alecu: did you test your other changes, like package removals?
[15:05] <alecu> fate dice, qr-codes, torch work too
[15:05] <lool> alecu: these will go in at the same time (single pipe, everything in trunk has to go in)
[15:05] <lool> alecu: was this with current or new download-manager (in ppa)?
[15:06] <lool> dobey: I dont know what that means (results invalidation); is this what I'd see in the log?
[15:07] <alecu> lool: download manager was not updated; I only installed unity-scope-click
[15:07] <lool> dobey: dont see anything like that in unity8; would you have a mp pointer or bzr revision or bug?
[15:07] <lool> alecu: ok, I think dobey is testing with new download manager
[15:07] <lool> ralsina: do you know how urgent the changes to download-manager are?
[15:07] <alecu> lool: and uninstall seems to be failing here with a pkcon error
[15:07] <lool> ralsina: should we preferably get them in or preferably not?  assuming preferably yes as what's in trunk should be reusable and system-image might need them?
[15:08] <dobey> lool: ah, scopes are supposed to invalidate their results, to force the dash ui to refresh. there is a libunity api call of results_invalidated(), but currently, nothing happens in the UI when it is called
[15:08] <ralsina> lool: system-image is (AFAIK) developing against trunk, so it does need those to land the integration
[15:08] <lool> alecu: so that's good to know, what's the difference with your local testing that explains the regression?
[15:08]  * ralsina reads backlog
[15:08] <alecu> [unity-scope-click] - DEBUG: click-scope.vala:192: Error building preview: Problem running: pkcon -p remove com.ubuntu.developer.alecu.qr-code;0.0;all;local:click (Child process exited with code 7).
[15:10] <lool> ralsina: would you know what testing the download-manager changes received in trunk?
[15:10] <lool> alecu, ralsina: So removal being broken shouldn't stop us from landing it as it's a new feature, so doesn't matter if it doesn't work
[15:11] <alecu> lool: ah, I manually changed the manifests of every installed app, to test the updater-app issues. I'll try with a freshly installed app.
[15:11] <lool> but I'd like to know why it wasn't found in development
[15:11] <ralsina> lool: I think it's because of alecu's manual testing of click-updater
[15:11] <lool> ok; let's confirm removal indeed works then
[15:11] <mandel> lool, what exactly do you mean with 'what testing the download-manager changes received in trunk?'
[15:14] <lool> mandel: we're assuming trunk is always releasable, and sometimes we publish full stacks (e.g. here this is part of the click stack)
[15:14] <lool> mandel: so the couple of changes in trunk need to be releasable
[15:14] <alecu> lool: uninstall is working. No UI feedback, as expected, due to: https://bugs.launchpad.net/unity8/+bug/1231404
[15:14] <mandel> lool, aha, and you want to know if the fixes are tested? atm all bug fixes come with unit tests with them
[15:15] <mandel> lool, ideally I'll grab the integration tests from barry (to start with) and will add them to my trunk too
[15:15] <dobey> ok, i need to get lunch. will try to run some tests on my nexus when i get back
[15:16] <lool> mandel: yes, kind of
[15:16] <mandel> lool, well, right now all fixes do come with at least one unit tests or more
[15:17] <mandel> lool, unless minor changes (logging for example)
[15:17] <lool> mandel: so to clarify, nobody asked us to land your changes in trunk, we dont land stuff by default, but there are other changes in the "click" stack (which includes download-manager) that we want to push and we prefer pushing whole stacks
[15:17] <lool> mandel: so if you've tested latest download-manager, we're good
[15:19] <mandel> lool, yes, everything in trunk is 'stable' and has been tested and all the new branches are always tested against the image-updates for integration issues
[15:19] <ralsina> mandel: we'll need to also test against click-scope and click-update-manager now
[15:19] <ralsina> mandel: since those will drag downloader when they land
[15:20] <ralsina> instead of only testing those when we wanted to land
[15:20] <mandel> ralsina, lool yes, I wonder how I can get jenkins to run those tests too.. I'm think, if we have integration tests in those dependencies I can add some code to run their tests and do no land if we have issues
[15:21] <mandel> ralsina, lool but, and is a big BUT, I don't believe those projects have integration tests
[15:21] <ralsina> mandel: we'll have to do manual testing until they do
[15:21] <ralsina> mandel: which is why I asked mmcc to work on that big integration test in today's call
[15:21]  * mandel nods
[15:22] <lool> mandel: that's a good question; autopkgtest is meant for this, and the cu2d infrastructure should arrange for packages to be built in the right order against each other (e.g. click-scope would be built against latest download-manager)
[15:28] <mandel> lool, ok, so as long as we have integration tests we can find those issues, else we might have problems because we do not have anything automated
[15:29] <mandel> lool, I might as well as some testing libs for the dependencies to have it easier to have tests agains a download-manager like we are doing with barry
[15:29] <lool> mandel: believe me, I've pushed for integration tests  :-)
[15:29] <lool> ralsina can testify
[15:29] <ralsina> amen
[15:39] <lool> I've bumped risk on mtp/lxc-android-config to medium
[15:39] <lool> (was low)
[15:39] <lool> as this touches boot stuff
[15:40] <didrocks> sure
[15:40] <didrocks> ogra_ tried to hide that! ;)
[15:41] <ogra_> ?? why is that ?
[15:41] <ogra_> (medium)
[15:42] <ogra_> lool, ^^^
[15:42] <lool> changes container startup/shutdown approach
[15:42] <lool> I'm super happy that this is coming in as it might solve my FS corruption issues
[15:42] <lool> and Jamie's
[15:42] <lool> but it's not low risk
[15:43] <ogra_> hmm, it has been tested and it has zero risk to affect any tests
[15:43] <ogra_> which is the assesment i use for the prio field
[15:44] <ogra_> should we judge prio by anything else ?
[15:46] <didrocks> I guess by the risk globally, not only on tests would make sense
[15:57] <didrocks> asac: FYI, all ppas are screwed
[15:57] <didrocks> ping on #ubuntu-release, trying #webops now
[15:58] <asac> didrocks: ?
[15:58] <didrocks> I've disabled cu2d autorebuild to avoid us ending up in a bad state
[15:58] <didrocks> asac: chroot issues
[15:58] <asac> infinity: cjwatson: ^
[15:58] <lool> gah
[15:58] <didrocks> asac: already pinged them :p
[15:59] <didrocks> (see #ubuntu-release)
[15:59] <didrocks> (no answer on #webops yet, will keep you posted)
[15:59] <asac> yeah thanks
[16:00] <didrocks> seb128: waiting your binaries for content-hub and system-settings to revert :p
[16:00] <didrocks> seb128: what you doing? ;)
[16:01]  * seb128 slaps didrocks
[16:01] <didrocks> heh
[16:02] <didrocks> asac: coming?
[16:02] <didrocks> sil2100: ^
[16:02] <ogra_> asac, hurry up slacker !
[16:03] <ogra_> :)
[16:36] <cjwatson> didrocks: I'll give back all the failures now, since I have a script for it
[16:38] <didrocks> cjwatson: thanks! I've gone ahead for the one I cared in term of timing
[16:39] <cjwatson> Fortunately when this happened on Tuesday morning I wrote a script for it rather than doing it ad-hoc ...
[16:40] <cjwatson> Sorry I didn't notice.  There's a Debian technical committee meeting this evening so I had to take some time to catch up on mail backlog.
[16:40] <cjwatson> And wasn't watching IRC.
[16:44] <lool> dobey: thanks for testing; mind pinging me when you're done so that I publish from PPA to archive?
[16:44] <dobey> i will
[16:44] <lool> cool
[16:44] <lool> I might be off for dinner, but will check back
[16:46] <thostr_> didrocks: not yet done with testing... somehow my device is broken... need to reflash completely
[16:46] <didrocks> cjwatson: no worry, it was still dealt promptly
[16:54] <lool> thostr_: if it's reassuring, we're fixing a probably filesystem corruption source in an upcoming image  :-)
[16:54] <lool> *probable
[17:16] <ogra_> finished. total time: 0.564s
[17:16] <ogra_> INFO:phablet-flash:Waiting for install to finish on device. Please do not unplug device until phablet-flash finishes.
[17:16] <ogra_> phablet flash hates me today
[17:16] <ogra_> i have the tour on the phone already
[17:25] <ogra_> omg
[17:26] <ogra_> the gates are open ... look for cover ... a beta freeze wave is coming out of proposed
[17:29] <cjwatson> err
[17:29] <cjwatson> how about not exaggerating wildly?
[17:33] <lool> robru: so archive is open again, that is proposed migration will happen again
[17:33] <lool> robru: e.g. "mir" is "Valid candidate"
[17:33] <robru> lool, oh, great. so i'm just waiting on plars to run some tests for me on his n4
[17:33] <cjwatson> but see #ubuntu-release; we're NOT opening floodgates entirely as ogra_ suggested
[17:34] <ogra_> sorry :)
[17:34] <cjwatson> ... or maybe I spoke up too late
[17:34] <lool> cjwatson: Yup, we've staged things in -proposed after testing in PPA and we're waiting for them to be in archive to build our next image
[17:36] <cjwatson> lool: (mir wasn't frozen anyway)
[17:37] <ogra_> i think we held back one dep in a PPA or some such to not have it promote ...
[17:37] <lool> cjwatson: it's on the image though
[17:37] <ogra_> (or was that the former Mir)
[17:37] <cjwatson> lool: it's not on an image releasing for beta
[17:37] <cjwatson> so wasn't frozen
[17:38] <lool> cjwatson: libmirclient3 isn't in ubuntu image?
[17:38] <lool> or libmirclient2 right now rather
[17:38] <cjwatson> nope
[17:38] <cjwatson> nor is xmir
[17:39] <lool> oh it's seeded because it's a bdep somewhere
[17:39] <lool> so might hurt package builds, but can't regress image in itself
[17:39] <lool> I thought we were pulling this in somewhere
[17:40] <cjwatson> only for a build-dep from xorg-server for the xserver-xorg-xmir package, afaik
[17:40] <cjwatson> definitely nothing runtime
[17:43] <lool> dobey: going for dinner
[17:49] <ogra_> geez
[17:49] <ogra_> the webbrowser-app autopilot test is massively scary
[17:49] <ogra_> you get a traceback every few minutes on the screen ... but it still passes
[17:52] <dobey> lool: have run into some other issues outside the click scope, which will get bugs shortly, but installing, uninstalling, and lack of network are all working as expected
[18:11] <ogra_> asac, wohoo ...
[18:12]  * ogra_ is at the 8th app test now with a freshly flashed maguro and lightdm 
[18:12] <ogra_> not a single failure yet
[18:19] <kgunn_> ogra_, hey since you're still on...
[18:19] <kgunn_> ogra_, i was hoping to try out the latest image with latest mir we pushed overnight...
[18:19] <kgunn_> however, i can't seem to find it (at least its not in the pending image)
[18:19] <kgunn_> any ideas ?
[18:19] <ogra_> likely in the daily-release ppa
[18:20] <ogra_> kgunn_, https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages?field.name_filter=&field.status_filter=published&field.series_filter=saucy
[18:20] <ogra_> is it there ?
[18:23] <lool> dobey: ok, publishing these then
[18:24] <kgunn_> ogra_, yep, that's it thanks....so, guess you gotta pin that ppa and update....
[18:24] <kgunn_> ?
[18:25] <ogra_> it should have higher versions anyway i guess
[18:25] <ogra_> no need for pinning
[18:26] <ogra_> i would flash an image, make it writable, add the ppa and install the required packages ... then disable the PPA, reboot and run the tests
[18:26] <balloons> fginther, can you turn on autopilot checks for dropping letters?
[18:26] <balloons> fginther, http://91.189.93.70:8080/job/dropping-letters-ci/1/
[18:26] <fginther> balloons, ack
[18:26] <balloons> ty :-)
[18:28] <lool> Hmm PPA files are "Pending publication"
[18:28] <lool> will see how long that takes
[18:30] <lool> kgunn_, ogra_: https://launchpad.net/ubuntu/+source/mir/0.0.12+13.10.20130926.1-0ubuntu1
[18:30] <lool> it's in saucy now, just apt-get update to it from an image
[18:30] <ogra_> published already ?
[18:32] <kgunn_> cool thanks
[18:32] <thostr_> asac: just ran AP with the fixes for unity
[18:32] <thostr_> asac: no crashes
[18:33] <thostr_> asac: so, seems all good, meaning no regressions
[18:33] <asac> thostr_: nice!
[18:33] <thostr_> asac: that is line 81 in the landing plan
[18:36] <asac> thostr_: libunity, unity-scope-home are the only sources you touched?
[18:37] <asac> ogra_: cool. did we get a positive on the mako side aas well?
[18:37] <asac> ogra_: do you know if #66 got ever blessed?
[18:38] <ogra_> nope, but i'm willing to test that one to
[18:38] <asac> or banned :)
[18:38] <ogra_> i dont think it did yet
[18:38] <asac> ogra_: how do the results look like?
[18:38] <lool> == Publishing click-package stack to archive ==
[18:38] <lool> but I think it will be caught in freeze
[18:38] <asac> bfiller: was there any breakthrough on the notes-app tests?
[18:38] <ogra_> https://system-image.ubuntu.com/saucy/mako/index.json ... latest blessed one is 65
[18:39] <ogra_> asac, all non community apps are fine ... unity8 is just running ...
[18:39] <bfiller> asac: working it with omer, we see what the problem is but not sure how to fix it yet
[18:39] <bfiller> asac: only happens on mako
[18:40] <ogra_> asac, i have a theory btw ... i suspect my app tests befofre failed because i ran the unity8 one first ... will try to re-run some of the app tests after unity to see if thats true
[18:41] <ogra_> asac, http://paste.ubuntu.com/6159874/
[18:41] <ogra_> nothing that doesnt also fail on the dashboard
[18:42] <asac> right
[18:42] <asac> i also noted that. but we reboot between tests
[18:43] <asac> noticed
[18:43] <ogra_> well, i didnt this morning
[18:44] <ogra_> yay
[18:44] <asac> right. thats true. seems unity is not restarted with same flags or something
[18:44] <ogra_> unity8 passed too
[18:44] <ogra_> so this is good on maguro i'd say
[18:53] <ogra_> asac, yeah, so running notes-app tests after unity8 i get 19 failures ... and i think i also know why
[18:53] <ogra_> (not sure how thats fixable though)
[18:54] <ogra_> the session info (dbus, upstart session socket etc) are set at login time ... via env vars ... if unity restarts at least the upstart session info changes (not surree about the dbus socket) ... but the vars indeed dont get updated
[18:56] <fginther> balloons,
[18:56] <fginther> balloons, http://91.189.93.70:8080/job/generic-mediumtests/490/
[18:56] <mdeslaur> I have a systemd permission fix that probably doesn't impact touch I'd like to upload: LP: #1226509
[18:56] <mdeslaur> lool: do I need to add it to the spreadsheet?
[18:57] <lool> looking
[18:58] <balloons> fginther, ack, weird.. probably a quick fix
[18:59] <lool> mdeslaur: Looks good, adding an entry; you may upload
[19:00] <mdeslaur> lool: thanks
[19:00] <lool> mdeslaur: FYI we're in archive freeze right now, so either you or I will have to get an ack from release team
[19:00] <mdeslaur> lool: yeah, I just asked in #ubuntu-release
[19:01] <seb128> see, lool is there
[19:02] <seb128> just ignoring me on other chans :p
[19:02] <seb128> or :-(
[19:02] <lool> seb128: didn't see your ping, sorry
[19:02] <lool> seb128: where was that?
[19:02] <seb128> lool, no worry
[19:02] <seb128> lool, I was wondering why you were telling people that testing on the n7 is worthless
[19:02] <seb128> lool, it might not be the preferred target, it's still useful testing
[19:02] <seb128> lool, especially for thing that are not hardware dependend
[19:02] <lool> seb128: I told robru it's a secondary citizen and had known breakage
[19:03] <lool> seb128: and wasn't alone in explaining that  :-)
[19:03] <balloons> fginther, pushed a fix.. I'll note the printout still isn't showing the esult
[19:03] <seb128> lool, ok, he told me that you said it was not worth testing the content-hub fixes on it, and he has access to nothing else
[19:03] <lool> seb128: I guess that if things pass on N7, it's a good indication it's likely to pass on N4/galaxy nexus; the reverse is completely false though
[19:03] <robru> lool, yeah, true. but specifically in the hangout this morning you told me to find somebody else to test these things. you didn't say i could test content-hub myself ;-)
[19:04] <robru> blame also didrocks ;-)
[19:04] <lool> didrocks told you to find someone else, but I agree  :-)
[19:04] <lool> we need Nexus 4 tests to confirm things work
[19:04] <seb128> lool, content-hub is nowhere device specific
[19:04] <seb128> *shrug*
[19:04] <seb128> lool, we need to get everybody a n4 if we want every fix to get confirmed there
[19:04] <lool> I think he had to run a bunch of autopilots tests that are fragile across devices though
[19:06] <robru> lool, just mediaplayer_app
[19:06] <robru> dunno if that one is
[19:07] <lool> the app itself is generic, sadly the stack can be quite device specific, especially with hw decode, but fortunately that's broken
[19:28]  * fginther has to step away for an hour or two.
[19:29] <lool> I've updated spreadsheet
[19:29] <lool> mtp isn't in
[19:29] <lool> should be boot tested before we allow it in
[20:05] <rsalveti> lool: can you release the platform stack? just powerd
[20:05] <rsalveti> we need it in so we can respin the android package and unblock powerd for mir
[20:06] <lool> rsalveti: asin publish to archive?
[20:06] <lool> rsalveti: did you test the binaries or same source built yourself?
[20:07] <lool> rsalveti: landing 37?
[20:08] <rsalveti> lool: yes, all deps are already in the archive
[20:08] <lool> rsalveti: Indeed, libhybris is good; publishing now
[20:08] <lool> rsalveti: FYI, we have another barrier just tonight
[20:09] <rsalveti> lool: what do you mean?
[20:10] <lool> rsalveti: archive is frozen; so I have to heads up release team
[20:10] <lool> there will be a cron allowing touch specific packages in soon
[20:11] <rsalveti> lool: ok, thanks
[20:11] <lool> rsalveti: now pending approval by stgraber with his new script
[20:22] <lool> rsalveti: https://launchpad.net/ubuntu/+source/powerd/0.13+13.10.20130926-0ubuntu1 pending publish in proposed
[20:22] <lool> should migrate to release by itself
[20:22] <lool> rsalveti: if you need to upload android with no change, just do so; it should get through automatically now
[20:23] <rsalveti> yup, doing that now
[20:23] <rsalveti> seems powerd was accepted
[20:23] <rsalveti> -queuebot/#ubuntu-release- Unapproved: accepted powerd [sync] (saucy-proposed) [0.13+13.10.20130926-0ubuntu1]
[20:23] <rsalveti> maybe still in proposed
[20:29]  * ogra_ uploads the sdk seed change 
[20:32] <lool> == publishing services stack ==
[20:32] <lool> to get updated mtp
[20:32] <lool> tested here along lxc-andorid-config (in archive)
[20:33] <lool> pff, got to wait til it rebuilds
[20:34] <ogra_> phew, that seed stuff was a beast
[20:34] <ogra_> (and the changelog looks most scary)
[20:36] <rsalveti> looks scary
[20:37] <ogra_> hehe, yeah
[20:38] <ogra_> but it makes everything so much nicer
[20:50] <asac> dont destroy the image :)
[20:50] <asac> thx
[20:50] <asac> :)
[20:50] <ogra_> heh
[20:52] <lool> tired to wait for intel test machine, might come back later to chekc
[21:17] <Saviq> fginther, huh, any idea what's https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1905/console about?
[21:42] <fginther> Saviq, I have no idea what happened there. "dh_auto_test -O--parallel -O--fail-missing" crapped out for some reason
[21:43] <Saviq> fginther, yeah, it looked pretty weird, have restarted, let's see what happens next
[23:16] <lool> == really publishing services stack ==
[23:16] <lool> for mtp
[23:18] <asac> lool: is that all according to the plan :)?
[23:19]  * asac stops worrying for now :)
[23:19] <lool> yes