[00:00] <sergiusens> plars, new image in?
[00:00] <plars> sergiusens: yeah, tests have started running now
[00:24] <sergiusens> plars, any errors so far?
[00:25] <plars> sergiusens: yes, first install on https://jenkins.qa.ubuntu.com/job/saucy-touch_ro-maguro-smoke-install-and-boot/150/console (maguro) failed with adb protocol fault
[00:25] <plars> sergiusens: we get those from time to time
[00:25] <plars> still
[00:25] <plars> mako was fine though, and retrying maguro now
[00:25] <plars> sergiusens: it was actually after the install, was just setting up the network at the time
[00:25] <sergiusens> plars, I guess adb just sucks wrt to data transport
[00:26] <sergiusens> oh
[00:26] <plars> sergiusens: yeah, it's super convenient, but there are certainly some reliability issues that plague us on it
[01:42] <plars> rfowler: so, the maguro appears to have eaten itself again
[01:42] <kgunn> fginther: thanks for the help...saw your post in our mp
[01:42] <plars> rfowler: I suspect it's going to be powered off like you found it this morning
[01:44] <plars> psivaa: on the plus side, I think I got cobbler living and breathing enough to run the lucid jobs again... we'll see.
[01:44] <fginther> kgunn, I'm still watching the builds, hope at least one completes before bed time
[01:44] <plars> fginther: what are you watching?
[01:44] <kgunn> fginther: sure appreciate it
[01:44] <plars> unity I guess?
[01:44] <fginther> plars, upstream merger for mir
[01:44] <plars> ah, mir
[01:44] <kgunn> yeah....good old mir
[01:52] <fginther> kgunn, alan_g, things are green again http://10.97.2.10:8080/job/mir-ci/
[01:53] <kgunn> fginther: \o/
[01:55] <alan_g> fginther: thanks, that looks healthier
[02:01] <veebers> fginther: I realise it's late for you, but this one looks odd; not sure I've seen it before: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-maguro/901/?
[02:01] <veebers> also that other job I pinged you about is now merged. Cheers for that.
[02:06] <fginther> veebers, the bulk of the unity8 tests did not run
[02:07] <veebers> fginther: yeah there appears to be some odd (read: haven't seen before) module import error happening
[02:11] <fginther> veebers, http://bugs.python.org/issue15030
[02:12] <fginther> veebers, I wonder if this hit stale pyc files. We don't reflash after running tests, it just uses apt-get to revert to the packages from the archive
[02:12] <veebers> fginther: ah very good point. I wouldn't be surprised if that's it
[02:14] <fginther> veebers, how do we fix that? do the pyc files get removed when a package is removed, perhaps when the parent dir is removed?
[02:15] <veebers> fginther: hmm, i don't know that answer to that (package removed). Ideally we would re-flash after each run but I understand that has issues in itself
[02:15] <veebers> surely if you install a newer or even different package the .pyc get re-generated
[02:18] <fginther> veebers, hmm, I'll ask thomi about it in the morning
[02:19] <veebers> fginther: cool, thanks
[08:33] <mandel> morning!
[08:33] <sil2100> Morning! Ah, meeting
[08:40] <lool> hmm is it over?
[08:46] <lool> I guess I have the wrong HO link
[08:58] <lool> sil2100: are you taking care of removing the webbrowser-app dependency?
[08:58] <lool> sil2100: it shouldn't be pulled in the desktop image; we can seed webbrowser-app directly in the Touch seed instead
[08:58] <lool> in fact it is already
[09:01] <sil2100> lool: yes
[09:02] <sil2100> lool: I'm actually reverting the commits now sadly, since the code needs to be rewritten in a way that the webbrowser-app is not necessary
[09:05] <didrocks> sil2100: please ping dbarth about it as well
[09:15] <ogra> lool, i'm looksing for a tester for the fix on bug 1226825 (since you just mentioned mtp) :)
[09:28] <Mirv> sil2100: https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/apps_add_libupstart-app-launch1/+merge/186274
[09:33] <lool> ogra: I was shocked that Nexus 4 came up in Nautilus when I plugged it in  ;-)
[09:33] <lool> I thouhgt I had plugged the wrong device for a sec
[09:34] <ogra> haha
[09:34] <ogra> well, if you reboot you will be left with 3 mtp error popups ... the above should fix that
[09:35] <Mirv> sil2100: https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/saucy_qa_add_python-psutil/+merge/186278
[09:45] <lool> ogra: oh gosh, I tried to apt-cache rdepends --installed --recurse libqt5organizer5 libqt5contacts5|sort -u, and that already lists almost everything
[09:46] <ogra> lool, heh i would just upgrade the installed packages
[09:46] <ogra> (note that touch uses --no-install-recommends by default)
[09:46] <lool> ogra: this was to identify the packages that are using the lib
[09:47] <ogra> ah
[09:47] <lool> ogra: note: --installed, this will limit output to things actually on the image
[09:48] <ogra> well i guess the pim stuff is some low level Qt5 dep
[10:50] <sil2100> asac: after testing on desktop and informing unity upstream about the failing tests, I published the scopes things
[10:51] <asac> sil2100: thanks! ... do you have a bug for that?
[10:51] <asac> i think we should file one with the log if you have
[10:51] <asac> and record it
[10:52] <sil2100> https://bugs.launchpad.net/unity/+bug/1227056
[10:52] <sil2100> Yes, this I have
[11:02] <asac> sil2100: did you start on the indicator etc. stuff yet?
[11:03] <asac> otherwise thostr had one clarification that we might want to take into account
[11:03] <sil2100> asac: I'm listening ;)
[11:03] <sil2100> It's best to land as much as we can, so I can re-do if needed
[11:04] <asac> right
[11:04] <asac> sil2100: its the mediascanner thing
[11:04] <asac> its not really indicator, but also from thostr
[11:04] <asac> so you have a single escalation point
[11:04] <asac> sil2100: he said we just need the one package that has the merge already in trunk
[11:04] <sil2100> In mediascanner?
[11:04] <asac> sil2100: thats line 33 in asks
[11:05] <asac> sil2100: it just needs the mediascanner source
[11:05] <asac> sil2100: can you check if thats built?
[11:05] <asac> and if that has the change he hopes it has? :)
[11:05] <sil2100> asac: ok, so I upgrade that as well, test and will release along that - it's built so I just need to test that
[11:06] <sil2100> Will do that in at max 30 minutes
[11:06] <asac> sil2100: cool. have put it in landing plan
[11:08] <sil2100> Awesome
[11:31] <asac> didrocks: does qtubuntu go into the mir ppa right now?
[11:31] <asac> or would that flow to daily-build still?
[11:31] <asac> asking because i see something might land there for tomorrow
[11:31] <asac> that we probably want regardless of mir
[11:32] <didrocks> asac: so, we do have trunk flowing in daily-build
[11:32] <didrocks> asac: there is a rebuild of trunk everytime they push a new mir in their ppa as well
[11:32] <didrocks> but we never commit this change
[11:34] <asac> didrocks: ok so qtubuntu can land without mir
[11:34] <asac> thanks!
[11:34] <didrocks> yep
[11:34] <didrocks> yw
[11:39]  * Mirv reflashes to try AP on device again
[11:57] <rfowler> plars: were you having issues getting to maguro-01?
[11:57] <rfowler> plars: because it was up
[11:59] <plars> rfowler: no, it was 02
[11:59] <plars> rfowler: I moved everything to maguro-01
[12:00] <ogra> plars, it didnt happen again on later images ?
[12:00]  * ogra forgot to ask if his fix worked
[12:00] <rfowler> plars: maguro-01 was off... i reflashed it
[12:01] <plars> rfowler: what?
[12:01] <plars> rfowler: I'm confused
[12:01] <asac> Mirv: sil2100: quick checkpoint where we stand, what is causing troubles etc.
[12:01] <plars> rfowler: you just said that maguro-01 was up, and then that it was off and you reflashed it
[12:02] <asac> Mirv: i think i could try testing applications if you still fight autopilots. just would know how to best install the right things
[12:02] <rfowler> plars: sorry 02
[12:02] <plars> ogra: so, the problem I had yesterday where I lost adb for a while - haven't seen that again
[12:02]  * asac starts flashing latest in any case
[12:02] <plars> right
[12:02] <rfowler> too early
[12:02] <plars> ok
[12:02] <plars> that makes more sense :)
[12:02] <ogra> plars, yay, thanks !
[12:03] <plars> ogra: we are seeing something with maguro where it sometimes ends up in a powered off state (is that what happened again last night with maguro-02 rfowler?)
[12:03] <sil2100> asac: lunch ;) But soon over
[12:03] <asac> sil2100: enjoy :)
[12:04] <plars> ogra: I think this is similar to the situation some of us were talking about at the sprint where if you have the maguro off, and plugged in, then try to turn it on - it will just show the battery meter
[12:04] <rfowler> plars: yes
[12:04] <ogra> plars, that sounds more like a charging issue though
[12:04] <asac> ogra: so i think unity-scope and libunity are in
[12:04] <plars> you have to pull the battery, unplug, etc
[12:04] <asac> lets do an image
[12:04] <asac> while folks test the next lot
[12:04] <rfowler> plars: yes
[12:04] <plars> rfowler: was this the same maguro that had the power problem yesterday too?
[12:04] <ogra> asac, ok, note you will also get gstreamer-pulse-foo-bar
[12:04] <asac> exactly
[12:04] <asac> thats the other landing i hoped to pick up before the next big shot
[12:04] <ogra> right
[12:04] <rfowler> plars: they both did that yesterday
[12:05] <ogra> i would like to get my mtp upstart job fix in today too
[12:05] <plars> rfowler: ok, so it's not specific to just one of the maguros
[12:05] <plars> :(
[12:05] <asac> sil2100: anything beyond unity-scope-home and libunity that we waited for?
[12:05] <asac> on scopes #1?
[12:05] <plars> as much as I'd hate to have a bad device, having one that we could point to as being bad would be nicer than a problem across all of that type
[12:06] <asac> ogra: sure, but if we can do that mtp thing later. feel we should double check with utah
[12:06] <rfowler> plars: they battery indicator showed the battery being low... but swiping over it said it was full
[12:06] <Mirv> asac: if you've a device usable, please try http://pastebin.ubuntu.com/6123606/ and then the autopilot tests.
[12:06] <ogra> asac, it only makes sure mtp exists on shutdown ... no risk for anything in the running image
[12:07] <asac> Mirv: cool. i assume you dont have the list of autopilot tests?
[12:07] <ogra> but i want to wait for davmor to finish testing it for me
[12:07] <asac> :)
[12:07] <asac> Mirv: guess i can guess them
[12:07] <plars> rfowler: ambiguity++
[12:07] <asac> ogra: sounds good
[12:07] <Mirv> that updates the apps being tested
[12:07] <ogra> so am i good to pull the trigger ?
[12:07]  * ogra has the finger on it 
[12:07] <Mirv> asac: just a second
[12:07] <asac> Mirv: yeah. i am still flashing, but will do after
[12:08] <rfowler> plars: now it's showing full battery
[12:09] <Mirv> asac: http://pastebin.ubuntu.com/6123620/ added notes app to be upgraded and a list of autopilot tests nsmrd
[12:09] <Mirv> I've just reflashed and hopefully my previous problems are gone, I'm now testing the autopilot itself again
[12:14]  * ogra gets a numb arm holding his hand still above the button ... 
[12:14] <ogra> asac, ^^^
[12:14] <plars> rfowler: I am still concerned about the temperature warnings we get on maguro frequently
[12:14] <plars> rfowler: http://paste.ubuntu.com/6123644/
[12:15] <Mirv> ok, I'm planning to publish the QA stack now, after successful unity8 autopilot run
[12:16] <Mirv> didrocks: the packaging changes would need ack http://10.97.0.1:8080/view/cu2d/view/Saucy/view/QA/job/cu2d-qa-saucy-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_autopilot_1.3.1+13.10.20130918-0ubuntu1.diff
[12:18] <asac> ogra: for the image?
[12:18] <asac> ogra: we dont know if all scope packages landed
[12:18] <asac> ogra: but i cant find anything obvious scope in proposed excuses
[12:18] <asac> so lets go
[12:18] <ogra> ok, i'll wait
[12:18] <ogra> lol
[12:18] <asac> unless sil2100 comes along
[12:19] <asac> ogra: give him 5 minutes
[12:19] <asac> to say something is not in there :)
[12:19] <asac> otherwise go
[12:19] <ogra> note that stuff being out of proposed doesnt mean its in the archive
[12:19] <Mirv> asac: unity-scope home in release pocket https://launchpad.net/ubuntu/saucy/+source/unity-scope-home/6.8.2+13.10.20130918.1-0ubuntu1 same for libunity https://launchpad.net/ubuntu/saucy/+source/libunity/7.1.1+13.10.20130918.1-0ubuntu1
[12:19] <asac> Mirv: right. also libunity is needed
[12:19] <ogra> there is usually a publisher run afterwards that takes a few minutes
[12:19] <Mirv> asac: "same for libunity" ^
[12:19] <asac> ogra: you could check on libunity and unity-scope-home to be sure
[12:20] <Mirv> asac: does your irc crop long lines?-)
[12:20] <asac> my brain and habtics do that unfortunately
[12:20] <asac> i will try harder
[12:22] <cjwatson> If it's not mentioned in excuses at all (as it isn't here) then it must be fully published to release
[12:23] <cjwatson> It's only ambiguous if you see current excuses/output that say they're about to migrate it
[12:23] <ogra> cjwatson, ah, so the publisher updates the page ?
[12:23] <cjwatson> ogra: No
[12:23] <cjwatson> ogra: But proposed-migration takes the published archive as its input; if a package isn't mentioned at all, then that must mean it doesn't have a newer version in -proposed in the published archive
[12:24] <cjwatson> IOW there's already been a publisher run and p-m has run after it
[12:24] <ogra> ah
[12:24] <ogra> got it
[12:24] <ogra> ok, then i can trigger a build :)
[12:24] <ogra> and off we go
[12:26] <asac> Mirv: so i think the applications was also supposed to take the new keyboard
[12:26] <asac> i assume i just have to install ubuntu-keyboard as well?
[12:27] <rfowler> plars: I don't have a way to measure temp...
[12:29] <plars> rfowler: there's a builtin temperature probe on the device - I don't think we see this normally on mako, just maguro
[12:29] <plars> rfowler: I pointed sarnold at it again, maybe he has some ideas
[12:29] <rfowler> ok
[12:30] <rfowler> plars: maybe i can leave the back off and blow a fan at them
[12:30] <rfowler> little active cooling
[12:30] <plars> rfowler: strap a peltier cooler to them? :)
[12:31] <plars> it shouldn't be needed
[12:31] <plars> rfowler: I just wonder if we're not hitting a battery drain issue, but rather a thermal shutdown
[12:31] <plars> rfowler: I seem to recall something sarnold added recently to shutdown if the temp got too high, and I think that might be what we're hitting
[12:32] <Mirv> asac: ok, I didn't realize that as it's in the services stack instead of apps stack. it's ready in the PPA as well, though.
[12:32] <rfowler> plars: or it thinks the battery is draining faster than it actually is?
[12:32] <asac> Mirv: right ... lets double check on all the bfiller entries one more time in ask
[12:32] <rfowler> plars: it showed empty when I reflashed it but when I plugged it in it went to full
[12:33] <asac> Mirv: so i see: gallery, dialer-app, history-service, messaging-app, ubuntu-keyboard, qtpim-opensource-src
[12:33] <rfowler> plars: but probably more likely temp
[12:33] <asac> sorry.. and... notes-app, camera-app and mediaplayer
[12:33] <asac> Mirv: ^^
[12:33] <fginther> morning
[12:36] <Mirv> asac: ok... messaging-app is in the phone stack, history-service again in the services stack. even phone stack is ready for testing. qtpim is separately handled.
[12:36] <plars> rfowler: there's an indicator-power change in the pipeline, not sure if that could have anything to do with the strange reading's you're seeing, but maybe
[12:37] <rfowler> plars: how do I check said pipeline
[12:39] <plars> rfowler: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc#gid=0
[12:39] <rfowler> plars: thanks
[12:41] <Mirv> asac: added messaging-app, history-service, dialer-app and ubuntu-keyboard to the pastebin at http://pastebin.ubuntu.com/6123730/
[12:46] <asac> yeah. /me sees issues with notes_app howver
[12:54] <lool> Hi folks
[12:54] <lool> So url-dispatcher stuff has a rather deep chain
[12:55] <lool> we want an updated qtubuntu to leverage it
[12:55] <lool> and we need an updated Mir platform API lib for it to work with either backends
[12:55] <lool> I've updated line 21 of the asks to list the relevant merge proposals
[12:56] <lool> didrocks: is the upstream merger still auto?
[12:56] <didrocks> lool: yeah, fginther is in charge of that
[12:56] <lool> didrocks: sorry, let me repharse, will https://code.launchpad.net/~thomas-voss/platform-api/ensure-symbols-are-included/+merge/186291 be automerged + uploaded to daily PPA?
[12:57] <didrocks> lool: yeah, in 2 steps
[12:57] <lool> ack
[12:57] <didrocks> it will get merged first
[12:57] <lool> both of these are still auto
[12:57] <didrocks> then, in the next daily release tick, it will go in the ppa
[12:57] <didrocks> yeah
[12:57] <lool> just the copy from PPA to archive isn't auto
[12:57] <lool> ok
[12:57] <didrocks> right
[12:57] <lool> can we push it to PPA right now?  it can go alone, and it will allow bulding the qtubuntu mp
[12:58] <didrocks> lool: next tick is in an hour, I would prefer we keep the dep order
[12:59] <didrocks> is that so urgent it needs to be in the PPA right now?
[12:59] <didrocks> (also, we have our landing order)
[12:59] <didrocks> is there a request for it?
[12:59] <asac> didrocks: so ralsina believes he is kind of ready for enabling two components in stack
[13:00] <didrocks> you mean, 2 new components?
[13:00] <asac> didrocks: lp:clickmanager-plugin lp:click-update-manager
[13:00] <asac> those... he worked with sil to prep packaging etc.
[13:00] <lool> didrocks: there is a landing ask for it, but to keep preparing it as fast as possible I was trying to get the builds done as soon as possible
[13:00] <didrocks> asac: right, sil pinged me few minutes ago to preNEW them
[13:00] <asac> right. preNEW has to happen
[13:00] <asac> ok
[13:00] <asac> didrocks: i assume you organize preNEWing through your spreadsheet as well usually?
[13:00] <lool> adding API in one package + using it another requires two ticks to land it seems
[13:01] <didrocks> asac: right
[13:01] <lool> 1 hour isn't much, that's ok
[13:01] <didrocks> lool: well, we have 250 components, imagine if everyone wants their stuff building right now? ;) I would think, if there is no urgency, this can just wait for an hour (not that long) to keep the dep order right in case something happens
[13:01] <didrocks> lool: you can land that in one tick, but soon, we'll first 2 right
[13:01] <didrocks> force*
[13:04] <ogra> new image is up on cdimage
[13:05] <Mirv> didrocks: I pinged you about the QA stack's packaging changes 50mins ago, can you check it?
[13:06] <didrocks> Mirv: it slept through my pings, can you paste the link again?
[13:07] <Mirv> didrocks: http://10.97.0.1:8080/view/cu2d/view/Saucy/view/QA/job/cu2d-qa-saucy-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_autopilot_1.3.1+13.10.20130918-0ubuntu1.diff
[13:08] <didrocks> Mirv: 61
[13:08] <didrocks> -1
[13:08] <didrocks> python-psutil is in universe
[13:09] <didrocks> and the source is in main, isn't it?
[13:09] <didrocks> Mirv: can you check with upstream if this is really needed? (and think next time to check this universe/main stuff ;))
[13:10] <didrocks> asac: lool: so, we have live results now: http://people.canonical.com/~platform/cu2d/results
[13:10] <Mirv> didrocks: ok. autopilot source seems to be in main, yes.
[13:11] <didrocks> and you can see what is currently building (if any), disabled, blocked by other stacks…
[13:12] <didrocks> (you can see as well raring, experimental, head… in addition to saucy)
[13:12] <didrocks> Mirv: mind working that on the spreadsheet as a reminder?
[13:12] <didrocks> writing*
[13:13] <asac> oha
[13:13] <Mirv> didrocks: just doing that
[13:13] <Mirv> asac: so moving python-autopilot below from the scheduled point since it cannot be released because of the added python-psutil dependency
[13:13] <Mirv> thomi: ^ https://bugs.launchpad.net/autopilot/+bug/1227118
[13:13] <thomi> Mirv: since when has autopilot been in main?
[13:13] <asac> Mirv: whats the problem with that depends
[13:13] <didrocks> Mirv: please, do recheck the rest, I just stopped at the first error
[13:14] <Mirv> thomi: the source seems to be
[13:14] <thomi> Mirv: hmmm, that's news to me!
[13:14] <Mirv> asac: a package in main can't build-depend on a package in universe
[13:14] <thomi> we really do need psutil, but I see no reason why AP needs to be in main?
[13:14] <thomi> unless I'm forgetting something?
[13:14] <Mirv> didrocks: ok. do you know when autopilot source was promoted to main, and why?
[13:15] <cjwatson> It's a critical part of our infrastructure, it's silly for it not to be in main
[13:15] <thomi> hmm, maybe because unity build depends on AP?
[13:15] <Mirv> probably something like that, I think it's pretty recent
[13:15] <cjwatson> I don't see the MIR bug, oddly
[13:15] <didrocks> right, what cjwatson said
[13:15] <cjwatson> That said
[13:15] <cjwatson> autopilot is not in main
[13:15] <didrocks> even if I don't remember about the promotion itself
[13:15] <cjwatson> https://launchpad.net/ubuntu/+source/autopilot/+publishinghistory
[13:16] <thomi> so... we're good to go?
[13:16] <cjwatson> Mirv: I think you are confused for some reason ... maybe looking at the wrong field somewhere?
[13:16] <didrocks> argh, scratch that
[13:16] <didrocks> I know what happened
[13:16] <didrocks> the ppa line…
[13:16] <didrocks>         500 http://ppa.launchpad.net/ubuntu-unity/daily-build/ubuntu/ saucy/main amd64 Packages
[13:16] <didrocks> -> main
[13:16] <cjwatson> Yeah, but PPAs only have main
[13:16] <didrocks> hence the confusion
[13:17] <didrocks> ok, let's proceed and continue the review
[13:17] <didrocks> but we still should at some point put autopilot in main
[13:17] <didrocks> (but I think not for 13.10)
[13:17] <Mirv> in case I'd at one point understand the LP terminology, why does https://launchpad.net/ubuntu/+source/autopilot/ have component (with '*') main but https://launchpad.net/ubuntu/+source/python-psutil has universe?
[13:18] <cjwatson> That's the component in the debian/control file
[13:18] <cjwatson> i.e. you haven't specifically written "Section: non-free/admin" or whatever
[13:18] <cjwatson> It makes more sense for imports from Debian
[13:18] <didrocks> Mirv: ok, +1 on the rest, please publish
[13:18] <Mirv> didrocks: ok
[13:19] <plars> image tests are running now on 55
[13:19] <thomi> anyone mind if I close that bug then?
[13:19] <didrocks> thomi: feel free
[13:19] <thomi> oh, you beat me to it :)
[13:19] <cjwatson> I forget why python-psutil has universe there, but anyway, that field is not the one you want to read, ever
[13:19] <thomi> fastest bugfix *evar* ;)
[13:19] <cjwatson> At least not for this kind of thing
[13:19] <Mirv> thomi: ;)
[13:20] <cjwatson> You want to look at the per-series component overrides, either in the table below or in +publishinghistory
[13:23] <didrocks> sil2100: you are missing the multiarch stenzas on qtdeclarative5-ubuntu-click0.1
[13:23] <sil2100> didrocks: ACK, fixing that
[13:23] <didrocks> sil2100: we can start promoting click-update-manager, this one is cleared
[13:23] <didrocks> so either both at the same time with your fix
[13:24] <didrocks> or just one by one
[13:24] <didrocks> as you prefer
[13:24] <didrocks> but for me, it's a +1
[13:24] <sil2100> Awesoooome, I have a merge ready so I just push that change to it and we're dune, since I have the bootstrapping ready
[13:24] <didrocks> great ;)
[13:24] <Mirv> asac: ok QA done but I need to continue with the apps tomorrow. on the device I'm getting all kinds of errors on apps (running the old autopilot now), I guess I'll need to at least reboot between each try or something like that, and try the old versions
[13:28] <sil2100> didrocks: final merges then! https://code.launchpad.net/~sil2100/click-update-manager/finalization/+merge/186311 , https://code.launchpad.net/~sil2100/clickmanager-plugin/finalization/+merge/186312 and the grand finale: https://code.launchpad.net/~sil2100/cupstream2distro-config/new_click_packages_daily/+merge/186313
[13:28] <sil2100> ;)
[13:29] <Mirv> sil2100: oh btw there was something wrong with the cupstream2distro-config according to merger, probably caused by fginther's direct pushes to trunk last night. you may need to manually merge after approval.
[13:29] <sil2100> :<
[13:29] <sil2100> Mirv: thanks for the info
[13:30] <sil2100> Mirv: I remember yesterday Francis did some manually merging as well
[13:30] <sil2100> I had hoped it was fixed already now
[13:30] <sil2100> asac: ok, testing of the new indicators, mediascanner and hud looks ok
[13:30] <fginther> sil2100, Mirv, just to deflect the blame a bit, the errors are caused by the duplicate branches in the experimental release :-)
[13:30] <sil2100> asac: I tried testing hud, but it seems hm, hard to do
[13:31] <sil2100> asac: since it's not currently working on touch from what we noticed
[13:31] <fginther> sil2100, Mirv I'm working on a workaround
[13:31] <sil2100> fginther: ah, then it's didrocks fault!
[13:31] <sil2100> HA!
[13:31]  * sil2100 points at didrocks 
[13:31] <Mirv> fginther: he, ok :) so it's going to be like that for a little while.
[13:31] <fginther> Mirv, hopefully only 30 more minutes or so.
[13:31] <Mirv> I probably didn't have merges for a couple of days before today, so I only quickly looked the latest commits there
[13:33] <asac> sil2100: if it doenst regress the rest
[13:33] <asac> its fine to land hud
[13:33] <asac> sil2100: it never worked, so it cant be worse
[13:33] <asac> unless its gone completely now
[13:33] <sil2100> ;)
[13:34] <didrocks> sil2100: it's this configuration, upstream merger used to support it
[13:34] <didrocks> sil2100: it seems it doesn't anymore
[13:34] <didrocks> (without warning on the change)
[13:35] <didrocks> sil2100: grrr, I don't have access to upstream trunk
[13:35] <didrocks> sil2100: can you ensure our team has access please?
[13:35] <didrocks> sil2100: otherwise, we won't release their work
[13:36] <sil2100> didrocks: ouch
[13:36] <sil2100> didrocks: ok, will make sure that's done
[13:36] <didrocks> thanks
[13:37] <sil2100> didrocks: btw. can I get an ACK http://10.97.0.1:8080/view/cu2d/view/Saucy/view/Indicators/job/cu2d-indicators-saucy-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-power_12.10.6+13.10.20130918-0ubuntu1.diff ?
[13:37] <didrocks> sil2100: I still don't see the mention of the FFe in debian/changelog
[13:37] <didrocks> am I missing anything?
[13:38] <sil2100> Shiiit
[13:38] <Mirv> sil2100: I pushed a changelog entry in there 3h ago
[13:38] <sil2100> Right, and there was a tick that got skipped
[13:39] <Mirv> sil2100: while at it you can also double-check the changelog entry text
[13:39] <sil2100> hmmm, no mention of FFe in that?
[13:40] <sil2100> didrocks: is this changelog entry enough? http://bazaar.launchpad.net/~indicator-applet-developers/indicator-power/trunk.13.10/revision/200
[13:40] <Mirv> sil2100: not directly, I wasn't sure about the wording
[13:40] <ogra> asac, hmm, i can't edit the spreadsheet
[13:41]  * ogra just wanted to addteh two bugfixes
[13:41] <asac> ogra: done
[13:41] <ogra> thx
[13:41] <asac> -> rw for you
[13:41] <didrocks> sil2100: it miss the bug number for the FFe we were lacking and I pasted in the chat
[13:41] <didrocks> this morning
[13:41] <didrocks> sil2100: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1215980
[13:42] <sil2100> Ok, preparing a direct push then
[13:43] <sil2100> didrocks: I'll just add the bug number to the changelog Mirv prepared I guess
[13:51] <asac> so the only test in the application stack failing is notes_app
[13:51] <asac> asked osmonon to check
[13:51] <ogra> osmonononon ? :)
[13:52] <asac> sil2100: is the indicators testing going well?
[13:52] <asac> you said its all good actually? except the scopes you dont know?
[13:52] <asac> then lets go for that and checkpoint it
[13:53] <asac> ogra: not sure... he is not in this channel so tab doesnt work
[13:53] <ogra> heh
[13:53] <sil2100> asac: they're good, but one commit that didrocks wanted was wrong so I need to rebuild
[13:54] <asac> sil2100: we cant release with that?
[13:54] <sil2100> No
[13:54] <asac> sil2100: what does it break?
[13:54] <sil2100> Nothing, changelog formalities
[13:54] <asac> then we can release
[13:54] <didrocks> asac: the release team will revert it
[13:54] <sil2100> We can't
[13:54] <didrocks> there is no link to the FFe
[13:55] <asac> omg
[13:55] <didrocks> the one I asked this morning
[13:55] <asac> hell
[13:55] <asac> thats stupid
[13:55] <asac> we didnt reference it in the changelog?
[13:55] <asac> and now we have to do the whole validation again?
[13:55] <sil2100> didrocks: I added a (FFe bug - LP: #blabla), is that enough?
[13:55] <asac> man...
[13:55] <asac> cjwatson: is that true?
[13:55] <ogra> rules :)
[13:55] <sil2100> asac: not whole validation, I guess as long as it builds it's ready
[13:55] <asac> we basically spend 4 hours validating those packages, got green light
[13:55] <didrocks> sil2100: it's enough for me
[13:55] <asac> and just want to push the button... now we respin and have to revalidated everything :(
[13:56] <ogra> asac, for a changelog addition ?
[13:56] <asac> yues
[13:56] <ogra> just make sure the upload has no code changes
[13:56] <didrocks> asac: why revalidating? we can just do one quick test (if the build-deps changes)
[13:56] <sil2100> Right
[13:56] <didrocks> and just rebuild that component
[13:56] <asac> didrocks: ok... which package is rebuilding?
[13:56] <asac> thought we rebuild the whole stack
[13:56] <didrocks> asac: indicator-power
[13:56] <sil2100> indicator-power
[13:56] <asac> ok
[13:56] <didrocks> asac: no, we can rebuild just part of the stack
[13:56] <asac> goodie
[13:56] <didrocks> daily release supports that
[13:56] <asac> so we will push the button in 30 minutes?
[13:56] <asac> before stuff bitrots?
[13:57] <didrocks> 40 minutes I would say
[13:57] <asac> didrocks: we might not be able to capture the stuff we tested if folks commit
[13:57] <asac> to trunk
[13:57] <didrocks> time for building + publish in the ppa + 10 minutes of AP tests
[13:57] <asac> so we have to start over if anyone from indicator team commits anything
[13:57] <didrocks> asac: well, we know which version we tested
[13:57] <sil2100> asac: in the meantime I'll publish mediascanner and hud if you don't mind
[13:57] <didrocks> let me check it
[13:57] <asac> didrocks: ok ... for everything we know the versions?
[13:57] <didrocks> it's 1 min
[13:57] <didrocks> less time that discussing it
[13:57] <asac> maybe we shoudl record exactly the version when we test so we can actually publish what we tested
[13:57] <ogra> asac, look like i have time to push the mtp fix then ... has been tested and seems to be fine
[13:58] <asac> didrocks: right. in general i think we should however, record
[13:58] <didrocks> so http://people.canonical.com/~platform/cu2d/results
[13:58] <asac> which versions we validate
[13:58] <didrocks>   * Automatic snapshot from revision 200
[13:58] <asac> as we might have new stuff all the time
[13:58] <asac> lets see how we can work that in
[13:58] <ogra> (line 43 on the "landing asks")
[13:58] <didrocks> indicator-power is at rev 201
[13:58] <didrocks> rev 201 being sil2100's changelog modificatoin
[13:58] <asac> ogra: are sure its super safe?
[13:58] <sil2100> I just added one commit with the FFe bug
[13:58] <didrocks> modification*
[13:58] <didrocks> so all good
[13:58] <didrocks> sil2100: rebuilding indicator-power only?
[13:59] <sil2100> didrocks: yep
[13:59] <asac> ogra: we have so many things we still need to land... you can put it in etc.
[13:59] <sil2100> :)
[13:59] <asac> just your call
[13:59] <ogra> asac, i tested mako, davmor tested maguro, no regressions in booting or rebooting, mtp still works fine
[13:59] <ogra> doing then :)
[13:59] <asac> if you want all of us to firedrill with likelyhood of > 0% :)
[13:59] <asac> ok do it
[13:59] <ogra> -10%
[13:59] <asac> haha
[13:59] <asac> heard that before
[13:59] <ogra> :)
[13:59] <didrocks> I would say
[13:59] <didrocks> makes 2 tests
[13:59] <didrocks> if they are fine, it means that nothing too strong changed in the build-dep
[14:00] <didrocks> and we can go & publish
[14:02] <fginther> sil2100, didrocks, https://code.launchpad.net/~fginther/cupstream2distro-config/relax-branch-validation/+merge/186324  - allows duplicate branches under 'experimental'
[14:02] <didrocks> fginther: do you want me to validate? Is there anyone else with a better view on the code than us?
[14:03] <cjwatson> asac,didrocks: uh?  the release team won't revert something just because you forgot to mention the FFe in the changelog
[14:03] <cjwatson> just mention it on #ubuntu-release or something
[14:03] <sil2100> Too late!
[14:03] <fginther> didrocks, just making you aware, once this lands, we can rerun the other blocked MPs
[14:04] <cjwatson> we have enough rules without people making up new ones
[14:04] <didrocks> cjwatson: already happened in the past
[14:04] <didrocks> a bug wasn't listed
[14:04] <cjwatson> didrocks: it's more likely if you don't explain what's going on
[14:04] <didrocks> and the upload was backed out
[14:04] <cjwatson> didrocks: and if nobody can be tracked down who knows what's going on
[14:05] <cjwatson> didrocks: I'm not going to discuss vague non-specific references to past events, sorry
[14:05] <cjwatson> no doubt there was more to it than that
[14:05] <didrocks> cjwatson: hence better to ensure that everything is cleaned and the bug is attached, isn't it?
[14:05] <cjwatson> and everyone knows there's a general ffe for touch-specific things anyway
[14:05] <cjwatson> didrocks: sure, it's *better*, but I'm not having you say "the release team will do <unreasonable thing>" and not challenge it, sorry
[14:06] <asac> ok thanks
[14:06] <asac> cjwatson all good
[14:06] <didrocks> cjwatson: this component is shared between desktop and touch
[14:06] <didrocks> it's not a touch-specific thing
[14:06] <cjwatson> even so, usually what happens with this kind of thing is that somebody asks if anyone knows what's going on with such-and-such an upload
[14:07] <cjwatson> the only release team reverts I'm aware of is where it caused some problem and nobody can be tracked down to explain it
[14:07] <didrocks> right, and it was during my night
[14:07] <asac> didrocks: you did the right thing though :)... i thought we respun the whole stack
[14:07] <cjwatson> so if you realise you've forgotten a bug in a changelog and have already validated, just drop a note on #ubuntu-release to explain it
[14:07] <cjwatson> rather than assuming bad faith
[14:08] <didrocks> cjwatson: I wasn't assuming bad faith, just trying to get everything clean and up for the release team
[14:08] <asac> right
[14:08] <didrocks> sorry that you took it as a critizim, it wasn't at all
[14:08] <cjwatson> it wasn't so much that I took it as a criticism, it's that I don't think it's in general true :)
[14:08] <asac> all good. was miinterpretations of few things :)
[14:08] <cjwatson> maybe it was true in a couple of specific instances with extenuating circumstances
[14:09] <asac> now we know that release team is super pragmatic
[14:09] <asac> which doesnt mean we shouldnt keep highest standards :)
[14:11] <ogra> asac, here is another quick fix that wont harm anything and woudl be good to have soon https://code.launchpad.net/~sergiusens/ubuntu/saucy/lxc-android-config/localbridge/+merge/186325
[14:13] <sil2100> didrocks: btw. related to no access to upstream trunk... ubuntu-download-manager is also part of ~ubuntuone-hackers and we're daily releasing that
[14:13] <didrocks> sil2100: yeah, and I already mentionned that it's an issue
[14:13] <didrocks> and we should fix it now
[14:13] <sil2100> didrocks: ACK, poking the admin but still no response
[14:13] <didrocks> it's the only team we don't have trunk access to
[14:13] <asac> ogra: everything is closed for this run
[14:13] <asac> we have like the whole spreadsheet almost done
[14:13] <sergiusens> asac, until when?
[14:14] <asac> i wont take any risk
[14:14] <asac> sergiusens: until we have what we currently land in and an image kicked
[14:14] <asac> sergiusens: unforutunately, I lack data to predict how long such a big landing takes
[14:15] <asac> sergiusens: so i have finished application validation
[14:15] <asac> only notes will not go in
[14:15] <asac> indicators and hud are also in
[14:15] <asac> more or less.. we just wait for a changelog respin
[14:15] <asac> just add your stuff to the asks
[14:15] <asac> and we can talk in a couple hours
[14:15] <asac> unless you feel its more urgent than me having food :)
[14:15] <ogra> asac, i'm on it
[14:17] <didrocks> asac: ogra: btw, as told, you can see without diving into jenkins that the indicator stack is building: http://people.canonical.com/~platform/cu2d/results
[14:18] <didrocks> (and we can see anotated sil2100's changelog as well)
[14:18] <asac> didrocks: i think thats awesome :)... i just need a quiet moment to take a look and digest that :)
[14:18] <asac> ah nice
[14:18] <asac> i spotted it
[14:18] <asac> so guess just need to find someone to make that beautiful
[14:18] <asac> didrocks: how often is that updated?
[14:18] <didrocks> asac: every minute
[14:19] <asac> didrocks: can you include the timestamp of last update right on top?
[14:19] <asac> even if its every minute it helps to spot in case this service stops working
[14:19] <didrocks> asac: it's right in the bottom :p
[14:19] <didrocks> but I can move it to the top if needed
[14:19] <asac> didrocks: no :)
[14:20] <didrocks> asac: I can make it like my other tools in term of ajaxy-css: http://people.canonical.com/~platform/design/
[14:20] <asac> its all great
[14:20] <asac> thanks
[14:20] <didrocks> yw
[14:20] <didrocks> (you can click and have transitions)
[14:20] <asac> yeah. thats nice
[14:20] <didrocks> just will need some time to move that from a script to something beautiful
[14:21] <asac> just think that we would like to look at this page every day a few times to support our decision making on whats landing next and what is ready etc.
[14:21] <asac> dont hurry on that one
[14:21] <asac> i am sure we will learn more requirements during the next days
[14:21] <asac> on what we really want to see
[14:21] <didrocks> yeah, I'm appending to my list rather than prepending :p
[14:21] <didrocks> yep
[14:21] <asac> sil2100: didrocks: ok my local testing finished for: http://pastebin.ubuntu.com/6123730/
[14:21] <asac> all are good, except notes
[14:22] <asac> we should hold that app back
[14:22] <asac> ubutu_keyboard i didnt run because its known to not work
[14:22] <asac> but thats ok
[14:22] <sil2100> asac: ok, I pushed mediascanner and hud already, but waiting for indicators to rebuild
[14:22] <asac> nice
[14:22] <asac> sil2100: let me retry notes one more time
[14:22] <asac> last attempt
[14:24] <sil2100> ACK
[14:26] <sil2100> asac: ok, indicators look fine, checking deps of the package - if all ok then publishing \o/
[14:26] <asac> ok i saw a notes_app success
[14:26] <asac> hell... that thing is flaki
[14:26] <asac> i will run again
[14:26] <asac> sil2100: go ahead and publish
[14:26] <asac> and wait another minute then lets go for the apps
[14:26] <asac> sil2100: i tested stuff that i apt-get install here for apps: http://pastebin.ubuntu.com/6123730/
[14:27] <asac> and dialer-app
[14:27] <asac> that was forgotten there
[14:28] <psivaa> asac: i ran notes app tests after installing the above pkgs on 55 and it passed, if that helps
[14:28] <asac> yeah
[14:28] <asac> it now passed two
[14:28] <asac> but 3 times it didnt
[14:28] <asac> psivaa: do we still record retries in automation?
[14:28] <asac> lets look next week and ensure that folks make it a priority to fix flaki tests
[14:29] <sil2100> asac: published
[14:29] <sil2100> asac: (indicators and settings)
[14:29] <psivaa> asac: i retried a weather test today, which i dint record, ill go ahead and record
[14:31] <sil2100> fginther: do you think now auto-merging for cu2d-config will work with your merge in?
[14:31] <fginther> sil2100, yes
[14:31] <asac> sil2100: ok all the apps in that apt-get install + dialer-app are ready to go
[14:31] <asac> i hope thats all we had for application #3
[14:31] <asac> psivaa: pleas alwasy do so
[14:32] <asac> super important to get that data
[14:32] <asac> to prioritize
[14:32] <psivaa> asac: ack, i will make sure that i do that
[14:33] <asac> ogra: lool: whats with qtpim?
[14:33] <asac> is that in?
[14:33] <asac> its still in TODO
[14:33] <lool> asac: barry rightfully points out that Landing spreadsheet is read-only; I've invited people to add "asks" there on ubuntu-phone@ though, would you mind making it read-write?
[14:33] <sil2100> asac: but didn't we plan application #3 tomorrow? It's 19 am there ;)
[14:33] <asac> lool: should go through leads
[14:33] <asac> lool: and a lead should be the PoC
[14:34] <lool> asac: that doesn't apply to non-Canonical folks though
[14:34] <ogra> asac, i thought lool was testing this morning
[14:34] <lool> ogra: I wanted to, but higher prio came up, but am testing now
[14:34] <asac> lool: can you be the proxy that stands in as the PoC for community requests?
[14:34] <asac> lool: or baloons?
[14:34] <ogra> ok, else i still can
[14:35] <asac> so yes, in canonical, please go through your lead
[14:35] <asac>  or manager
[14:35] <asac> if not, use lool, ogra or baloons
[14:35] <asac> sounds good?
[14:35] <ogra> sounds ok
[14:35] <asac> lool: ?
[14:35] <lool> asac: yes
[14:35] <lool> trying to think on how to put that out
[14:35] <asac> can you check with baloons as well?
[14:36] <ogra> i think the community requests that dont go through an employee already are rare anyway
[14:36] <asac> lool: just tell that a spreadsheet is not a very good way to revision and collaborate and hence we cant allow the world write access
[14:36] <asac> and then say that ogra and you offer to be their proxxies
[14:36] <asac> makes sens?
[14:36] <ogra> asac, probably someone in US TZ too
[14:36] <asac> baloons :)
[14:36] <ogra> :)
[14:36] <asac> but check with himn first
[14:36] <asac> so he understands this whole process
[14:36] <ogra> you didnt mention him in the last summary
[14:37] <asac> if not, lets talk to jono
[14:37] <asac> yeah. i am lazy trying to stay below 50k letters a day on IRC these days :)
[14:37] <ogra> lol
[14:38] <asac> sil2100: applications we planned for today
[14:38] <asac> sil2100: was a typo
[14:38] <asac> i wanted all bill filler stuff in (if you remember)
[14:38] <asac> apps are usually safe to take... we should taket hem everyday
[14:38] <lool> asac: I wrote the email already
[14:39] <lool> balloons: ^ hey, sorry to put you on the spot before you get the chance to hear of it, but we needed a default contact for community requests for Landing "asks"; hope that's ok with you!
[14:39] <asac> sil2100: fixed date
[14:39] <asac> :)
[14:39] <asac> sil2100: remember the above commands has partly packages in service
[14:39] <asac> that we want to go in as well
[14:41] <balloons> so essentially this is just covering asks for the core apps?
[14:42] <lool> balloons: typically, yes
[14:42] <lool> balloons: could also be a community person contributing a fix somewhere I guess
[14:42] <balloons> right, just let me know what you need of me, I don't think it will be a big deal
[14:43] <sil2100> asac: history-service again?
[14:44] <sil2100> asac: ok, I'll browse the list and try publishing apps now
[14:44] <asac> sil2100: http://pastebin.ubuntu.com/6123730/ thats the lot
[14:45] <asac> sil2100: the apt-get install lacks the dialer-app ... i added that after
[14:45] <asac> but that was tested as well
[14:45] <lool> didrocks: did https://code.launchpad.net/~thomas-voss/platform-api/ensure-symbols-are-included/+merge/186291 miss the window?  I dont see an updated platform-api package in the PPA
[14:45] <asac> didrocks: could be in the archive?
[14:46] <asac> err
[14:46] <asac> lool: ^^
[14:46] <asac> otherwise it missed
[14:46] <didrocks> lool: looking
[14:46] <asac> lool: it merged only 1 hour ago
[14:46] <asac> dont be impatient :)
[14:47] <didrocks> asac: yeah, it was merged after latest tick
[14:47] <didrocks> err
[14:47] <didrocks> lool: ^
[14:47] <didrocks> asac: as we run a lot of stacks manually right now, the ticks are missed
[14:47] <lool> too bad, so I have to wait 3 hours now  :-)
[14:47] <asac> lool: just sit back and relax. try to teach thostr so he knows about all the bits we want to land
[14:47] <asac> lool: i would really prefer if he comes to me with all the stuff that is needed
[14:47] <asac> in one shot
[14:47] <didrocks> (we don't run a stack if some depends are currently building)
[14:47] <asac> lool: not because its not good to do it, just because we lacked someone owning the topic
[14:47] <lool> asac: I want to lend them in the image at once, but this particular one is needed to build the next one
[14:47] <asac> :)
[14:48] <asac> lool: ok. can you make a landing entry that has all the items needed explicitely called out?
[14:48] <asac> thats the picture me and rick lack to be confident
[14:48] <lool> asac: I updated the ask for this stuff
[14:48] <asac> ok ... so its one entry with everything explicit?
[14:48] <asac> good
[14:48] <asac> then yeah. just merge and stage
[14:48] <lool> asac: I'm not 100% happy with url-dispatcher being listed under indicator-power though
[14:48] <asac> and we will look at that once we have this batch out
[14:48] <asac> latest tomorrow morning
[14:49] <lool> asac: what I'm not clear on is ask vs. landing slot; I added details on the second sheet, but not to the first one, this might be wrong though
[14:49] <ogra> same here
[14:49] <asac> lool: thats good
[14:50] <lool> asac: are you ok to land url-dispatcher + indicator-power + qtubuntu + platform-api together?
[14:50] <asac> lool: just dont punch it in the archive before its on landing plan sheet
[14:50] <ogra> i just added all three of my current changes after getting confirmation on IRC already and marked them as candidates
[14:50] <asac> lool: sure if all of that is reawdy in ppa
[14:50] <asac> lool: but maybe not today. depends on how things go right now
[14:50] <asac> we might be landing it today
[14:50] <asac> and only validate imagfe tomorrow
[14:51] <asac> lool: from technical side didrocks can say if those can be combined at all
[14:51] <asac> some might be disabled because xmir hacking
[14:52] <lool> asac: it wont be today for sure
[14:52] <didrocks> lool: asac: they are not disabled, you can have a landing with those
[14:52] <didrocks> but indicator-power + url-dispatcher are alreayd in, aren't they?
[14:53] <lool> then this sucks, this means that it was the wrong landing slot
[14:53] <asac> goodie. lets not land, but stage
[14:53] <asac> lool: goodie
[14:54] <lool> didrocks: indeed, indicator-power is in
[14:54] <lool> I suspect url-dispatcher isn't working though
[14:54] <lool> indicator-power is not in the image
[14:55] <didrocks> lool: it's in the soon-to-become image
[14:55] <didrocks> so will start existing nearly
[14:55] <lool> Hmm the one in the image doens't work anyway
[14:55] <lool> the part that got changed that is
[14:56] <didrocks> yeah, so not a real regression
[14:56] <asac> lool: well. so we had a indicator-power landing that busted desktop FF
[14:56] <asac> we wanted to bring that back todayu
[14:56] <didrocks> then, we can bind with the missing qtubuntu and platform-api
[14:56] <asac> any other fixes you need to do can still come in a second run
[14:56] <asac> we never planned to pick up a merge from today on that
[14:56] <asac> just bring back what was delivered last week
[14:56] <asac> of course if we knew it was coming, we could have waited
[14:57] <ogra> asac, but the fix for desktop required code changes
[14:57] <ogra> that was pretty clear
[14:58] <asac> sure. if we missed those they can land later
[14:59] <asac> ogra: next time put all you need to know needs to happen in the landing ask info :)
[14:59] <ogra> asac, dude ... "after this image is published" ...
[14:59] <asac> or even in the landing plan line
[14:59] <ogra> asac, could you rather say something like "after image #56 is published" or so ...
[14:59] <ogra> "this" is a pretty bad identifier as for which image :)
[15:00] <asac> i agree ... at best we had a bot that says what the next image nbumber is on /topic
[15:00] <asac> i sometimse loose sight :)
[15:00] <asac> all i know we are pumping stuff in as we speak for an image
[15:00] <ogra> yeah something like that
[15:00] <asac> so thats "THIS image
[15:00] <asac> "
[15:01] <asac> sil2100: ok ... are apps INPROPOSED now?
[15:01] <sil2100> asac: not yet
[15:01] <asac> hehe
[15:01] <asac> ogra: how is 55 going? already in testing?
[15:01] <ogra> asac, yeah
[15:02] <asac> nice
[15:02] <asac> psivaa: plars: i assume you are doing nothing but helpiong this thing :) ... recording all retries
[15:02] <kenvandine> asac, do we need to add bug fixes to your landing doc?  we need to get the webcred stack published
[15:02] <asac> yes
[15:02] <kenvandine> to fix failure to add accounts on the device
[15:02] <kenvandine> ok
[15:02] <asac> kenvandine: add it,m tell me why its safe (e.g. only desktop) and then you can go
[15:02] <asac> if it affects touch you will have to run some autopilots before pushing
[15:03] <lool> asac, didrocks, ogra: Ok, confirmed that url-dispatcher in the proposed image + new indicator-power is what we want with thostr, and that we miss a new landing slot for url-dispatcher + qtubuntu + platform-api, but we need more details on this before we request a slot
[15:03] <lool> rebooting with latest indicator-power
[15:03] <ogra> k
[15:03] <lool> I also expected I'd have to update the qtpim-opensource-src packages, but they are already in the image
[15:03] <plars> asac: I'm keeping an eye on it, and yes it's been testing
[15:03] <psivaa> asac: yea plars is doing the retries and i am trying fill as much retry recording as possible :)
[15:03] <asac> lool: sounds like i see it
[15:03] <didrocks> lool: ok, just provide details so that we can process
[15:03] <asac> lool: we know we need more, but we are kind of waiting on code of the next shot on this
[15:03] <ogra> lool, so that landing request is moot ?
[15:03] <asac> lool: so add a landing ask slot and set it to waiting for code or something
[15:03] <ogra> (for the PIM bits)
[15:04] <asac> lool: oh ... this affects the pim upload?
[15:04] <asac> cant we just upload that or does ti break stuff?
[15:04] <ogra> sounds like its already in
[15:05] <lool> so I can confirm that with latest proposed image + indicator-power from archive, I can go to settings from indicator-power
[15:05] <lool> which I couldn't do before updating indicator-power from archive
[15:05] <lool> so +1 on indicator-power testing
[15:05] <lool> asac: the landing *ask* slot is there already; will update to mention waiting for code
[15:05] <lool> asac: this is all unrelated to pim
[15:06] <plars> *sigh*
[15:06] <lool> asac: pim is already in the proposed image
[15:06] <plars> psivaa, asac: publisher plugin died again
[15:06] <psivaa> plars: so that's twice today
[15:06] <kenvandine> asac, added it, there aren't autopilot tests that cover this but i added a manual test case
[15:06] <kenvandine> i'll test it manually myself on the device
[15:07] <plars> psivaa: it's continually dying, more cu2d missing jobs probably, checking on it
[15:07] <plars> no, the job is ther
[15:07] <plars> e
[15:07] <plars> hmm
[15:08] <plars> retoaded: can you take a look at http://10.97.0.1:8080/plugin/build-publisher/
[15:08] <retoaded> plars, sure
[15:09] <plars> retoaded: publisher doesn't want to resurrect, usually when I see this, it's some job that doesn't exist anymore and it's trying to publish it, but the job it's stuck on seems to be there
[15:09] <plars> cu2d-media-saucy-3.0publish #4 is the one it's trying and failing to get past
[15:09] <retoaded> ack
[15:09] <plars> asac: ^ blocks anything being visible on the dashboard until resolved, but the tests are running
[15:11] <retoaded> plars, it's publishing now
[15:12] <plars> retoaded: sure?
[15:12] <plars> retoaded: http://10.97.0.1:8080/plugin/build-publisher/ says it's still dead
[15:12] <asac> kenvandine: wait :)
[15:12] <retoaded> plars, ok, it was working
[15:12] <asac> kenvandine: so the story about autopilots is that you run the autopilots of the other teams first and froremost
[15:12] <asac> kenvandine: so we are sure you are not breakgin them. if you dont havge tests
[15:12] <asac> thats your call
[15:13] <asac> in this way writing tests will protect you from the evil folks :)
[15:13] <asac> which is the incentive weant
[15:13] <asac> kenvandine: so tell us what you want to do and we asses what needs to be tested on your side
[15:13] <retoaded> plars, it's rolling again.
[15:13] <asac> e.g. if you need to run just one or two or all autopilots
[15:14] <plars> retoaded: did you just remove that one from the xml?
[15:14] <retoaded> plars, on the ones it got stuck on there was a broken link in the build directory; removed the link and resurrected the publishing
[15:14] <kenvandine> asac, so we have autopilot tests for gnome-control-center-signon, which of course is desktop only
[15:15] <kenvandine> asac, we need autopilot tests for system-settings, which is where this would be tested
[15:15] <plars> retoaded: that's one I haven't seen before :)
[15:15] <plars> retoaded: thanks for resurrecting it!
[15:15] <retoaded> plars, not sure where the broken links are coming from other than likely being pushed from the test machines
[15:17] <plars> fginther: any idea how http://10.97.0.1:8080/job/cu2d-media-saucy-3.0publish/ might get some broken links in the build directory? apparently the publisher plugin doesn't handle exceptions properly and just grinds to a halt when it gets confused
[15:19] <fginther> plars, hmm
[15:22] <fginther> plars, retoaded, are these broken links to other builds or artifacts or?
[15:23] <retoaded> fginther, artifacts
[15:23] <doanac> ogra: you mind taking a look at: https://code.launchpad.net/~doanac/phablet-tools/adb-errors/+merge/182515
[15:24] <retoaded> fginther, for example build /var/lib/jenkins/jobs/cu2d-media-saucy/builds/6 had a link of 2013-09-18_14-05-21 that pointed to build/2013-09-18_14-05-21
[15:24] <doanac> it should help us be able to use phablet-test-run in our automation
[15:24] <ogra> doanac, sorry, was meaning to yesterday already
[15:24] <fginther> retoaded, thx
[15:24] <doanac> no worries - wasn't sure if your mail filters may have skipped the email :)
[15:24] <ogra> doanac, approves
[15:24] <ogra> s/s/d/
[15:25] <doanac> thanks!
[15:25] <fginther> retoaded, hmm, there is no 6
[15:26] <fginther> wtf jenkins
[15:27] <retoaded> fginther http://10.97.0.1:8080/job/cu2d-media-saucy/6/
[15:28] <fginther> oops, wrong job
[15:28] <vila> fginther: https://en.wikipedia.org/wiki/The_Prisoner ?
[15:28] <retoaded> fginther, I don't think the broken link shows up thru the web interface
[15:28] <retoaded> fginther, I cleared from the cli
[15:30] <lool> asac: so given that the qtpim-opensource-src packages were already in the image, I didn't run the autopilot tests myself; what I did is that I created an event from the calendar-app, created a contact from contact app, and checked that the contact was listed in the phone-app
[15:32] <lool> 5.0~git20130828-0ubuntu2 seems super old though
[15:34] <plars> balloons: it looks like filemanager is much happier now
[15:35] <fginther> retoaded, plars, still no clue as to what happened.
[15:35] <didrocks> fginther: hey, did you remove the hack to bump ABI for the Mir team?
[15:35] <asac> lool: yeah. the autopilots show different bugs then using though.
[15:35] <asac> lool: i can run them just to feel safe
[15:35] <didrocks> fginther: it will really create issues on the engineering team
[15:35] <didrocks> those things needs to be manual and coordinated
[15:36] <balloons> plars, yes, calc and fm are happy again
[15:36] <fginther> didrocks, at the moment it's still there. If it needs to be removed, I can do that
[15:36] <asac> lool: just tell me where i can grab whatever debs
[15:36] <didrocks> fginther: yes please (they need to bump manually I guess as per thread)
[15:36] <didrocks> fginther: didn't get a reply, so I think we can go ahead
[15:36] <fginther> didrocks, ack
[15:36] <didrocks> thanks!
[15:38] <asac> sergiusens: did you get why python-autopilot didnt make it?
[15:38] <asac> or am i mistaken and its in?
[15:38] <asac> i thought there was an issue with some dep
[15:39] <lool> asac: sorry, I got it wrong, retesting now
[15:40] <sergiusens> asac, issue? I saw yesterday that it just needed manual review by the daily release team
[15:40] <didrocks> it's in the release pocket now: https://launchpad.net/ubuntu/+source/autopilot
[15:41] <asac> hmmm
[15:41] <asac> 15:13 < Mirv> asac: so moving python-autopilot below from the scheduled point since it cannot be released because of the  added python-psutil dependency
[15:41] <thomi> asac: he was mistaken
[15:41] <asac> is that solved?
[15:41] <asac> oki
[15:41] <lool> or rather, I miss debs
[15:41] <asac> so its in and done?
[15:41] <thomi> asac: he thought ap was in main, but it's not, so no problem
[15:42] <lool> Mirv: may I ask for https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtpim-opensource-src to be merged into main branch as to get .debs and a build test + build-time testsuite run?
[15:42] <asac> thomi: ok ... guess we expect it to be picked up in image 56 then. thanks
[15:42] <lool> hmm this might be late for Mirv
[15:43] <thomi> nw
[15:43] <lool> asac: is Mirv off already?
[15:43] <asac> lool: yeah. he is off. see if cypher can help
[15:43] <lool> asac: So I was confused about which qtpim version to test; the branch has not been merged yet, no merge proposal => no review, no testbuild, no .debs
[15:43] <asac> or ken or in worst case didrocks
[15:43] <asac> actually skip ken. i think he is fighting content-hub battles
[15:43]  * didrocks is the worst :p
[15:43] <lool> asac: I think I'll ping bfiller/renato (requestors)
[15:44] <asac> lool: thankw
[15:45] <asac> didrocks: exactly :P ... don't use the all-cure-joker until you really need it :)
[15:45] <asac> but... feel free to grab it :)
[15:45] <lool> the number of things that can go wrong is so high  :-)
[15:46] <lool> ogra: BTW, I didnt get any error with nautilus neither this morning nor after latest image update
[15:46] <lool> ogra: that was before updating mtp package I guess
[15:47] <ogra> lool, intresting, are you sure they didnt pop under another window ?
[15:47] <lool> ogra: how do you trigger it?
[15:47] <ogra> i see them on desktop as well as on the chromebook
[15:47] <lool> ogra: Hmm I haven't restarted nautilus though, I've plugged the phone
[15:47] <lool> ogra: do I have to start nautilus?
[15:47] <ogra> just reboot the phone with usb plugged into a PC
[15:48] <ogra> if you run a normal ubuntu desktop it should just pop up a window for you with the phone content
[15:48] <ogra> shortly after boot
[15:48] <ogra> on reboot the window stays and gvfs pops up some mtp errors
[15:48] <ogra> (reboot of the phone)
[15:49] <ogra> i know davmor could reproduce it just fine with his maguro
[15:50] <lool> didrocks: so qtpim-opensource-src isn't under CI, I guess because it's used bu KUbuntu; would there be a way to get a build of it nevertheless?
[15:50] <ogra> could be that the mako gadget driver is clever and notices if the server goes away
[15:50] <lool> didrocks: upload manually to ubuntu-daily PPA?
[15:50] <lool> sorry ubuntu-unity/daily-build
[15:50] <didrocks> lool: yeah, that's what we are doing most of the time where there are big changes
[15:51] <didrocks> to get real armhf build
[15:51] <lool> ogra: I tried again, and it worked
[15:52] <lool> ogra: that said, I had disabled automounting a while ago; perhaps I've only partially reenabled it and some things dont get automounted
[15:52] <lool> ogra: in which case, I'm afraid I'll just give on reproducing the bug if you and/or cypher alreayd know how to do this
[15:56] <lool> didrocks: hmm should I use some kind of ~addition?
[15:56] <didrocks> lool: yeah, ~ppa1 is enough
[15:56] <lool> ok, thanks
[15:56] <didrocks> yw
[15:58] <asac> psivaa: is notes app on mako retried? :)
[15:58] <lool> let's see if I have permission
[15:58]  * asac thinks that we would like a script like didrocks did for that apart
[15:59] <lool> didrocks: Rejected:
[15:59] <lool> Signer has no upload rights to this PPA.
[15:59] <lool> didrocks: helpz
[16:00] <didrocks> lool: do you have the source so that I can upload it?
[16:00] <lool> no, I just wrote it as input to dput <<EOF
[16:00] <didrocks> impressive :p
[16:00] <asac> how are apps going? inproposed now? any troubles i want to know about?
[16:01] <lool> didrocks: http://people.canonical.com/~lool/didrocks-please-sponsor-this-thx/
[16:02] <didrocks> lool: processing
[16:02] <lool> /-\-/-\
[16:02] <lool> Sorry spinner doens't work well on IRC
[16:02] <lool> |[16:02] <ogra> heh
[16:03] <lool> |[16:03] <didrocks> tssss :p
[16:03] <didrocks> lool: still uploading?
[16:03] <didrocks> or it's done?
[16:03] <lool> didrocks: it's done I think
[16:03] <didrocks> weird, can't decompressed it
[16:03]  * didrocks rechecks
[16:03] <lool> didrocks: you need the .orig to decompress
[16:04] <lool> which I'm not uploading
[16:04] <lool> cause it's in saucy
[16:04] <didrocks> well, thanks, but I figured that out :p
[16:05] <lool> hmm I could unpack locally
[16:05] <lool> the terminal which ran scp is long gone, but didn't get any error
[16:05] <didrocks> lool: uploaded after redownloading
[16:06] <lool> I double-checked the md5s while I was as it
[16:06] <lool> *at it
[16:06] <didrocks> yeah, the md5sum
[16:11] <psivaa> asac: just did it
[16:11] <sil2100> didrocks: landed the apps ;)
[16:11] <psivaa> asac: (notes on mako)
[16:12] <didrocks> sil2100: thanks!
[16:22] <psivaa> asac: notes app passed and rss reader tests are also running. that means the tests complete for 55
[17:06] <lool> what's the rune to launch all tests on a phone?
[17:06] <lool> locally
[17:10] <asac> lool: not possible
[17:10] <asac> lool:  you run individual tests
[17:10] <asac> i can explain why its not possible, but not now... it would involve using our cu2distro config as input
[17:11] <asac> as thats where we encode the test to be run against which stack at what stage
[17:11] <asac> lool: just run phablet-test-run -n -p unity8-autopilot unity8
[17:11] <asac> and then reboot fresh and unlock screen and run phable-test-run -p webbrowser-autopilot webbrowser
[17:11] <asac> lool: all that needs RW atm
[17:14] <asac> psivaa-afk-bbl: thx. have given this to ogra and popey for blessing and release
[17:14] <asac> ogra: we are waiting for mtp and a bunch of apps etc. in the release pocket
[17:15] <asac> sil2100: do you know which packages we exactly pushed for the apps i tested (e.g. application #3)
[17:21] <mmcc> Hi folks, can I clarify whether having daily releases set up for a project is a strict requirement for landing? I got some help yesterday from robru to set it up for lp:ubuntuone-credentials, but our team is concerned that changing from our existing release process so late is disruptive.
[17:25] <balloons> fginther, remember our discussion @ the spring about commits from non-core devs and jenkins not running? Does this https://code.launchpad.net/~andrewsomething/ubuntu-weather-app/lp121890/+merge/186371 merge look like you expected? I don't see that the testsuite ran for this.
[17:25] <balloons> fginther, it did autoland things as expected, just want to make sure this is what we expect to happen on these
[17:27] <fginther> balloons, that's correct. the behavior is that successful tests on autolanding are not posted to the review (as requested by certain developers)
[17:28] <balloons> fginther, perfect, thanks for confirming
[17:30] <sil2100> asac: I published webbrowser, gallery, notes, camera and history-service IIRC from that list
[17:30] <sil2100> asac: i.e. I published everything that I could publish from that list
[17:30] <sil2100> Since some did not have anything to release
[17:33] <lool> asac: ok
[17:37] <dobey> asac, lool: ^^ see mmcc's question please
[17:40] <lool> mmcc: it's not a requirement
[17:40] <lool> mmcc: it's greatly preferred for us
[17:40] <lool> mmcc: instead, just coordinate uploads to the archive with us
[17:40] <asac> sil2100: let me double check
[17:41] <asac> sil2100: ubuntu-keyboard
[17:41] <asac> sil2100: dialer-app
[17:41] <asac> sil2100: mediaplayer\
[17:41] <asac> sil2100: those three is what i was missing
[17:42] <mmcc> lool: ack, thanks.
[17:42] <asac> mmcc: we can do manual uploads. you usually need to find a core-dev that runs the autopilots for you and acks it (and does the upload)
[17:42] <sil2100> ubuntu-keyboard I published, dialer-app didn't have anything new to release
[17:42] <asac> sil2100: interesting
[17:43] <sil2100> mediaplayer-app I didn't publish since it wasn't on the list ;)
[17:43] <sil2100> I can do that if that's tested?
[17:45] <robru> mmcc, quite a bit less release effort when you're on the daily_release train... all kinds of stuff gets automated for you
[17:46] <dobey> asac: what do you mean by "upload" there? i have permissions to upload the package in question to the ubuntu archive.
[17:46] <dobey> robru: we have all kinds of existing automation, infrastructure, and process, that daily-release conflicts with
[17:46] <robru> dobey, what kind of conflicts?
[17:46] <asac> dobey: is that a per-package upload right?
[17:47] <dobey> asac: it's in the ubuntuone package set
[17:47] <asac> dobey: do you have a maguro and mako phone?
[17:48] <dobey> asac: no. i have a nexus7 now though. and we run the existing tests we have for ubuntuone-credentials when landing to trunk, during the package build, and in autopkgtests
[17:48] <asac> ok so you cant test for us
[17:48] <asac> meaning we have to find a core-dev to do manual testing of all autopilots
[17:48] <asac> that might be affected
[17:48] <asac> its ok... just not self service
[17:49] <asac> dobey: clarify through lool in the landing asks what is needed etc. and we try to get that in as soon as we can arrange the testing
[17:49] <dobey> we need to get some autopilot tests written i guess
[17:50] <asac> dobey: we protect others from getting their tests broken as that prevents them from merging
[17:50] <asac> dobey: if you dont have tests for your own stuff you just have no protection, but me (as in CI) doesnt really care
[17:50] <kenvandine> asac, i did the manual testing for the webcred stack
[17:50] <kenvandine> phone and desktop
[17:50] <asac> so we run autopilots of the others
[17:50] <dobey> robru: we don't release from trunk for one. we create stable branches at the beginning of each cycle, and develop on trunk, then backport into the stable branch for doing releases. we have existing PPAs that build packages when things land, etc…
[17:50] <kenvandine> asac, should i update the status?
[17:50] <asac> kenvandine: yeah. please update and say which ones you ran
[17:51] <robru> dobey, not sure what the big deal is... with all the daily_release'd projects I work on, we have a 'trunk-next' branch for development and then stuff only lands in trunk when it's ready for release.
[17:52] <kenvandine> asac, updated on the asks sheet
[17:52] <kenvandine> asac, what should the status on the landing plan sheet be?
[17:52] <kenvandine> should i publish the stack?
[17:52] <dobey> robru: the deal is that there's ~4 weeks left until 13.10, and making huge swathing change to established processes right now is only asking for things to go boom.
[17:52] <asac> kenvandine: we are waiting for the things we want to take for the 56 image
[17:52] <asac> after that you can
[17:53] <kenvandine> ok, cool
[17:53] <asac> sil2100: is everything in now?
[17:53] <asac> :)
[17:53]  * asac needs a tracker for that i guess
[17:53] <kenvandine> yeah, i was just wondering how i would know when that was ready :)
[17:53] <sil2100> asac: what about mediaplayer-app? Should I publish that too?
[17:55] <sil2100> asac: all other things went in it seems
[17:55] <asac> sil2100: hmm. does that have an autopilot?
[17:56]  * lool dinner
[17:56] <sil2100> asac: yes
[17:56] <sil2100> asac: let's move that to tomorrow maybe then
[17:56] <sil2100> Or wait
[17:57] <sil2100> asac: I'll do a quick test on my device
[17:57] <asac> sil2100: sure wait
[17:57] <asac> sil2100: an you add an ask at the end?
[17:57] <asac> so we dont forget
[17:57] <asac> sil2100: ok do that :)
[17:57] <asac> your call
[17:57] <asac> we just need to check that unity8 doesnt fall over if it doesnt have tests
[17:57] <asac> i guess
[17:57] <asac> then go ahead
[17:57] <kenvandine> sil2100, can you publish the webcred stack when it's all clear?
[17:58] <kenvandine> signon and libaccounts-glib in there, both tested
[17:58] <sil2100> kenvandine: are there any tests for thoses?
[17:58] <kenvandine> no autopilot, i did the manual testing
[17:58] <sil2100> kenvandine: did you test the latest changes on touch?
[17:58] <kenvandine> critical fix though
[17:58] <kenvandine> yes
[17:59] <sil2100> kenvandine: ACK :)
[17:59] <kenvandine> sil2100, great... i want to go get some food :)
[17:59]  * kenvandine goes to lunch
[18:21] <sil2100> kenvandine: I will publish later
[18:21] <sil2100> asac: mediaplayer-app published
[18:22] <sil2100> I disconnect now, webcreds will be published in 30 minutes once the stack finishes running
[18:31] <alan_g> fginther: are you the guy to talk to to get the Mir clang build to run the tests?
[18:32] <asac> lool: the url-dispatcher was pulled in through indicator-power?
[18:32] <fginther> alan_g, yes
[18:32] <alan_g> fginther: Can you make it happen please?
[18:34] <fginther> alan_g, this job? http://10.97.2.10:8080/job/mir-clang-saucy-amd64-build/
[18:34] <alan_g> fginther: double checking...
[18:37] <asac> so anyone knows about something that is still in flight before the next image?
[18:37] <alan_g> fginther: that's https://jenkins.qa.ubuntu.com/job/mir-clang-saucy-amd64-build/? (I can't connect to the IP address you quote)
[18:37] <fginther> alan_g, yes
[18:37] <asac> ogra: not sure when to start
[18:37] <alan_g> that's the one
[18:37] <asac> ogra: but either now or after mediaplayer is in, is my guess
[18:38] <asac> cant find apps in proposed so thinking its in
[18:38] <asac> ogra: do you know what "bug fix" uploads might still be missing?
[18:39] <asac> lool: qtpim lands tomorrow?
[18:39] <ogra> we could use the one from sergiusens for lxc-android-config and the seed change ...
[18:39] <asac> ogra: those are already in though, no?
[18:39] <ogra> are they ?
[18:39] <asac> everything not upload surely will not be in this build
[18:39] <ogra> who uploaded them ?
[18:39] <asac> ogra: i guess i am not sure what you are talking about then
[18:40] <ogra> damned, gnome-settings just totally trashed my fonts
[18:40] <asac> ogra: so in landing plan the only item that is INPROPOSED is applications #3
[18:40]  * ogra only sees half sentences in xchat 
[18:40] <asac> i feel thats in
[18:40] <fginther> alan_g, I think I have enough now to get it added, I'll let you know
[18:40] <alan_g> fginther: thanks
[18:41] <asac> ogra: ok... once https://launchpad.net/ubuntu/+source/mediaplayer-app is migrated
[18:41] <asac> we go
[18:42] <asac> wow
[18:42] <asac> so mako went green :)
[18:42] <asac> of course not the REAL green
[18:42] <asac> but first time that our dashboard shows green for a full run :) well done!
[18:48] <asac> plars: psivaa: i think with balloons trying to fix the core app test
[18:48] <asac> plars: psivaa: we shoudl start also retrying those etc.
[18:48] <asac> to give them a good picture at lesat
[18:48] <plars> asac: we have been
[18:48] <plars> asac: unless it's all the same failures we've seen before
[18:48] <asac> ah... so they get the same service? nice
[18:49] <asac> right
[18:49] <plars> asac: we talked about calculator, calendar, etc a while ago
[18:49] <balloons> lol, rssreader will be the death of us all
[19:01] <lool> asac: I've passed qtpim to bfiller and renato and am testing myself; did the same manual testing on it so far
[19:02] <lool> I saw some glitches in the app (never used these before), but no regression AFAICT
[19:07] <asac> ogra: can you double check that mediaplayer app is now in the archive (madison) and kick off?
[19:07] <asac> thanks
[19:07] <asac> sergiusens: ^^
[19:08] <ogra> checking
[19:10] <asac> lool: everything that you know was uploaded is in?
[19:11] <ogra> asac, not in yet
[19:11] <asac> ogra: if lool doesnt confirm dont wait for him
[19:11] <asac> L:)
[19:12] <ogra> ok, but i guess mediaplayer will still take a moment
[19:12] <lool> asac: not qtpim obviously
[19:12] <lool> asac: there are various fixes in flight, but I dont think they are ready for iamge inclusion
[19:13] <lool> like they'd need package builds and what not
[19:13] <asac> lool: inflight? i only care about INPROPOSED
[19:13] <asac> right now
[19:13] <asac> :)
[19:14] <lool> asac: right, and I dont have any of theese
[19:14] <asac> dont want to miuss anything that we thought was in
[19:14] <asac> ok cool
[19:14] <asac> ogra: so go in self kick off once tht mediathing is in
[19:14] <lool> perhaps the seed changes?
[19:14] <ogra> asac, thats what i planned
[19:14] <lool> where do I fish the autopilot test results once it's done?
[19:15] <lool> wow /tmp is crowded
[19:15] <asac> lool: reports.qa.ubuntu.com
[19:15] <asac> lool: or if you want a sneak preview you can harvest the qalab jenkins (needs VPN accesss)
[19:16] <lool> I mean the ones I ran locally
[19:16] <lool> all I got was: Ran 21 tests in 382.769s
[19:16] <asac> ah
[19:16] <lool> does that mean all passing?
[19:16] <asac> lool: they succeeded :)
[19:16] <lool> is there some file?
[19:16] <asac> lool: it prints OK
[19:16] <asac> usually
[19:16] <asac> or Success
[19:16] <asac> plars: ^^
[19:17] <ogra> you have to listen to your gut feeling :)
[19:17] <ogra> (it prints Ok ... :) )
[19:18] <ogra> and it gets noisy if it fails
[19:18] <plars> lool: which test is this?
[19:19] <lool> plars: this was unity8
[19:19] <plars> lool: that should be a pass then, there are 21 tests I believe
[19:19] <plars> (23 on the dashboard due to systemsettle)
[19:20] <lool> ok
[19:22] <asac> its interesting. i had the same feeling. if you dont feel its annoying, it usually was OK :)
[19:22] <asac> funny tool. feedback through textual emotions
[19:23] <asac> ogra: is the next edition in print yet?
[19:23] <asac> :)
[19:23] <lool> blah device failed to come up
[19:24] <ogra> seems there was a publisher run (getting fesh Packages file here)
[19:24] <ogra> lets see
[19:25] <ogra> there we go
[19:25] <lool> sensorservice is using loads of CPU on boot for some reason
[19:25] <ogra> running
[19:26] <lool> ImportError: No module named python2.7.test.test_support
[19:27] <plars> ogra: so you are building a new image now?
[19:28] <ogra> plars, yep
[19:28] <plars> psivaa: is still rerunning webbrowser :(
[19:28]  * plars won't be able to land any new automation fixes until 3am at this rate
[19:28] <psivaa> plars: just wanted to get rid of that single failure
[19:28] <plars> psivaa: you got 2 in its place
[19:29] <psivaa> plars: i know :(, trying once more
[19:29] <lool> ah got a traceback in a webbrowser test
[19:30] <lool> is this known?  http://paste.ubuntu.com/6125300/
[19:32] <psivaa> plars: i'll stop it with this time.. sorry dint know you were looking for a lul to land stuff. will dash_ignore if it's not any better
[19:33] <plars> psivaa: if there's an image building now, then we've lost our window anyway
[19:33]  * plars will try again for it tonight
[19:33] <psivaa> plars: ack
[19:34] <psivaa> plars:  the last one also finished with one failure
[19:35]  * fginther needs to leave, will be back later this evening
[19:37] <elopio> hey, can somebody trigger this rebuild for me?
[19:37] <elopio> http://s-jenkins:8080/job/ubuntu-ui-toolkit-ci/674/rebuild
[19:37] <sergiusens> lool, that is known
[19:37] <lool> thanks
[19:37] <elopio> jenkins is sooo slow here, I've been one hour waiting for the login to complete.
[19:39] <sergiusens> elopio, that's already running
[19:39] <sergiusens> http://10.97.2.10:8080/job/ubuntu-ui-toolkit-ci/675/
[19:40] <elopio> thanks sergiusens.
[19:43] <lool> sergiusens: hmm I dont seem to have permission to start a rebuild myself either, would you mind starting http://10.97.2.10:8080/job/qtubuntu-ci/77/ ?
[19:43] <lool> (I'm logged in as lool)
[19:44] <lool> asac: ok, so qtpim is good for me: http://paste.ubuntu.com/6125362/ I think bfiller wanted to test himself
[19:44] <sergiusens> lool, done
[19:45] <lool> sergiusens: ty
[19:46] <sergiusens> lool, I don't see your username on the jenkins instance
[19:48] <lool> sergiusens: http://10.97.2.10:8080/user/lool/?
[19:48] <lool> Jenkins user id: lool
[19:48] <lool> email loic.minier@canonical.com
[19:50] <sergiusens> lool, yeah, jenkins perm matrix admin is terrible
[19:50] <sergiusens> need to run for a bit but I'll add you when I get back
[19:50] <lool> sergiusens: thanks
[19:50] <lool> sergiusens: https://jenkins.qa.ubuntu.com/job/qtubuntu-saucy-armhf-ci/70/console looks like ubuntu-unity/daily-build is screwed
[19:51] <lool> W: GPG error: http://ppa.launchpad.net saucy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C012599D727CC694
[19:51] <lool> W: Failed to fetch bzip2:/var/lib/apt/lists/partial/ppa.launchpad.net_ubuntu-unity_daily-build_ubuntu_dists_saucy_main_binary-armhf_Packages  Hash Sum mismatch
[19:51] <ogra> bad timing ...
[19:51] <lool> oddly, C012599D727CC694 is Launchpad PPA for gcovr maintainers
[19:52] <lool> I dont have permission to retry anyway
[19:55] <asac> lool: show to wgrant and stevenk maybe
[19:58] <ogra> asac, cdimage is done
[20:08] <plars> new autopilot in this build
[20:09] <plars> ooo, and mediascanner also
[20:09] <plars> supposed to have a fix for bug #1222731
[20:10] <plars> psivaa: note: webbrowser change landed also that will have it skip the constantly failing test
[20:10] <plars> so the total # tests will change in this run for sure
[20:14] <asac> plars: yeah. lets hope :). the mediascanner would be amazing
[20:17] <plars> asac: well, tests are running on touch_ro now
[20:17] <plars> we should know soon :)
[20:36] <Saviq> hi friend
[20:37] <ogra> haha
[20:37] <cjohnston> hey!
[20:37] <cjohnston> welcome!
[20:39] <Saviq> asac, done
[20:40] <lool> there's something wrong, bandwidth to system-image seems anormaly slow
[20:41] <lool> I only get some tens of KiB/s
[20:41] <lool> or less
[20:41] <lool> from a dedicated server, from my home DSL, from my home cable
[20:41] <lool> e.g. with https://system-image.ubuntu.com/pool/ubuntu-66fb9ed004ea451885088c0e7e0438d0ec558d238713c5853ed51b625990b1f2.tar.xz
[20:41] <cjwatson>  0% [                                       ] 614,400      199KB/s  eta 17m 28s
[20:41] <cjwatson> from my home DSL (which rarely does any better than that)
[20:42] <cjwatson> actually more like 250KB/s now
[20:42] <lool>  0% [                                       ] 335 872     46,0KB/s  eta 74m 49s
[20:42] <lool> http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/pending/saucy-preinstalled-touch-armhf.zip is at 95,7KB/s
[20:42] <Saviq> lool, 1.8MBps
[20:43] <lool> hmm that's odd, it's from two different ISPs
[20:43] <Saviq> lool, although I'm in Lexington
[20:43] <Saviq> lool, same, 1.8MBps on this one, too
[20:44] <lool> right, 8.93MB/s from another dedicated server
[20:45] <lool> clearly some peering issues with my two ISPs
[20:45] <asac> Saviq: your changs are in unity8 only?
[20:45] <asac> are those pad.lv links bugs ids?
[20:46] <Saviq> asac, yes
[20:46] <Saviq> asac, and yes
[20:49] <asac> Saviq: so one question
[20:49] <Saviq> asac, https://bugs.launchpad.net/unity8/+bugs?field.status%3Alist=FIXCOMMITTED
[20:49] <asac> Saviq: do you maintain anything like library SONAMEs etc.
[20:49] <asac> or dbus interfaces
[20:49] <thomi> fginther: any idea WTH happened here? https://code.launchpad.net/~thomir/autopilot/forward-port-changes/+merge/186369
[20:49] <asac> Saviq: that suffer from the problem that we have to move them in lockstep?
[20:49] <asac> just wonder if you have that phenomenon in the code that your team is owning
[20:50] <thomi> CI complains about unaproved changes, but it's all approved AFAICS
[20:50] <Saviq> asac, no, nothing like that
[20:50] <Saviq> asac, actually one more - unity-mir
[20:51] <ogra> Saviq, iirc ricmm needed something in unity-mir too ... is that in ?
[20:51] <ogra> (for the media stuff)
[20:51] <Saviq> ricmm, ↑ ?
[20:51] <asac> Saviq: whats with unity-mir?
[20:51] <Saviq> asac, there's a fix in there
[20:51] <asac> you want to land that? or that has unstable api?
[20:51] <asac> ah
[20:51] <asac> add it
[20:51] <asac> ah you did
[20:51] <Saviq> asac, just did
[20:51] <asac> Saviq: is that all in trunnk etc.?
[20:51] <asac> we dont fish patches :)
[20:52] <Saviq> asac, yes
[20:52] <Saviq> asac, all that is trunk
[20:52] <cjohnston> thomi: pitti approved it three hours ago, r331 was added 1 hour ago.. noone has approved it since r331 landed, therefor not all of the revisions have been reviewed
[20:53] <asac> Saviq: so do you have unstable inter-package apis in your domain?
[20:53] <Saviq> asac, no
[20:53] <asac> sure?
[20:53] <asac> ok
[20:53] <Saviq> asac, yes, sure, no ABI changes there
[20:54] <asac> Saviq: you know what i mean? like dbus interfaces that you change?
[20:54] <asac> API
[20:54] <asac> i meant
[20:54] <Saviq> asac, and no, no API changes either
[20:54] <Saviq> asac, there's an API addition, but nothing uses it yet
[20:54] <asac> ok
[20:54] <Saviq> asac, and you requested it AFAICT
[20:55] <Saviq> asac, the SessionBroadcast thingy
[20:55] <ricmm> Saviq: asac I dont need anything in unity-mir for media stuff, not anything that im aware of yet at least
[20:55] <thomi> cjohnston: that's totally confusing - that's now how I read the LP API. Maybe the autolander should check that before going ahead and building the packages?
[20:55] <asac> ricmm: Saviq: so your unity8 landing is to prepare for multimedia?
[20:55] <asac> that would be worth mentioning
[20:55] <ricmm> what?
[20:55] <Saviq> asac, not
[20:55] <ricmm> I have no unity8 landing
[20:55] <asac> ah :)
[20:55] <ricmm> who keeps putting these things in the spreadsheet? ;)
[20:56] <cjohnston> thomi: I don't know about that. it sounds more like something for fginther...
[20:56]  * ricmm has:
[20:56] <ricmm> 1. qtubuntu branch for input in jim's media playback, no-op anywhere else
[20:56] <ricmm> 2. qtubuntu branch for qurl()
[20:56] <asac> oki... sounds like not yet ready for image landing :)
[20:56] <ricmm> 3. platform-api release needed, already bumped deps as-per didrocks instructions
[20:56] <asac> will wait for that then :)
[20:57] <ogra> ricmm, oh, sorry, i thought you said unity-mir too for the input fix
[20:57]  * ogra didnt mean to cause confusion
[20:57] <ricmm> unless my fried brain is skipping cycles, no
[20:57] <ricmm> but its completely possible
[20:57] <asac> ricmm: 3. sounds like a landing request if you want to get that into the image tomorrow
[20:57] <ricmm> well its part of the same stack as qtubuntu, didier advised to just make deps right and run the stack in one go
[21:03] <lool> asac: platform-api is listed with qtubuntu and url-dispatcher stuff
[21:03] <lool> in the asks
[21:04] <lool> anyway, bandwidth is too crappy and it's too late
[21:04] <lool> got to go to bed
[21:18] <asac> sleep well
[21:18] <asac> i am off also in a bit
[21:18]  * ogra goes too now ...
[21:24] <ricmm> Saviq: asac the fix uou mentioned is not for media, its a general fix to be able to launch apps from the command line
[21:24] <ricmm> I assume thats the one mentioned
[21:25] <ogra> oh, right, arg parsing ... that was it
[21:25] <ricmm> something like that, t was actually wrong desktop file parsing
[21:25] <ricmm> but yea, the same bug you are thinking of
[21:25] <ogra> yeah, that
[21:28] <plars> asac: no mediascanner crash this time
[21:28] <asac> wrong desktop file parsing?
[21:28] <asac> plars: really? :)
[21:28] <asac> wow
[21:29] <plars> asac: it usually happens on camera
[21:29] <asac> plars: it was a 100% crasher, right? or is there a chance we are just lucky?
[21:29] <plars> asac: no crash file left behind though
[21:29] <plars> asac: yes, every time
[21:29] <asac> nice
[21:29] <asac> lets see what happens on the other device
[21:29] <ogra> asac, it was omitting the desktop_file_hint from the exec line in the desktop ... so apps didnt properly start
[21:30] <ogra> so it only read the app name, but not the args
[21:30] <asac> effect?
[21:30] <plars> asac: camera_app.tests.test_capture.TestCapture.test_shoot_button_disable failed on maguro, but quite possibly a random testcase failure
[21:30] <ogra> apps started by tapping on an icon in unity didnt start
[21:30] <plars> mako passed 100% though
[21:30] <bschaefer> hello, I was wondering if someone could restart a job for unity7 (saucy/unity) here: https://jenkins.qa.ubuntu.com/job/autopilot-saucy-daily_release/
[21:30] <asac> plars: record and retry
[21:30] <asac> :)
[21:31] <asac> camera_app.tests.test_capture.TestCapture.test_shoot_button_disable - i remember that one
[21:31] <asac> thats a racy test
[21:31] <asac> ricmm: that was the one we had during the sprint, right?
[21:31] <plars> yeah
[21:31] <asac> plars: can we file a bug and link it in the spreadsheet where we log the retries?
[21:32] <asac> i think thats a proven awful test :)
[21:32] <asac> i want to look at what is flaky soon to ensure we can reliably gate on them
[21:32] <ricmm> asac: we saw it on monday
[21:32] <asac> right. that wasnt the unity thing, but the RW thing
[21:32] <asac> or something
[21:32] <asac> cool
[21:33] <asac> i think it actually indicated something bad there :P
[21:39] <plars> asac: https://bugs.launchpad.net/camera-app/+bug/1227373
[21:40] <asac> plars: can you put it in our spreadsheet?
[21:40] <asac> where we log retries?
[21:40] <plars> asac: already did
[21:40] <asac> kk
[21:40] <asac> thx
[22:20] <sergiusens> asac, I talked to thomi and om26er about camera_app.tests.test_capture.TestCapture.test_shoot_button_disable
[22:20] <sergiusens> asac, as it is written, that test has to go
[22:31] <asac> sergiusens: can they bring in a new one?
[22:31] <asac> a better one?
[22:32] <asac> sergiusens: i would prefer a trade :)
[22:33] <asac> please stand up for our right to not regress on test coverage :)
[22:34]  * asac off
[22:48] <sergiusens> asac, lol, that test tests a transition, autopilot is not  designed for that
[23:02] <plars> sergiusens: any idea if anything changed with sensorservice? nothing I see but https://jenkins.qa.ubuntu.com/job/saucy-touch_ro-mako-smoke-ubuntu-calculator-app-autopilot/93/artifact/clientlogs/top_before.log/*view*/ had it going a bit crazy before the test ran (after fresh boot)
[23:13] <sergiusens> plars, nothing changed, you might of just hit the mako sensor bug