[02:04] <imgbot> [03:39] <imgbot> [03:39] <imgbot> [03:58] <Mirv> morning
[07:09] <tvoss> mvo_, good morning :)
[07:10] <mvo_> hey tvoss, good morning!
[07:51] <brendand> tvoss, you said preseeding the trust database is not ready, right?
[07:52] <tvoss> brendand, it landed end of last week
[07:52] <tvoss> brendand, the env var approach is fine for now, but I wanted to make sure that we don't forget about preseeding
[07:52] <brendand> tvoss, ok
[07:52] <tvoss> trainguards, could use some help with https://ci-train.ubuntu.com/job/ubuntu-landing-015-0-reconfigure/1/console
[07:56] <sil2100> tvoss: looking!
[07:57] <jibel> 'restart' has been removed from the shutdown menu?
[07:57] <sil2100> tvoss: so, it seems that the spreadsheet is down!
[07:57] <sil2100> tvoss: I get "We're sorry, a server error occurred" when opening the CI Train
[07:58] <tvoss> hmmm
[07:58] <sil2100> Ok, only on the csv...
[08:03] <sil2100> tvoss: so, let me try reconfiguring manually
[08:03] <sil2100> Until google is back
[08:04] <Mirv> :(
[08:04] <sil2100> :|
[08:04] <sil2100> Let's hope it's only temporary
[08:05] <tvoss> sil2100, thank you
[08:08] <ogra_> wow, the tests look pretty horrid
[08:09] <sil2100> geh
[08:09] <sil2100> tvoss: ok, I think it should be reconfigured now
[08:09] <tvoss> sil2100, thank you
[08:09] <tvoss> sil2100, the dashboard still does not show the new mps
[08:10]  * ogra_ thinks this cgroups u-a-l stuff really bites us ... that should have come 3 months ago to get enough testing 
[08:10] <sil2100> tvoss: yeah, the dashboard uses the csv output from the spreadsheet :|
[08:10] <tvoss> sil2100, okay
[08:10] <sil2100> Which is currently not available...
[08:10] <tvoss> sil2100, ack, perhaps we put that information in the channel topic
[08:10] <ogra_> during dogfooding the shell stops being able to start apps for me after half a day or so
[08:10] <sil2100> tvoss: it's implicitly mentioned there
[08:11] <sil2100> tvoss: that you should expect problems with the dashboard ;p
[08:11] <sil2100> I'll send out an annoucement on the mailing list anyway
[08:11] <tvoss> sil2100, ack, and thanks
[08:13] <ogra_> sil2100, i'm not sure what we should do with the u-a-l cgroups stuff ... doesnt look like ted actually worked on fixing the UITK issues with it
[08:16] <sil2100> ogra_: so, did we get a confirmation on Friday that the UITK issues are caused by the u-a-l landing?
[08:17] <ogra_> sil2100, well, they are caused by apps not being able to start ... random apps ... and it started happening with the u-a-l landing apparently
[08:17] <ogra_> sil2100, i also find the phone quite unstable since a few days ...
[08:18] <ogra_> i wonder how urgently we need cgroups support at all ... this feels like totally untested ... two week before final ...
[08:18] <ogra_> tvoss, could we live without cgroups support ? ^^^
[08:19] <sil2100> tvoss: hah, ok, it's back up ;)
[08:19]  * sil2100 just finished the e-mail
[08:27] <tvoss> ogra_, sil2100 do we have any strong evidence that the cgroup changes are actually the root cause? apart from: ual landing coincides?
[08:27] <tvoss> ogra_, sil2100 also note that multiple people tested the changes, including davmor2
[08:29] <ogra_> tvoss, we didnt roll back and hanve an image tested with a rolled back u-a-l to prove it, no
[08:30] <tvoss> ogra_, so all issues are fixed with the rolled back ual?
[08:30] <ogra_> tvoss, but i cant start apps anymore after a few hours of using my phone ... which might indeed also be a coincidence
[08:30] <ogra_> i doubt any of the testers tried the changes for a day or two
[08:31] <brendand> sil2100, need to restart to try and get sound back
[08:31] <ogra_> shit .-.. my phone is stuck with the harps and i cant wake up the screen
[08:31] <sil2100> brendand: ok
[08:31] <tvoss> ogra_, sure, I doubt that as well. However, do you see anything in syslog or upstart logs when apps fail to launch?
[08:31] <ogra_> tvoss, these are changes that should have been tested for a month *at least*
[08:32] <ogra_> afaik the feature itself landed in upstart only 4 weeks ago, it is barndnew and untested
[08:32] <tvoss> ogra_, if it is untested why did it land in upstart?
[08:32] <tvoss> ogra_, also: just calling for a month of testing is unrealistic
[08:33] <ogra_> tvoss, i'm calling for having it in the image for a month at least to make sure every side effect can be fixed before a release
[08:33] <tvoss> ogra_, in addition: we have no evidence that the cgroup-related changes are responsible at all. With that, I would propose that we start digging into the root cause
[08:34] <ogra_> what we used to do with the normal distro in the past to make sure a feature is at least remotely safe to ship
[08:34] <tvoss> ogra_, well, then I would propose that you propose changes to our landing process
[08:34] <ogra_> landing some super intrusive feature that spans from kernel to UI two weeks before hard freeze is really not the quality assurance i'D expüect
[08:35] <ogra_> tvoss, no, i ask people to stick to the schedule ... feature freeze was over a month ago
[08:36] <ogra_> tvoss, so the cgroups changes landed with only half our kernels even having necessary features enabled ... i wouldnt call that greatly tested
[08:36] <tvoss> ogra_, sure, fixed by now
[08:36] <tvoss> ogra_, anyway, it's an important bug fix. Without the cgroup changes, random apps can escape our lifecycle
[08:36] <ogra_> yes, which costed a bunch of people a day of work that they had planned for other stuff
[08:37] <tvoss> ogra_, and that will happen again
[08:37] <ogra_> tvoss, if it is so important, why did it not land earlier but only a few weeks before the end ?
[08:37] <tvoss> ogra_, as you pointed out: the upstart support was required
[08:38] <ogra_> tvoss, it happens right now ... we'll go into traincon0 because a ton of tests fail
[08:38] <tvoss> ogra_, and again: do we have *any* strong evidence for the cgroup changes causing the issues? or are we merely correlating events in the search for an easy answer here?
[08:40] <Mirv> I wonder if anyone can reply to James regarding cgmanager debug mode at https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252 ?
[08:45] <Mirv> tvoss: at least the above bug mentions Chipaca having seen a problem in upstart where a cgroup could not be created for a task
[08:46] <Mirv> the problem were seen after these landed: http://people.canonical.com/~ogra/touch-image-stats/188.changes
[08:47] <tvoss> Mirv, do we have the requested debug information available?
[08:47] <Chipaca> yes, got a weird cgroups-related error in an untrusted helper
[08:47] <tvoss> Chipaca, once or in a reproducible way?
[08:47] <Chipaca> tvoss: once, which makes it even worse in my book
[08:47] <tvoss> Chipaca, fair
[08:47] <Mirv> tvoss: no, that's why I asked if someone could answer about enabling the debug info in autopilot tests / knows how to do that. maybe we could get it to the dashboard machinery?
[08:48] <Chipaca> because we *spotted* it once; how many notifications have been lost to this bug without us noticing?
[08:48] <tvoss> Mirv, I'm not the right person to talk to about autopilot
[08:48] <tvoss> Chipaca, sure
[08:49] <Mirv> tvoss: I think we can get CI to that, but who would know to tell them how they'd run cgmanager in debug mode?
[08:49] <tvoss> Mirv, I would think ted or someone from foundations probably
[08:50] <Mirv> or well, there's info in the bug too, so maybe just asking like that. the problem might be if also that upstream merge proposal is needed.
[08:52] <ogra_> Saviq, so we see you added and reverted stuff in unity8/qtmir on the weekend ... we are not sure now about the final state ... was it added or reverted ion the end ?
[08:52] <Mirv> psivaa: I wonder if the bug ^ 1357252 cgmanager changes could be tried on the mako running the UI Toolkit tests? there's a patch to ubuntu-touch-session and a cgmanager.conf change
[08:52] <tvoss> Mirv, hmmm, jodh might be the best person to help
[08:53] <brendand> Mirv, how did you run camera-app tests? when i run them from local branch they work
[08:53] <brendand> Mirv, but i saw you use phablet-test-run
[08:54] <Mirv> brendand: so, yes, any instructions welcome :) I created a click package on mako and installed it, + copied __init__.py + helpers.py to /home/phablet/autopilot/camera_app (/tests)
[08:55] <brendand> Mirv, i'll try that way and see what happens. it could be a difficulty with permissions or something
[08:55] <brendand> Mirv, since setprop uses sudo
[08:55] <sil2100> brendand: so, download and install all .deb packages besides the -dev package from this place: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-002/+build/6070859
[08:56] <psivaa> Mirv: i could try that. it'd speed up the process if you could let me know what exact change that i need to do :)
[08:56] <Mirv> brendand: so, I also installed dev environment on the phone and checked out your branch there. then ./click-build.sh, pkcon install-local, and updating the already phablet-click-test-setup:d tests in /home/phablet/autopilot
[08:56] <Mirv> brendand: in reality, probably the only thing needed would be manually copying the two files into /home/phablet/autopilot
[08:56] <jodh> Mirv: please can you put precise test setup details on the bug so this is captured?
[08:56] <Saviq> ogra_, it was reverted and unreverted
[08:56] <Saviq> ogra_, i.e. it's good
[08:57] <ogra_> good = in ?
[08:57] <Saviq> ogra_, yes, everything's good now
[08:57] <Saviq> ogra_, I was trying to fix http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-utopic-touch/ #3637 and up
[08:57] <Mirv> psivaa: https://launchpadlibrarian.net/182357738/ubuntu-touch-session.patch + editing /etc/init/cgmanager.conf so that one adds cgmanager_opts="--debug" there
[08:57] <Saviq> ogra_, but then it just fixed itself in #3661
[08:58] <Saviq> ogra_, I've currently no idea what was happening between the two, the runner was just getting stuck at some point and jobs timed out after 60mins
[08:58] <Saviq> ogra_, but then magically that stopped happening
[08:59] <brendand> hmm wiki.ubuntu.com is down
[09:00] <sil2100> Saviq: yeah, actually I wanted to also ask what were all those landings about ;)
[09:00] <Mirv> jodh: added the steps to run UITK tests which show the problem reliably to the bug
[09:00] <jodh> Mirv: thanks
[09:01] <Saviq> sil2100, so yeah, runner #3637 and up started locking up in a random place (like *all* of them) so I got scared that the qtmir landing, which was the only related difference
[09:02] <tvoss> Mirv, do only the uitk tests reliably expose the issue?
[09:02] <psivaa> Mirv: ack, will try that. looks like it needs a bit of handholding during the run. but i'll try
[09:03] <Mirv> tvoss: psivaa could remember better if "Application failed to start." was also seen sometimes elsewhere
[09:03] <Saviq> sil2100, so with rsalveti's help we reverted that, but then before it migrated, stuff went just went back to normal
[09:03] <Mirv> psivaa: thanks!
[09:03] <Saviq> sil2100, so we landed a reverted of the revert (and snuck in a unity8 test fix)
[09:06] <dbarth> Mirv: good morning; so finally silo 13 is ready :)
[09:07] <dbarth> it has a complx history, so should need manual help as discussed
[09:07] <dbarth> right now, i think the powerpc build is stuck on a dep wait for oxide
[09:08] <brendand> Mirv, i'm not sure what you did, but i can't reproduce it :)
[09:08] <sil2100> Saviq: ah, ok, so theoretically in the current state we're back to what we had + that one test fix, rigth?
[09:10] <Mirv> dbarth: ok, actually powerpc + ppc64el claim to miss Mir (too)
[09:11] <Mirv> sil2100: ^ landing-013 has ubuntu-system-online-accounts that is dropping support for powerpc and ppc64el because of new dependencies.
[09:15] <Mirv> brendand: hmm, darn! I'll try again without installing the self compiled camera, only the changed tests
[09:16] <Mirv> brendand: success \o/ maybe it was that self compiled camera app to blame
[09:17] <sil2100> Mirv: hmm, is that completely necessary?
[09:18] <dbarth> Mirv: on which we depend as well, with the new trusted session support
[09:19] <Mirv> brendand: approved
[09:20] <Mirv> sil2100: ^ apparently trusted session support goes through mir
[09:23] <Saviq> sil2100, not only theoretically :)
[09:23] <sil2100> I guess nothing we can do about that
[09:27] <brendand> sil2100, i'm running the uitk tests now
[09:28] <Mirv> sil2100: we seem to have at least friends-app and reminders-app as reverse dependencies to online accounts, and they used to build for powerpc too :(
[09:29] <Mirv> and then account-plugins as a third source package
[09:30] <Mirv> dbarth: so the main problem is that we would need to ask archive admins to remove all powerpc/ppc64el binary packages for friends-app, reminders-app and account-plugins with this landing, and they don't generally like it
[09:30] <dbarth> Mirv: the problem will repeat though
[09:31] <dbarth> Mirv: we have online accounts to land, then webbrowser-app, with the same dependencies
[09:31] <dbarth> Mirv: and then another set of OA and webbrowser-app
[09:31] <dbarth> so every time we have this dep-wait
[09:32] <Mirv> dbarth: could the trusted session support made optional so that you would only build depend on Mir on those platforms that it's available?
[09:32] <sil2100> brendand: thanks!
[09:33] <sil2100> Mirv: isn't reminders-app a click-only package?
[09:33] <sil2100> Mirv: friends-app we don't care about anymore
[09:33] <oSoMoN> Mirv, can I get a silo for 32? dbarth says it’s ok to put silo 6 aside (which would conflict) for now, as it’s not fully ready anyway (not sure if it’s also ok to re-assign it temporarily?)
[09:34] <Mirv> sil2100: it does not seem so: https://launchpad.net/ubuntu/+source/reminders-app
[09:34] <Mirv> sil2100: yes I know friends-app is obsolete
[09:35] <sil2100> Mirv: uh oh!
[09:36] <Mirv> dbarth: at least webbrowser-app isn't already shipping on ppc, so that's not a problem
[09:37] <Mirv> oSoMoN: done
[09:37] <bzoltan> Mirv: sil2100: I just checked that yet again the UITK is totally bloced by Jenkins. Is here anybody who could help us?
[09:38] <sil2100> bzoltan: what do you mean by 'totally blocked'?
[09:39] <bzoltan> sil2100:  no successful build by Jenkins in the last 4 days.. and not because of the UITK
[09:40] <bzoltan> sil2100:  builds are marked as UNSTABLE, no hint in the logs what could be wrong. Maybe somebody who hear the cihelp keyword...
[09:40] <oSoMoN> Mirv, thanks
[09:40] <sil2100> psivaa: could you maybe take a look at that ^ ?
[09:41] <bzoltan> sil2100: Mirv: cihelp -> http://s-jenkins.ubuntu-ci:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-autolanding/
[09:41] <bzoltan> psivaa: ^
[09:43] <Mirv> bzoltan: psivaa: clicking those links again, I can get to eg. http://s-jenkins.ubuntu-ci:8080/job/generic-mediumtests-utopic/2852/artifact/results/autopilot/results/test_ubuntuuitoolkit.xml where one sees a lot of "Application Launch Failed", already discussed today a lot :(
[09:44] <Mirv> sil2100: so the thing is that the problem stops SDK team from landing anything, and I'm wondering whether they should start merging manually and testing manually too...
[09:44] <sil2100> grrrr
[09:44] <Mirv> so for example here: http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-mako/3575/ <- all failures are due to application failing to start, not UITK problem
[09:45] <tvoss> Mirv, sil2100 do we see the issue on any other test suite?
[09:45] <tvoss> bzoltan, I see you being blocked, but I would like to understand the issue
[09:46] <Mirv> bzoltan: maybe if you learn to click those unstable links far enough (like I just managed to do) and find only failing tests fail with application failing to start, you merge manually? starting with that one (https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/ucglobals/+merge/230804)
[09:46] <bzoltan> tvoss:  it seems that the "Application Launch Failed" problems bites our autolandings too.
[09:46] <tvoss> bzoltan, sure, but apparently it only shows up in the autopilot test suite
[09:46] <Mirv> bzoltan: I think tvoss would like still to understand why UITK specifically is able to trigger that problem
[09:46] <tvoss> Mirv, yup
[09:46] <bzoltan> Mirv:  merging manually is an option, but it will not solve the problem.
[09:47] <bzoltan> tvoss: Mirv: I have no idea :(
[09:47] <tvoss> bzoltan, for the UITK test suite, I see app/file names being generated on the fly. Could you explain in a few words what the test suite is doing?
[09:47] <Mirv> bzoltan: no, and that's why today's battle about understanding the problem. psivaa is already busy trying to get cgmanager debug mode enabled so that we'd get the debug logs we would need
[09:48] <Mirv> bzoltan: I just mean that this would be an option so you are not totally blocked
[09:49] <Mirv> bzoltan: so for guiding how I got to the page to click the tests open: http://s-jenkins.ubuntu-ci:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-autolanding/365/console -> "generic-deb-autopilot-utopic-touch #3691" (UNSTABLE) -> "Console" -> "generic-deb-autopilot-runner-mako #3575" (UNSTABLE). then click all the failures open and check if they all were the application failing to start or if you have a real problem
[09:50] <sil2100> brendand: how's the test run with u-a-l reverted going
[09:50] <sil2100> ?
[09:50] <bzoltan> tvoss: elopio could tell more about why they have chosen to do this kind of dynamic test creation.
[09:50] <tvoss> elopio, ^
[09:51] <tvoss> bzoltan, do you start the actual executable with --desktop_file_hint?
[09:51] <bzoltan> tvoss: All I know that this is way of creating tests on the fly we started to use since May.
[09:51] <tvoss> bzoltan, sure, still would like to understand what it dows
[09:51] <tvoss> does
[09:52] <tvoss> bzoltan, which timezone is elopio in?
[09:52] <ogra_> costa rica
[09:52] <bzoltan> tvoss: 3:52 AM for elopio right now
[09:53]  * tvoss hopes that he is an early riser
[09:54] <psivaa> Mirv: tvoss: sorry was dealing with something else.. regarding http://s-jenkins.ubuntu-ci:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-autolanding/, i see some test failures in the downstream jobs.
[09:54] <psivaa> i'm not sure what I can do about it
[09:56] <psivaa> sil2100: re: the manta results not being there for dashboard, we have devices being offline.. manta devices appear to have a charging problem
[09:56] <bzoltan> tvoss: he checks in early and stays id there is anything. here is the launcher what is used to run those on the fly created qml apps http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/files/head:/tests/launcher/
[09:58] <tvoss> bzoltan, so the applications are not click packages, correct?
[09:59] <bzoltan> tvoss:  no, these apps are absolutely not. IMHO it was a mistake to do what is done here... that was the reason why I changed the SDK's app deployment to click, because the direct qml deployment was unstable. Crap..I missed that piece of code.
[10:00] <tvoss> bzoltan, so the flakiness in app startup was known?
[10:02] <bzoltan> tvoss:  no, it was not about flakyness ... It was about that the app launching policy was changing often and without giving time to the SDK  tools to adopt, so the app deployment feature of my tools just broke and I had to run after the changes. So we decided to forget about it and do the click way and deploy the apps in a supported way.
[10:07] <bzoltan> tvoss|afk:  psivaa: kalikiana will arrive before elopio, I will check with him the details.
[10:09] <Saviq> trainguards, icanhasreconfigure on silo 17 please, added unity-scopes-shell there
[10:09] <davmor2> Morning all
[10:10] <davmor2> sil2100: there are still issues with the recent images but they are mostly already documented :)
[10:11] <ogra_> davmor2, for me the app scope stops starting apps after half a day or so ... did you see that anywhere ?
[10:12] <ogra_> sidebar launcher still works then, but tapping an icon in the app scope just gets me a vibration ... not even a launcher splash
[10:12] <sil2100> Saviq: doing!
[10:12] <sil2100> davmor2: yeah ;) We're fighting smoketesting results right now though...
[10:13] <davmor2> ogra_: no but because of crap wifi and 3g I was still on fridays image
[10:14] <ogra_> me too (192)
[10:16] <Mirv> psivaa: yeah, the test failures we now found and they are (usually) all from this applaunch failure that is not UITK problem by itself. so I suggested they do some manual merging while the actual issue is being investigated, in case they see no other failures.
[10:18] <Mirv> (or, they might change their test creation method to workaround the problem)
[10:19] <oSoMoN> are there known issues with otto?
[10:22] <brendand> sil2100, ubuntuuitoolkit works with the reversion
[10:23] <sil2100> brendand: and with the normal packages installed it fails?
[10:23] <brendand> sil2100, that i need to check now
[10:24] <davmor2> sil2100: I've had a thought as to ogra_ 's issue.  If the dash is kill as part of the app lifecycle and is restarted but it's contents are still cached then it might have results like when you install an update to an app if you click on the app straight away it won't open.  I'll keep an eye out for it while I kill things today and see what happens
[10:25] <ogra_> Saviq, ^^ would what davmor2 suspects be possible ?
[10:26] <ogra_> i recently checked the oom_adj values for dash and unity ( ricmm asked) ... and they seemed ok ... but i assume it could still be killed at some point
[10:26] <davmor2> Saviq: I've asked ogra to see if search still works as that will refresh the scope and see if that means apps open again
[10:29] <Saviq> davmor2, ogra_, dash isn't subject to lifecycle
[10:29] <Saviq> davmor2, what's the symptoms?
[10:30] <davmor2> Saviq: ogra_ can explain it better
[10:30] <ogra_> Saviq, its the app scope more than the dash
[10:30] <ogra_> Saviq, apps dont start anymore after a while ... i can start them from the launcher, but tapping them on the scope just gets me a vibrate ...
[10:30] <ogra_> not even a startup splash
[10:30] <Saviq> ogra_, app scope just goes .openUrlExternally on application:/// appid:/// urls
[10:31] <Saviq> ogra_, so if anything, the url dispatcher gets confused
[10:31] <ogra_> ok
[10:31] <ogra_> and launcher doesnt use it ?
[10:31] <Saviq> ogra_, no, launcher launches internally (because it's part of the shell, dash isn't any more)
[10:31] <ogra_> ok, thanks
[10:31] <Saviq> ogra_, when that happens, please have a look at unity8 and -dash logs
[10:31] <ogra_> then it must be urö-dispatcher
[10:32] <ogra_> s/ö/l/
[10:32] <Saviq> as you press the apps in the dash
[10:32] <ogra_> Saviq, will do ... i didnt have it since yesterday afternoon anymore ... seems to behave now
[10:32] <ogra_> and when i had it i was iindeed outdoors ... no PC near
[10:35] <davmor2> ogra_, Saviq: I wonder, ogra said he had poor signal and little wifi? I wonder if the issue is somehow related to internet.  That should be pretty easy to replicate I'll have a play and see
[10:42] <tvoss|afk> Mirv, which other test suite is affected by applications not launching?
[10:44] <Saviq> sil2100, hmm, the reconfigure didn't stick?
[10:44] <Saviq> tvoss|afk, you're afk!
[10:44] <sil2100> Saviq: hmm, let me retry
[10:45] <tvoss> Saviq, :)
[10:45] <sil2100> hmmm
[10:47] <Saviq> hmm?
[10:47] <ogra_> hmm :)
[10:47] <ogra_> (sounds like the start of an acapellar song)
[10:48] <Mirv> tvoss: I don't remember if we've seen it in the smaller suites, psivaa has been staring the most at the test results and might remember if "Application failed to start." has been seen elsewhere
[10:49] <sil2100> Saviq: ok, I know what happened, it should be good now :) One merge request was invalid (i.e. not a merge request) - I changed that and reconfigured
[10:49] <sil2100> I mean, still reconfiguring though
[10:49] <psivaa> Mirv: i remember seeing them, now and then.. need to check if that's seen in recent ones
[10:49] <sil2100> Saviq: ok, it's ready to build
[10:49] <Saviq> sil2100, sorry..
[10:50] <Mirv> psivaa: I have that vague memory too, about seeing it elsewhere
[10:59] <brendand> sil2100, the reversion definitely works for uitk
[11:02] <sil2100> brendand: ok, good to know
[11:04] <sil2100> ogra_, tvoss, bzoltan: not sure what the final consensus was regarding UITK and u-a-l, but it seems that with the cgroup change is the cause of the UITK test failures
[11:04] <sil2100> ogra_, tvoss, bzoltan: the revert of that fixes the test situation
[11:04] <Mirv> sil2100: psivaa: tvoss: here's music-app failing on Application failed to start. http://ci.ubuntu.com/smokeng/utopic/touch/mako/188:20140814:20140811.1/9648/music_app/1530204/
[11:04] <sil2100> Just for your information
[11:04] <sil2100> Mirv: might be related to the same landing
[11:05] <Mirv> sil2100: yes, I just digged that out since tvoss was interested if we see the same problem outside of UITK, or if it's restricted to how UITK starts apps
[11:05] <sil2100> Mirv: thanks!
[11:05] <Mirv> and here's messaging app http://ci.ubuntu.com/smokeng/utopic/touch/mako/189:20140814.1:20140811.1/9674/messaging_app/1532527/
[11:05] <sil2100> Anyway, since it also seems to affect other apps, it seems like a serious issue
[11:06] <sil2100> hmmm
[11:07]  * sil2100 has problems running dialer-app/messaging-app tests
[11:08] <Mirv> yes I think there has been no doubt about the seriousness :)
[11:08] <sil2100> I think I need to change the platform
[11:08] <tvoss> sil2100, Mirv okay, thanks for digging things out, seems to me the cgroup setup procedure is racy
[11:08] <tvoss> sil2100, Mirv just a wild guess, though
[11:09] <sil2100> tvoss: I assume tedg is the best person to work on this, right?
[11:09] <tvoss> sil2100, exactly. However, some help with getting the cgmanager debug information into his hands would be greatly appreciated
[11:09] <tvoss> thostr_, ^
[11:09] <psivaa> Mirv: ack, thanks. sorry could not check that. making the uitk tests with the cgmanager patch in the lab is a little involving
[11:10] <Mirv> added a comment to the bug documenting it there too
[11:11] <Mirv> psivaa: no problem, I just needed to dig far enough and found myself
[11:11] <brendand> sil2100, dialer/messaging seem ok for me
[11:11] <brendand> sil2100, what problems are you seeing?
[11:13] <ogra_> tvoss, note that we use lxc containers too ... might be that we also do not have a "normal" cgrops setup
[11:13] <tvoss> ogra_, ack
[11:14] <ogra_> (we definitely dont use a sandard lxc setup on the phone, this is very specific, not sure if cgmanager might act differnt due to that)
[11:16] <oSoMoN> Mirv, sil2100: silo 10 is ready for publication, when you have a minute
[11:17] <Mirv> oSoMoN: I happened to stare at the spreadsheet at the second you turned it to testing pass and started looking at it :)
[11:18] <oSoMoN> Mirv, that’s the very definition of responsiveness :)
[11:18] <oSoMoN> thanks!
[12:25] <Mirv> tvoss: non-approved MP:s
[12:25] <Mirv> (claims https://code.launchpad.net/~thomas-voss/location-service/enable-report-to-free-databases/+merge/230618 ie no top-approve)
[12:31] <dbarth> Mirv: is silo 13 ok for landing now?
[12:34] <sil2100> brendand, Mirv, ogra_: so it seems that the ofono-landing from #192 causes all the dialer-app/messaging-app failures
[12:34] <ogra_> ouch
[12:35] <sil2100> brendand, Mirv, ogra_: after downgrading the packages listed here http://people.canonical.com/~lzemczak/landing-team/192.commitlog I got only 1 failure on dialer-app (which was seen in earlier images as well)
[12:35] <sil2100> Confirming messaging as well...
[12:35] <sil2100> Need to poke Bill about this once he's up
[12:39] <Mirv> dbarth: you didn't answer the question about only depending on mir on non-powerpc/ppc64el and allowing the package build without trusted session support there?
[12:39] <Mirv> dbarth: if we publish now, it will be blocked and the archive admins would probably ask for the same thing
[12:40] <Mirv> or sil2100 may comment on that, but I believe the default is to ask upstream to workaround so that package can still at least build on all archs, just with less features
[12:40] <Mirv> sil2100: good to have that confirmed! the ofono landing looked like the probable culprit in 192.changes
[12:41] <tvoss> Mirv, thanks, fixed
[12:42] <sil2100> hm, messaging-app has 5 failures still, re-running to see if that's always the same value
[12:48] <brendand> sil2100, who owns messaging? is it boiko ?
[12:48] <sil2100> brendand: yes, generally it's boiko
[12:49] <sil2100> hm, again the same number of failures on re-run - still better than with the ofono landing
[12:49] <brendand> sil2100, actually i suppose since it's ofono that's the culprit we should talk to foundations
[12:49] <sil2100> brendand: the landing was driven by bfiller, so I wanted to poke him directly
[12:50] <Mirv> dbarth: I see that the online-accounts is depending strictly on libmirclient-dev. it should be made "libmirclient-dev [!arm64 !powerpc !ppc64 !ppc64el]" similar to eg. mesa is doing it
[12:50] <boiko> sil2100: what failures? maybe I can take them a look?
[12:52] <sil2100> boiko: I was trying to determine what causes almost all dialer and messaging tests to fail on smoketesting, e.g. http://ci.ubuntu.com/smokeng/utopic/touch/mako/197:20140818:20140811.1/9753/dialer_app/ (same for messagign)
[12:52] <sil2100> boiko: this seems to be failing since #192, not sure why no one from your team noticed :)
[12:53] <sil2100> boiko: anyway, after reverting the ofono landing from #192 driven by bfiller, dialer-app tests seem to be passing
[12:53] <boiko> sil2100: interesting, let me try it locally, let's see if I can get that
[12:53] <sil2100> boiko: these failures are reproducible locally, at least on 2 of my devices
[12:55] <Mirv> sil2100: I moved the online-accounts discussion to #ubuntu-touch so that mardy can join it. I checked that various other packages depend on libmirclient-dev with architecture list specified, so it should be possible to modify code to just build with less features on powerpc
[12:55] <dbarth> Mirv: last i checked, cjwatson was recommending to not special case the packaging, so that's why we kept it architecture independant in webbrowser-app as well
[12:56] <dbarth> Mirv: so, do I need to do something else on this silo to land? i guess i'm confused about which next button i should press after all this time ;)
[12:56] <Mirv> dbarth: it was probably because oxide already was never built for other than armhf/i386/amd64, so everything works in that case
[12:57] <Mirv> dbarth: mardy seems to be on it, with luck the building without that feature on powerpc is a no-brainer
[12:57] <Mirv> dbarth: also, cjwatson recommends not to add special case architecture lists generally by making everything simply work on all platforms :)
[12:58] <Mirv> but in this case, we don't have Mir so we should build online-accounts without features requiring it, similar to mesa and others
[13:11] <dbarth> ok
[13:13] <Mirv> boiko: like it says above ^ , landing-020 publishing failed since MP:s are not top-approved
[13:13] <Mirv> boiko: https://ci-train.ubuntu.com/job/ubuntu-landing-020-2-publish/1/console
[13:20] <sil2100> MacSlow|lunch: https://code.launchpad.net/~macslow/unity-notifications/fix-1354406/+merge/231005 <- can you get someone to review this branch? :)
[13:26] <boiko> Mirv: oups, I just tested the silo (as requested by renatu), let me check the branches
[13:26] <psivaa> Mirv: finally be able to run the uitk with the patch you mentioned... http://q-jenkins.ubuntu-ci:8080/job/psivaa-utopic-touch-mako-smoke-daily-test-mako-14/31/console
[13:27] <psivaa> Mirv: tried to tweak the device and run the tests but continuously had some screen-unlock issues, but this should give us the results
[13:27] <Mirv> psivaa: whee, excellent! could you then add the resulting /var/log/upstart/cgmanager.log to bug #1357252 for jodh to see?
[13:28] <psivaa> Mirv: ack, will do
[13:28] <Mirv> let's hope there's something revealing in there
[13:29] <boiko> Mirv: ok, I'll wait for renatu to be back and ask again about the MRs
[13:29] <Mirv> boiko: ok, thanks.
[13:48] <sil2100> boiko: were you able to reproduce the issues? Do you know any reasons why the ofono-related landing could have caused at least some of them?
[13:49] <boiko> sil2100: sorry, got distracted with other things, let me try it
[13:49] <sil2100> boiko: thanks! It basically makes us blind as we have no AP test results right now
[14:00] <brendand> sil2100, did you find the ofono landing that broke the apps?
[14:04] <bzoltan> psivaa: Mirv: sorry guys, i did not follow the progress. Is there an MR on the way to fix the applauncher problem?
[14:17] <MacSlow> sil2100, always trying :)
[14:26] <Mirv> bzoltan: next step is having a debug log from psiva_a to the bug #1357252 report
[14:26] <Mirv> so no code proposals yet
[14:31] <sil2100> brendand: I just identified that the landing from 192 caused the dialer app failures
[14:33] <brendand> sil2100, telepathy-ofono from 0.2+14.10.20140807-0ubuntu1 to 0.2+14.10.20140814-0ubuntu1?
[14:33] <sil2100> brendand: yes, along with others as well, I didn't triage to exactly one component, but I know the landing that served this was the cause
[14:41] <sergiusens> plars: hey, did the 'do not send me emails' for jenkins failures ever get pushed to jenkins?
[14:46] <plars> sergiusens: hmm, I thought so, are you still getting spammed?
[14:46] <sergiusens> plars: yes
[14:46] <plars> sergiusens: I'll check into it
[14:47] <plars> sergiusens: nag me again if it still happens after today
[14:55] <sil2100> tvoss, tedg: so, I see bug LP: #1357252 has been identified to be in upstart - do we have anyone directly assigned to this?
[14:55] <tedg> sil2100, jodh is looking into it
[14:57] <tvoss> sil2100, did you actually revert the ual landing?
[14:57] <sil2100> tvoss: not yet, but depending on how long the upstart fix will take we might revert u-a-l still
[14:58] <tvoss> sil2100, ack and thx
[14:58] <sil2100> Since it affects multiple components and clouds our smoketesting
[14:58] <sil2100> But I still want to give some time to assess
[15:02] <oSoMoN> sil2100, Mirv: silo 10 is ready to be published, when you have a moment
[15:04] <sil2100> oSoMoN: aye! Doing
[15:05] <oSoMoN> sil2100, thanks!
[15:08] <t1mp> tedg: can you extend the tests for app-launcher to run UITK AP tests before landing a new launcher?
[15:08] <t1mp> perhaps some apps as well
[15:09] <tedg> t1mp, Can you propose an MR for what you want changed? /tests/manual
[15:10] <tedg> t1mp, Here's a link: http://bazaar.launchpad.net/~indicator-applet-developers/ubuntu-app-launch/trunk.14.10/view/head:/tests/manual
[15:14] <t1mp> tedg: I'll report a bug with the steps to run the tests
[15:23] <psivaa> Mirv: bzoltan: jodh: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/comments/10 is the debug logs from /var/log/upstart/cgmanager.log for a uitk test run
[15:23] <brendand> sil2100, is there anything i need to look at?
[15:23] <sil2100> brendand: did you have a look at filemanager failures as well?
[15:23] <brendand> sil2100, nope - i can do that now
[15:24] <t1mp> tedg: sorry I don't have time to do the MR now, I reported this bug https://bugs.launchpad.net/ubuntu-app-launch/+bug/1358356
[15:25]  * ogra_ sees the webbrowser changelog and hugs oSoMoN 
[15:29]  * oSoMoN gets his daily share of ogra_’s hugs :)
[15:29] <ogra_> :D
[15:29] <ogra_> well deserved ones :)
[15:30] <jodh> psivaa: thanks. I think this demonstrates the issue is with cgmanager.
[15:39] <tvoss> t1mp, ping
[15:39] <tvoss> t1mp, for https://bugs.launchpad.net/ubuntu-app-launch/+bug/1358356
[15:40] <tvoss> t1mp, I checked with bzoltan in the morning, and it seems like the uitk testsuite is using --desktop_file_hint to the start the application. Is that correct? If not, how are the dynamic application started?
[15:48] <t1mp> tvoss: good question to which I don't know the answer. on desktop I simply use autopilot3 run, and for device phablet-test-run from desktop
[15:48] <tvoss> tedg, ^
[15:48] <t1mp> kalikiana: ^ do you know?
[15:49] <tedg> tvoss, I think they're creating desktop files in ~/.local/share/applications and then running them as legacy apps.
[15:49] <t1mp> ah elopio should know
[15:49] <t1mp> elopio: ^^
[15:49] <sil2100> NOTICE! Google CSV output is broken again, expect problems with the dashboard
[15:50] <sil2100> bfiller: I was able to assign a silo for you manually though, silo 14
[15:50] <fginther> Saviq, tsdgeos, can you elaborate on the issue with testShell segfaulting in https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-utopic/977/ ?
[15:51] <tsdgeos> fginther: issue is, it segfaults and is not marked as failing
[15:51] <kalikiana> tvoss, t1mp: with this http://unity.ubuntu.com/autopilot/api/testcase.html#autopilot.testcase.AutopilotTestCase.launch_upstart_application
[15:51] <kalikiana> using .desktop files
[15:52] <brendand> sil2100, file manager failures don't seem to be reproducible
[15:52] <sil2100> ouch
[15:53] <fginther> Saviq, tsdgeos, Is checking for a crash (any crash) and failing the test an appropriate response in these cases?
[15:53] <tsdgeos> fginther: imho yes
[15:53] <tsdgeos> a crashing test is always a failure
[15:53] <sil2100> brendand: we had them failing on smoketesting for at least 2 images
[15:53] <tsdgeos> tests shouldn't crash i'd sya
[15:54] <fginther> tsdgeos, agreed, just trying to think of an appropriate method for identificaton
[15:54] <sil2100> brendand: could you maybe fill in a bug for the smoketesting failures then? We'll start counting it out and poke the developers
[15:54] <tsdgeos> fginther: the exit status of the process will be non 0
[15:54] <tsdgeos> not sure if that is something you can use
[15:54] <brendand> sil2100, ah no wait :)
[15:54] <fginther> tsdgeos, than why didn't make check fail the build?
[15:54] <brendand> sil2100, they are reproducible
[15:55] <brendand> sil2100, and the reason is very trivial
[15:55] <sil2100> Oh!
[15:55] <sil2100> brendand: what's wrong? ;)
[15:55] <tsdgeos> fginther: i don't know, it does fail here, if i do a bash while loop depending on the result of the make check it stops on segfault
[15:55] <brendand> sil2100, python3-lxml is not there
[15:56] <fginther> tsdgeos, hmmm
[15:56] <brendand> sil2100, not sure if it's meant to be in the image, or if the test is meant to install it
[15:56] <t1mp> kalikiana: thanks :)
[15:56]  * t1mp gotta go, bbl
[15:57] <brendand> sil2100, the changelog doesn't say that python3-lxml was removed, so i assume it was being installed before
[15:58] <sil2100> brendand: hmmm! Interesting, since I didn't saw any dropped packages from the images
[15:58] <sil2100> brendand: but! Maybe the unity8-autopilot deps changed
[15:59] <brendand> sil2100, filemanager's manifest specifically mentions python3-lxml
[15:59] <brendand> sil2100, so not sure why it won't install it
[16:00] <sil2100> brendand: well, it's a click package so it has no power of forcing installing of dependencies during smoketesting
[16:00] <sil2100> If it's not installed by default on the image or installed explicitly by the smoketesting infra, well...
[16:01] <sil2100> brendand: is that a new dependency?
[16:01] <brendand> sil2100, what does this part mean? http://paste.ubuntu.com/8080928/
[16:05] <boiko> sil2100: salem_ found a crash that might be the responsible for the failures
[16:05] <salem_> sil2100, ussdmanager in the telephony-service qml plugin is crashing
[16:05] <salem_> sil2100, if unity uses this plugin, it might be crashing. I am already working on it
[16:08] <oSoMoN> robru, hey, can I have a silo for line 38, please? it’s going to conflict with silo 6 but it’s okay, we’ve agreed with dbarth that silo 6 is on hold anyway as its contents are not ready
[16:09] <robru> oSoMoN, ok
[16:09] <robru> oSoMoN, you got silo 10
[16:10] <popey> balloons: you about? can you join the landing call?
[16:10] <popey> balloons: http://bazaar.launchpad.net/~ubuntu-filemanager-dev/ubuntu-filemanager-app/trunk/revision/253  where did that depends come from?
[16:12] <oSoMoN> robru, thanks, that’s my favourite silo of the day :)
[16:12] <robru> hehe
[16:13] <ogra_> jodh, are you driving that bug forward or do we (teh landing team) need to hunt hallyn for it ?
[16:13] <ogra_> (it just came up in the daily meeting)
[16:14]  * balloons waves
[16:15] <dbarth> robru: btw, i have silo 13 which takes some manual acking it says
[16:15] <dbarth> robru: can you help land that one?
[16:15] <jodh> ogra_: making slow progress. I think it's a cgmanager issue though. It would certainly make sense to be able to hand over to someone state-side to keep the momentum but hallyn is at a conference so stgraber may be a better bet.
[16:15] <balloons> popey, the pamauth?
[16:15] <balloons> popey, it's part of the source tree.. filemanager provides it
[16:15] <popey> balloons: on the landing call nobody has seen that syntax before
[16:16] <dbarth> ogra_: Mirv made comments during the day on why it was stuck with dep-waits, and then we updated the packaging, etc.
[16:16] <popey> the autopilot depends bit
[16:16] <robru> dbarth, ok, need to find a core dev
[16:17] <robru> infinity, around for a packaging ack? new binary package. https://ci-train.ubuntu.com/job/ubuntu-landing-013-2-publish/
[16:17] <ogra_> jodh, thanks
[16:17] <jodh> ogra_: I'll update the bug before I EOD.
[16:17] <ogra_> jodh, ok thanks a lot for looking into it !
[16:28] <balloons> fginther, have some time to talk today about running qml tests for community core apps during merges on jenkins?
[16:28] <salem_> sil2100, https://code.launchpad.net/~tiagosh/telephony-service/fix-ussd-crash/+merge/231225
[16:31] <boiko> robru: sil2100: ^ can I get a silo for that one to speed up testing, line 35 of the spreadsheet
[16:31] <boiko> ?
[16:32] <popey> ogra_: davmor2 got a bug number for http://popey.mooo.com/screenshots/device-2014-08-18-172928.png ?
[16:32] <balloons> brendand, plars ahh I see paul already did it: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/revision/278
[16:32] <ogra_> popey, yes, Saviq gave it to me but i cant remember
[16:32] <davmor2> popey: just looking for it, ogra_ might be quicker
[16:32] <popey> hehe
[16:32] <popey> you guys ☻
[16:32] <ogra_> popey, fix is underway already
[16:32] <robru> boiko, for utopic?
[16:32] <popey> ok
[16:32] <popey> nvm then
[16:33] <ogra_> realyl looking forward to have that and the jiggly browser fixed
[16:33] <Saviq> bug #1328839 ?
[16:33] <ogra_> the two most annoying usability bugs
[16:33] <brendand> balloons, can you try and find out if CI on the merge proposal should have caught it?
[16:33] <Saviq> yeah
[16:33] <boiko> robru: well, not sure, whatever the latest image is using that has the broken tests
[16:33] <robru> boiko, yeah
[16:33] <robru> boiko, it conflicts with bfiller in silo 4...
[16:34] <robru> boiko, so just coordinate that with him. whoever releases second will need to rebuild after the first one releases
[16:34] <ogra_> Saviq, hmm, i see the panel issue on QML/C++ apps too ... not only browser
[16:34] <boiko> robru: that's fine, salem_ still needs to do some code changes for the stuff in silo 4
[16:35] <robru> boiko, ok you got silo 15
[16:35] <boiko> robru: yep, it is just to land this fix quicker for you guys
[16:35] <boiko> robru: nice! thanks
[16:35] <ogra_> Saviq, try dekko, wait til it restarts in bg and see it coming up behind the panel
[16:35] <robru> sil2100, what's the status of rtm? can I publish that rtm silo? ;-)
[16:36] <balloons> brendand, if CI should have caught it? Technically we're in this weird state of still using phablet-test-run, and having our depends listed in a testconfig. So things are a bit in flux. I didn't know FM was being pushed to the store, but I reckon I should have proposed the MP for it to coincide with the store landing
[16:36] <davmor2> sil2100: so this image you are kicking now do you want me to look at dogfooding it or do you want me to look at tomorrows image instead
[16:36] <balloons> or whomever landed it should have done the gutcheck I suppose
[16:36] <balloons> jenkins uses debian packages, so it won't see it
[16:38] <sergiusens> we should get rid of the debian packaging for all the clicks already
[16:38] <sergiusens> this just causes pain for the 'possibility' of running on desktop
[16:38] <sil2100> robru: I think you can! Not sure if we tested publishing through a real silo already ;p
[16:39] <ogra_> sergiusens, well, desktop-next uses and will use them ... and its not clear yet if they will be clicks there in the end
[16:39] <sergiusens> ogra_: desktop-next should use the clicks
[16:39] <sergiusens> if it's unity8 based
[16:39] <ogra_> should, yeah
[16:39] <ogra_> "does" ... not so much yet
[16:44] <imgbot> [16:46] <robru> infinity, also https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-001-2-publish/ if you have time
[16:46] <davmor2> sil2100: is there any point dogfooding this image or should I just look at tomorrows instead?
[16:47] <balloons> sergiusens, since we test on 'desktop' images, the clicks would need to work there. or we need more phablet hw (real or virtual (emulator?))
[16:47] <balloons> but I'm totally in favor of ridding the deb packaging
[16:47] <sergiusens> balloons: afaik the emulator is ready for this already; xnox even had a juju charm
[16:48] <sergiusens> balloons: the desktop next images could be used instead as well
[16:48] <balloons> sergiusens, last I checked the emulator has timeout issues trying to run AP tests
[16:48] <sergiusens> balloons: on x86?
[16:48] <sergiusens> where are the bugs for that?
[16:48] <sil2100> davmor2: I think let's wait for tomorrow ;)
[16:48] <balloons> meaning they ran, but since we don't know when an app launches fully (and on the emulator it's a min), they fail
[16:48] <sil2100> davmor2: we'll be reverting something so the next image will be more exciting
[16:49] <davmor2> sil2100: \o/
[16:49] <balloons> sergiusens, there's a bug for us not being able to tell when an app is finished loading..
[16:50] <sergiusens> balloons: is that the bug where I complain as well?
[16:50]  * sergiusens wonders if there is one where he doesn't complain after mentioning that
[16:50] <balloons> specific to the emulator, I've not been able to use it since the unity issues a couple weeks ago. That bug never seems to have gone away for me. Unity crashes on start. I've not done enough to debug why that is.
[16:50] <balloons> sergiusens, complain away :-) I don't have the bug offhand, let's see
[16:51] <plars> sil2100: brendand: ok, filemanager is much improved, 25 pass, 1 fail
[16:51] <balloons> sergiusens, other than the startup timing, simple AP tests ran. The other issue I encountered was going OOM
[16:51] <plars> but at least it runs properly now
[16:54] <sergiusens> balloons: then the first thing we need to do, is enable image testing on emulator and trigger traincon 0 on it
[16:54] <nik90> sil2100: has there been any news or progress on bug 1357311?
[16:55] <balloons> sergiusens, is there a generic bug for OOM and speed issues? I'd be happy to make a meta-bug for AP tests that link to those bugs, along with the app launch issue
[16:55] <nik90> sergiusens: in addition to the bug balloons pointed out, there are 2 other bugs related to the app header being cut off and some scrolling issues in the emulator for the past 2 weeks
[16:56] <sergiusens> nik90: yeah; these are bugs due to lack of traincon 0 wrt to the emulator
[16:57] <sil2100> plars: \o/
[16:57] <sergiusens> I guess everyone knows about them, but care less to fix them
[16:57] <nik90> sergiusens: yes
[16:57] <sil2100> nik90: not sure... the only info we have is in the bug itself
[16:58] <nik90> sergiusens: imho, we should trigger traincon 0 and fix all issues listed in the landing email rather than wait for it to be high priority later on.
[16:58] <ogra_> sergiusens, not ture, rsalveti made us block on emu bugs the last traincon 0 round
[16:58] <nik90> not just the image blockers
[16:58] <sergiusens> that too
[16:58] <sergiusens> ogra_: but that was a manual block
[16:58] <sil2100> ogra_: do you have a moment to upload a revert package?
[16:58] <ogra_> sergiusens, well, and it was a very serious issue too
[16:58] <sergiusens> ogra_: if pass rate is not good as mako; it should be a blocker
[16:59] <ogra_> sil2100, and have tedg and tvoss hate me forevah !?!?
[16:59] <sergiusens> or will never reach the "run on emulator" goal
[16:59] <sil2100> ogra_: no worries! They +1'ed ;)
[16:59] <ogra_> sergiusens, prob is that we have no pass rate for emulator ... we dont run smoketests for it
[16:59] <sil2100> ogra_: there's no one around this week to work on it...
[16:59] <fginther> balloons, sure, can we do a hangout 2 hours from now?
[17:00] <sil2100> ogra_: Stephane and Serge are both attending a conference ;/
[17:00] <sergiusens> ogra_: that's why I said it should be enabled ;-)
[17:00] <ogra_> sil2100, oh, ok ... i just dont want to be the bad guy ... nobody will buy me beer anymore !
[17:00] <balloons> fginther, yes I would be free thanks!
[17:00] <fginther> balloons, anyone else need to join?
[17:00] <ogra_> sergiusens, it would need to be able to run them first of all :P
[17:00] <ogra_> enabling wont help if the test suites cant run
[17:00] <balloons> fginther, well clock is going to be the guniea pig as usual, so nik90 can come if he wishes.
[17:00] <sergiusens> ogra_: they can run
[17:01] <sergiusens> ogra_: just not well enough
[17:01] <ogra_> i thought we still werent read for that
[17:01] <sergiusens> and that should be traincon 0 right there
[17:01] <ogra_> sergiusens, well, do we have anyone who couldfind time t work on it ?
[17:01] <nik90> balloons: ?
[17:02] <ogra_> that smells like eternal traincon 0
[17:02]  * nik90 read backlog
[17:02] <sil2100> ogra_: no worries! The revert will be signed by me ;)
[17:02] <rsalveti> emulator should indeed block promotion
[17:02] <sergiusens> ogra_: rtm is going to be crap for app developers if the emulator doesn't work
[17:02] <balloons> nik90, qmltests, jenkins, clock app :-)
[17:02] <nik90> balloons: ooh yes
[17:02] <ogra_> sergiusens, well, but we can fix the emulator for utopic since rtm happens before utopic
[17:02] <nik90> balloons: we have some qml tests ready to test
[17:03] <sergiusens> ogra_: as long as no new framework is added; it should work
[17:03] <balloons> indeed, so there's something live for fginther to play with
[17:03] <ogra_> rsalveti, how exactly without having dsomeone to put time into getting tests on it at all ?
[17:03] <davmor2> sil2100: you make it sound like everyone hates you and doesn't buy you beer already? say it isn't so ;)
[17:03] <nik90> fginther, balloons: sure I will come..
[17:03] <rsalveti> ogra_: manually validating it before promoting something would already help
[17:03] <sil2100> davmor2: that's true! No one buys me beer! I guess that's because I don't drink beer, hmmm
[17:04] <fginther> nik90, you should have an invite
[17:04] <davmor2> sil2100: hahahahaha
[17:04] <ogra_> davmor2, we may both have long hair, but i llook sligthly different from sil2100
[17:04] <ogra_> (you mixed up the beer comment ;) )
[17:04] <ogra_> sil2100, but you are polish !!! now dont tell us you dont eat sausage either !
[17:05] <sil2100> I love sausage!
[17:05] <infinity> Mmm, sausage.
[17:05] <ogra_> :)
[17:05] <infinity> robru: Still need those reviews?
[17:05] <sil2100> ogra_: anyway, if you have time here you can find all package essentials: http://people.canonical.com/~lzemczak/packaging/
[17:05] <sil2100> ogra_: for the revert upload ;)
[17:05] <davmor2> sil2100: polish vodka then ;)
[17:06]  * ogra_ wgets 
[17:06] <Laney> dget!
[17:07] <robru> infinity, yeh
[17:07] <robru> yeah
[17:07] <nik90> fginther: yup got it.. thnx
[17:07] <infinity> What's with these version numbers?
[17:07] <infinity> 0.6.2+rtm+rtm ...
[17:08] <ogra_> we add one +rtm per upload :)
[17:08] <robru> uh
[17:08] <ogra_> for the fun of long version numbers
[17:09] <infinity> robru: So, unity-scopes-api needs to be pushed back with "the changelog doesn't even remotely describe the change".
[17:10] <infinity> robru: Drops a bunch of linked libraries (which is probably great!), but doesn't say why, or even that it's being done.
[17:10] <robru> infinity, hm, ok
[17:10] <infinity> robru: Also, automatic re-sorting of the symbols file is ludicrous.  There's no way (short of me sorting the old and new and comparing) to tell if symbols have been dropped, which is the whole point of the file (and reviewing it) in the first place.
[17:10] <robru> infinity, are you talking about u1db?
[17:10] <infinity> robru: Yes.
[17:11] <robru> infinity, automatic sorting? as far as I know we don't sort the symbols file. unless the upstream did that
[17:11] <infinity> robru: The diff pretty clearly shows the sort order changing.  ie: symbols moving up and down in the file.
[17:13] <infinity> If the new order is somehow preferred by upstream, I'll happily do the one-time sort-and-diff review to make sure it's sane, but if it's an accident (say, some tool that behaves differently on Jon's LA_ALL=en_UK machine than on Fred's LC_ALL=fr_FR machine), then they should fix it so they don't keep generating pointless changes.
[17:13] <robru> infinity, I dunno, looks random, I wouldn't describe it as sorted. One chunk changes from "S, T, O, R, B" to "S, O, T, R, B". I don't know what alphabet that's being sorted against.
[17:14] <robru> infinity, figures neither of the listed upstreams are here right now
[17:15] <robru> infinity, ok is that all that's wrong? I'll kick it back to upstreams
[17:15] <infinity> robru: Anyhow, any time there's a '-' line in a symbols diff without an ABI and package name bump, that's a massive red flag.
[17:16] <infinity> robru: In this case, maybe the sumbols all just moved around in the file, but that's sort of why they shouldn't do that. :P
[17:16] <elopio> t1mp: tvoss: sorry, I was out of the office. Can I help you with something?
[17:16] <infinity> robru: Let me look at unity-scopes-shell too, since it's the same landing.
[17:16] <robru> infinity, well most of it is hard to read, but that one example I already mentioned, shows the version number bumping from 0.6.0 to 0.6.2
[17:16] <robru> so it's not just a simple shuffle, version numbers are changing
[17:17] <infinity> robru: That's not an ABI bump.
[17:17] <infinity> robru: The library is still libunity-scopes3, hence no symbols can change or drop, only be added.
[17:18] <infinity> robru: And unity-scopes-shell has the same "dropped u1db with no changelog entry explaining why".
[17:18] <robru> ok
[17:18] <infinity> If this is a fault of the tools putting together the changelogs, we need to fix this.
[17:18] <infinity> If this is a fault of the upstreams literally commiting silent changes, well.  Good thing we employ these upstreams and can teach them, right?  Right?
[17:18] <bfiller> robru: can you republish silo 20, all MR's are approved now
[17:19] <robru> infinity, i'll check the merges. i'm not aware of any bugs with changelog generation, most likely somebody had an MP that did two things but only described one of them
[17:19] <infinity> robru: In both cases, I'm almost positive the dropping u1db (and related) deps is what we want, but that's no excuse for sliding it in silently with no comment on the matter. :P
[17:20] <robru> bfiller, done
[17:23] <balloons> sergiusens, do you have the time to tackle getting tests going on the emulator then or ?
[17:23] <ogra_> sil2100, uploaded ...
[17:24] <sil2100> ogra_: thanks! HAHA, you're to blame now!
[17:24]  * sil2100 runs away
[17:24] <ogra_> lol
[17:24]  * ogra_ throws beer at sil2100 
[17:26] <robru> infinity, yeah, https://code.launchpad.net/~pete-woods/unity-scopes-shell/location-setting/+merge/230694 here's where they drop u1db but the commit message doesn't mention it.
[17:28] <sergiusens> balloons: I don't plan on catching up on anything until ci supports it as a candidate for traincon 0
[17:28] <infinity> robru: landing-13 looks better, except for ubuntu-system-settings-online-accounts not documenting the addition of enable-mir.
[17:30] <balloons> sil2100, plars would you guys (CI) support the emulator as a candidate for traincon 0, per sergiusens ^^?
[17:31] <plars> sil2100: I haven't tried it super recently, but I haven't seen much improvement on that front either. Last I knew the emulator wasn't even capable of running ap tests without crashing
[17:31] <plars> balloons: ^
[17:31] <sil2100> balloons: up until now we were only considering the emulator just like a supported platform, so only making sure it 'works'
[17:32] <balloons> so we're between a rock and hard place then sergiusens. I'm willing to help out, but there's definitely hurdles to cross
[17:32] <sil2100> balloons: currently we're busy enough getting one platform into a promotable state, I don't want to think of how much time we would need to get the emulator in the equation as well
[17:32] <balloons> thanks plars sil2100
[17:32] <sil2100> balloons: since mako is our main focus and it's able to hold up promotion for more than 7 days in average ;/
[17:33] <balloons> sil2100, yes, I know I'm waiting for the new image for clock app atm :-)
[17:33] <robru> infinity, thanks
[17:33] <robru> brb, breakfast
[17:40] <sil2100> o/
[17:58] <davmor2> ogra_, popey: could you try something for me please.  Pick up you phone walk out of range of your wifi and see if the indicator updates,  I was about 800+Metres from home and I couldn't connect to the internet couldn't figure out why till I realised the phone said I was still connected to the wifi
[17:59] <davmor2> I'm wondering if the issue with the clock isn't so localised to the clock
[17:59] <ogra_> davmor2, mine does that every time i wake itup from suspend :P
[18:00] <ogra_> indicator shows wlan fine but browser or webapps get me a network error ... inspecting the device everything seems fine ... no erros
[18:00] <ogra_> but i can only get online again after tapping one of my APs (even if its the same one) and trigger a re-connect
[18:01] <davmor2> ogra_: yeah so for me I had to knock the wifi off to trigger 3g and then everything was fine
[18:02] <davmor2> ogra_: I'm concerned that it didn't update though, I'm beginning to suspect that the clock rendering and wifi not updating could be related.  did you file a bug for the wifi?
[18:03] <ogra_> it did update for me yesterday when i took my phone to the store with me
[18:03] <ogra_> but i dont know when it did that ... i had it in my pocket
[18:03] <ogra_> probably its just slow
[18:04] <davmor2> ogra_: yeah but it wasn't that is what is concerning me
[18:04] <popey> davmor2: i can't yet, but will do a bit later
[18:05] <davmor2> popey: thanks
[18:05] <popey> just rebooted my phone and all i see (for over 30 mins) is the small rotating ubuntu logo
[18:05] <davmor2> popey: ouch that doesn't sound good
[18:05] <popey> apport loop
[18:05] <popey> telephony-service
[18:06]  * popey reboots
[18:06] <davmor2> man I thought things were meant to get more stable now not less
[18:07] <popey> booted that time
[18:08] <popey> gah, really wish network manager wouldn't connect to the farthest access point
[18:09] <ahayzen> +1
[18:09] <davmor2> popey: but it wants to damn you
[18:09] <ahayzen> popey, is that a bug for that ...i am sitting ~1m away from one ap point and it always connects to the other one ~10m away
[18:09] <popey> of course what it really means is I should sort my house wifi our
[18:09] <popey> yyes
[18:10] <popey> bug 1330471
[18:10] <ahayzen> popey, thanks i'll confirm it :)
[18:11] <popey> thank you
[18:11] <robru> rsalveti, not sure what happened in the spreadsheet but I fixed it up so your maliit landing correctly points at silo 8.
[18:11] <robru> rsalveti, don't run the WATCH_ONLY build until after the source package already finishes building
[18:12] <rsalveti> robru: hm, I didn't run watch-only for mallit
[18:12] <rsalveti> maliit
[18:12] <robru> rsalveti, I know you didn't, I'm saying don't do it ;-)
[18:12] <rsalveti> robru: oh, then fine, thanks :-)
[18:13] <robru> rsalveti, there's some kind of bug where citrain can get itself in an inconsistent state if you run the WATCH_ONLY build before the source package finishes building. makes it a pain to publish after that.
[18:14] <rsalveti> oh, good to know :-)
[18:14] <robru> rsalveti, yeah, it used to work fine but it bit me a couple times last week
[18:19] <imgbot> [18:19] <imgbot> [18:20] <robru> woop woop
[18:20] <ogra_> rsalveti, new browser ^^
[18:20] <ogra_> no more jiggly ... (they say)
[18:20] <davmor2> robru: ah your the other part time zoidberg along with popey
[18:21] <robru> davmor2, http://youtu.be/-Rnw0D2AdYU
[18:22] <davmor2> robru: is it just a zoidberg appreciation society? :D
[18:23] <robru> davmor2, actually I was going more for some kind of air raid siren, but zoidberg is cool so if that's what you got out of 'woop woop' them I'm all for it ;-)
[18:23] <robru> (if I was trying for zoidberg I would have typed a few more 'woop's ;-)
[18:26] <davmor2> robru: hahahaha
[18:26] <davmor2> robru: popey even has the ascii version of zoidberg :)
[18:27] <robru> nice
[18:27] <robru> oh yeah I think i saw that once
[18:38] <nik90> ogra_: yup the browser experience is so much better
[18:38] <nik90> ogra_: although launchpad.net looks terrible on the phone and doesn't use the entire phone width for some reason
[18:38] <ogra_>  yeah, some work for the design team :)
[18:45] <jhodapp> robru, can I get a silo for line 37?
[18:45] <jhodapp> nik90, that's the fix for clock app to play sounds
[18:45] <jhodapp> nik90, I'd need you to test that fix out when it builds in whatever silo I get assigned
[18:45] <nik90> jhodapp: cool..I will keep an eye on it
[18:45] <robru> jhodapp, ok you got 16
[18:46] <jhodapp> robru, thanks ^
[18:46] <robru> jhodapp, you're welcome
[18:46] <nik90> jhodapp: will do
[18:47] <nik90> jhodapp: couldn't I test the fix from the https://code.launchpad.net/~jhodapp/media-hub/allow-shared-sounds/+merge/231242 ? It has armhf packages that I can manually install on the phone to test
[18:47] <jhodapp> nik90, it's better to test from the silo packages
[18:48] <nik90> jhodapp: ack
[18:48] <jhodapp> robru, does this mean media-hub is in another silo? https://ci-train.ubuntu.com/job/ubuntu-landing-016-1-build/2/console
[18:49] <robru> jhodapp, no, it means that somebody manually uploaded a new version to distro, bypassing citrain. you have to sync the changes back
[18:49] <jhodapp> ok
[18:50] <robru> jhodapp, http://launchpadlibrarian.net/182350513/media-hub_1.0.0%2B14.10.20140813-0ubuntu1_1.0.0%2B14.10.20140813-0ubuntu2.diff.gz here's the diff from distro, please apply that directly to trunk then rebuild
[18:50] <jhodapp> robru, ok
[18:53] <boiko> robru: btw, silo 15 fixes dialer-app's and messaging-app's autopilot failures seen in recent smoke tests
[18:54] <boiko> robru: so if there is an image building scheduled soon, it might be worth including that one
[18:54] <robru> boiko, ah you just missed it. next one isn't for about 8 hours.
[18:55] <boiko> robru: that's fine, at least it is fixed already :)
[18:55] <robru> boiko, hehe, great, thanks
[19:01] <fginther> balloons, meeting time
[19:03] <balloons> fginther, coming
[20:02] <jhodapp> robru, can you advise on this, I'm not quite sure with looking at the debian/changelog what it's talking about: https://ci-train.ubuntu.com/job/ubuntu-landing-016-1-build/3/console
[20:03] <robru> jhodapp, hm, when you took that diff I mentioned, did you push it to trunk or did you add it to your MP?
[20:03] <jhodapp> robru, added to my MP
[20:05] <robru> jhodapp, ok, right. so what's happened is, when you make changes to debian/changelog in your MP, citrain won't touch the changelog and considers your version as gospel. so all the automatic changelog-generation logic gets turned off. so now you have to either back that change out of your MP and just push it direct to trunk, or write your own changelog by hand (which is easy enough but annoying if there's lots of MPs in the silo)
[20:06] <jhodapp> robru, hmm, so am I able to push directly to trunk?
[20:06] <robru> jhodapp, depends on how the project is set up. if you're in the team that owns it you can.
[20:07] <robru> jhodapp, I can push to pretty much any trunk that ctrain knows about so I'd be surprised if you can't push to your own trunk
[20:07] <jhodapp> robru, should be, I registered the project
[20:07] <jhodapp> robru, this is such a trivial change, I'll go ahead and just do that...and then I assume it'd just get picked up on the next image build right?
[20:07] <robru> jhodapp, yeah, just push it to trunk then. if anybody gives you any guff about a trunk commit with no review, blame it all on jdstrand (since it's his direct distro upload that required this resync)
[20:08] <robru> jhodapp, no, if you just push the whole MP to trunk, no packages will be built, and it won't be in the image build
[20:08] <robru> jhodapp, image builds don't build from trunk, they pull packages from distro. and the way to get packages in distro is through citrain
[20:08] <jhodapp> robru, ok, just to make sure I'll have nik90 just try out the packages build by the Jenkins bot
[20:08]  * jdstrand notes he asked for permission on said direct upload
[20:08] <jdstrand> ;)
[20:09] <jhodapp> jdstrand, yeah, I think I oked that...I guess I didn't fully understand what that entailed
[20:09] <boiko> robru: would you mind reconfiguring silo 004? I have added new components in there
[20:09] <robru> jdstrand, yeah, no worries, direct uploads are normal and ok things, it just causes some re-sync dancing in citrain is all
[20:09] <robru> boiko, sure
[20:09] <jhodapp> robru, so then how would my change get into the next image?
[20:09] <jdstrand> yep, which is why I asked about it first :)
[20:09] <boiko> robru: thanks
[20:10] <jhodapp> jdstrand, next time I'll say no :)
[20:10] <robru> jhodapp, you have to build it in a silo and publish the silo. I was trying to say "just push the packaging change to trunk, then build your silo normally." sorry for the confusion
[20:10] <nik90> jhodapp: so what do you want me to test?
[20:10] <jhodapp> robru, ah ok...so it'll still go through the silo process then before being apart of the image...that's cool
[20:10] <robru> jhodapp, yeah
[20:11] <jhodapp> nik90, I guess nothing yet, I'll still want you to try silo 16 in a few mins
[20:11] <nik90> jhodapp: oke
[20:11] <robru> boiko, hm, having some trouble with the reconfig job, hang on...
[20:12] <jhodapp> robru, cool yeah, it said nothing to do for merging, but is still building it in the silo
[20:12] <robru> jhodapp, after you pushed to trunk you mean?
[20:12] <jhodapp> robru, yep
[20:13] <robru> jhodapp, yeah, that's fine, then it's just doing a trunk release.
[20:13] <jhodapp> nik90, you can follow the progress here: https://ci-train.ubuntu.com/job/ubuntu-landing-016-1-build/4/console
[20:13] <nik90> cool
[20:13] <jhodapp> nik90, once you give me the ok that you're enabled, we can publish the silo
[20:18] <nik90> jhodapp: yup will do so
[20:18] <jhodapp> thanks
[20:23] <robru> boiko, sorry there seems to be some kind of temporary connectivity issue with the spreadsheet, but it doesn't seem very temporary. still digging
[20:23] <boiko> robru: oups, ok
[20:33] <robru> boiko, ok seems to be working now. please build
[20:33] <boiko> robru: nice! thanks
[20:34] <robru> boiko, you're welcome!
[20:48] <t1mp> elopio: hi
[20:48] <t1mp> elopio: we were discussing this bug https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252
[20:48] <t1mp> elopio: there were some questions how we execute the apps for testing on phone, I didn't know the answer and thought you would know
[20:48] <t1mp> elopio: I don't know what's the status of that bug now
[20:49] <t1mp> elopio: also there is this bug https://bugs.launchpad.net/ubuntu-app-launch/+bug/1358356 perhaps you can comment there to let us know what you think of it?
[20:50] <elopio> we have two options to launch apps. If they are installed, we just use ubuntu-app-launch
[20:51] <elopio> if we are using it from the build or branch dirs, we use the desktop-file-hint.
[20:52] <elopio> t1mp: to fix the second bug, the best way is to turn the toolkit tests into autopkgtests
[20:54] <Saviq> hum hum
[20:54] <t1mp> elopio: can you comment on the bug? if you explain it to me and then I explain it to ted is not the most effective way to sort it out :)
[20:54] <brendand_> fginther, what environment does this jenkins job run in? http://91.189.93.70:8080/job/generic-mediumtests-utopic/1523/console
[20:54] <Saviq> robru, I think it was overlooked that https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-001-3-merge-clean/1/console were MPs targetting respective trunks, but landed in rtm
[20:54] <brendand_> fginther, or any like it
[20:55] <t1mp> elopio: perhaps ted is right and we don't need to test anything additional in the app-launcher, but I don't have a clear view of what is/should be tested where
[20:55] <robru> Saviq, sweet
[20:55] <Saviq> robru, sweet how?
[20:55] <Saviq> robru, rtm is ahead of utopic now
[20:55] <robru> Saviq, because it's totally aweosme that I have to fix that now
[20:55] <Saviq> on those two projects
[20:55] <Saviq> robru, right, that
[20:56] <fginther> brendand_, it runs under X11 on a cloud instance. The x server is started for each test run
[20:56] <Saviq> robru, FWIW, check out the comment I left in that line in the spreadsheet
[20:56] <elopio> t1mp: I think that when ubuntu-app-launcher lands, all the toolkit tests should run as a reverse dependency. autopkgtests will take care of that.
[20:56] <elopio> t1mp: but the actual important part is to make sure that each fix lands with a test on the same project.
[20:56] <robru> Saviq, yeah, I saw that, for some reason i was thinking somebody else took care of that already
[20:56] <elopio> t1mp: I can comment on the bugs.
[20:56] <brendand_> fginther, is it utopic desktop?
[20:56] <rsalveti> robru: I published silo 2, now waiting to see if the src package publishing will work
[20:56] <fginther> brendand_, it's utopic, but it's not running unity
[20:57] <fginther> brendand_, it's installed from a cloud image
[20:57] <fginther> not desktop
[20:57] <robru> rsalveti, oh, ok
[20:57] <rsalveti> robru: seems you tried to publish right after I published it
[20:57] <brendand_> fginther, so the seed is different from the phone image, of course
[20:57] <robru> rsalveti, yep
[20:57] <rsalveti> not sure if it'll stay in a broken state now
[20:57] <robru> rsalveti, it should be good I think.
[20:57] <fginther> brendand_, yes, of course :-)
[20:57] <rsalveti> great
[20:57] <brendand_> fginther, can you confirm that python3-lxml is seeded in that image?
[20:57] <Saviq> robru, sounds like thostr didn't get all the memos about what rtm is ;)
[20:58] <Saviq> although I did try to unconfuse him today, obviously failed to do so
[20:58] <robru> Saviq, ok I'm gonna send an email
[20:58] <Saviq> robru, yeah, sounds like stuff needs to be cleared up
[20:58] <t1mp> elopio: I commented on https://bugs.launchpad.net/ubuntu-app-launch/+bug/1358356
[20:59] <tedg> robru, How's the silo count? Could I get one to leave the cgroup'd UAL in for testing? (it'll probably stay for a week)
[20:59] <robru> tedg, yeah we can probably do that.
[21:00] <robru> tedg, do you have a spreadsheet line?
[21:00] <tedg> robru, No, was asking first, I'll need to setup an unrevert MR too.
[21:00] <robru> tedg, sure, there's 4 free, I don't anticipate anything big, just ping me when the spreadsheet row is ready
[21:00] <tedg> robru, Cool, thanks!
[21:00] <fginther> brendand_, Installed: 3.3.5-1
[21:00] <robru> tedg, you're welcome
[21:01] <Saviq> robru, there's one more thing: Releasing 0.6.2+rtm+rtm+rtm+14.09.20140818-0ubuntu1
[21:01] <Saviq> robru, see anything unexpected? ;)
[21:02] <Saviq> robru, there's only two in Releasing 0.5.3+rtm+rtm+14.09.20140818-0ubuntu1 ;)
[21:02] <Saviq> it's like it's accumulating them as it goes, and I'm not really joking
[21:02] <t1mp> Saviq: what's the release target for that? utopic? ;)
[21:02] <Saviq> sounds like some variable isn't reset
[21:03] <robru> Saviq, yeah, that's a feature. A new "+rtm" gets prepended every time the build is retried. We were having a problem where it used to say "0ubuntu3" or whatever, but we found that numbers were too hard to read. It's so convenient now, you can just see how many times "+rtm" appears in the string and you know right away how many times the build was retried ;-)
[21:03] <brendand_> fginther, that's something of an issue sometimes, because it means branches that don't get tested on mako can run into dependency problems
[21:03] <Saviq> robru, oh! never thought of that
[21:03] <brendand_> fginther, we got this recently with filemanager
[21:03] <Saviq> numbers?
[21:03] <Saviq> who uses numbers
[21:03] <robru> Saviq, but yeah, I'm aware. I'll look at it shortly, just got some other stuff to clean up first
[21:03] <Saviq> what are we? engineers in 1990?
[21:03] <tedg> Hmm, I think that sil2100 messed up this version number ;-) "0.4+14.10.20140808.2.is.0.4+14.10.20140808.2"
[21:04] <nik90> jhodapp: two questions. 1. After installing media-hub from the silo, do I need to restart the media-hub service? If yes how to do it?
[21:04] <tedg> Yes, yes it is :-)
[21:04] <t1mp> Saviq: it is a 1-ary number
[21:04] <nik90> jhodapp: 2. Once I finish testing, how do I proceed to remove the silo?
[21:04] <jhodapp> nik90, yes, "restart media-hub"
[21:04] <Saviq> t1mp, yup, base +rtm
[21:05] <jhodapp> nik90, try ppa-purge, or just do a fresh flash of 198 with --wipe
[21:05] <nik90> jhodapp: ok
[21:09] <brendand_> fginther, is there a plan long or medium term to address that?
[21:09] <brendand_> fginther, either by getting those running on devices, or perhaps on the emulator
[21:10] <tedg> robru, line 38
[21:11] <Saviq> robru, oh no it isn't!
[21:11] <fginther> brendand_, I agree that can be a problem, but right now, we don't have a way to run the core-apps MPs on makos... Yes, we want to run these on the emulator, but I don't have a timeline for that
[21:11] <Saviq> robru, https://code.launchpad.net/~unity-team/unity8/rtm-14.09
[21:11] <robru> Saviq, oh well, nobody told me of that one
[21:11] <Saviq> robru, it happened like last week! ;)
[21:12] <fginther> brendand_, we still don't have emulator as a smoke testing platform
[21:12] <robru> Saviq, hm, actually when I asked sil if I could publish this latest one, he said he wasn't sure if the rtm publish job was ever tested. so how did an rtm landing get out without sil or i knowing?? :-P
[21:12] <Saviq> robru, lol, good question
[21:12] <Saviq> robru, someone needs to buy sil some lecithin
[21:13] <Saviq> robru, although he did push a whole lot of it through manually
[21:13] <Saviq> robru, fixing things as it went
[21:13] <robru> Saviq, ah that could be why
[21:13] <Saviq> robru, so maybe that's what he meant
[21:13] <robru> Saviq, https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-001-2-publish/build?delay=0sec indeed there's only one successful publish job, and it's mien
[21:14] <nik90> jhodapp: confirmed silo-16 fixes my issue with audio playback :)
[21:14] <Saviq> robru, https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-000-2-publish/build?delay=0sec
[21:14] <jhodapp> nik90, excellent!
[21:14] <Saviq> robru, mine was there
[21:14] <jhodapp> nik90, I'll publish then
[21:15] <nik90> jhodapp: yup go go go :)..lets make into the next image build
[21:15] <Saviq> robru, "Started by user Łukasz Zemczak"
[21:15] <jhodapp> robru, can you please publish silo 16 for me?
[21:15] <Saviq> robru, so like, really, he can't say no :)
[21:17] <robru> Saviq, ah, the mysterious silo 0!
[21:17] <Saviq> robru, the one and only
[21:17] <robru> jhodapp, can you mark it tested:yes, please?
[21:18] <jhodapp> robru, done
[21:18] <robru> jhodapp, thanks!
[21:18] <robru> jhodapp, and approve the merge ;-) https://ci-train.ubuntu.com/job/ubuntu-landing-016-2-publish/2/console
[21:19] <jhodapp> robru, right
[21:19] <jhodapp> robru, got weird since it said merged
[21:19] <robru> jhodapp, oh right, nm
[21:20] <jhodapp> robru, how's that work now?
[21:20] <tedg> robru, Thanks!
[21:20] <robru> jhodapp, just stupid code. it doesn't consider 'Merged' as being equivalent of 'Approved', so it thinks "oh, this merge is not approved!" so I just told it to allow unapproved merges and it was fine
[21:20] <robru> tedg, you're welcome
[21:21] <jhodapp> robru, ok great, thanks man
[21:21] <robru> jhodapp, you're welcome
[21:28] <robru> haha
[21:29] <rsalveti> lol
[21:36] <robru> kenvandine, mterry: need some packaging advice, anybody around?
[21:37] <mterry> robru, I'm around briefly
[21:37] <robru> mterry, can you think of a punctuation character that would be valid in a debian version number, and sorts lexically higher than +.
[21:37] <robru> ?
[21:38] <mterry> robru, I think the point of + is that it's treated as highest
[21:38] <robru> mterry, eg, like is "rtm*14.09" a higher version than "rtm+14.09" and still legal? crap
[21:38] <mterry> robru, just like ~ is bottom
[21:40] <mterry> robru, this might help? http://manpages.ubuntu.com/manpages/trusty/man5/deb-version.5.html
[21:41] <mterry> robru, that indicates that + is not special
[21:41] <mterry> robru, try .
[21:41] <robru> mterry, thanks
[21:43] <mterry> robru, if that doesn't work, reading the Sorting Algorithm part of that man page is likely going to help.  gotta go
[21:44] <robru> mterry, thanks a ton!
[21:53] <rsalveti> robru: you can publish this one ^ :-)
[21:53] <robru> rsalveti, gladly! ;-)
[22:42] <popey> I'm getting http://paste.ubuntu.com/8083631/ when trying to re-trigger https://code.launchpad.net/~nik90/ubuntu-clock-app/play-sound-preview/+merge/230959
[22:44] <nik90> popey: I have no idea what means
[22:44] <popey> jenkins is ill i think
[22:45] <popey> ooh, worked this time
[22:46] <popey> http://91.189.93.70:8080/job/ubuntu-clock-dev-ubuntu-clock-app-utopic-3.0-ci/ building
[22:50] <nik90> woohoo