[01:04]  * asac reads backlog
[01:04] <asac> at least two books of content got written here in 2 weeks :)
[02:04] <imgbot> [03:34] <imgbot> [03:34] <imgbot> [04:39] <Mirv> asac: around that amount, and in the end of book 2 one battle was won :)
[05:15] <bzoltan> cihelp: I have a bunch of MRs pending on autolanding to the staging branch https://code.launchpad.net/ubuntu-ui-toolkit/+activereviews  Is anybody around who could tell e what to do to make Jenkins work?
[05:29] <bzoltan> cihelp: this is the failure everywhere: make: *** No rule to make target 'coverage-xml'.  Stop.
[05:46] <tvoss> good morning
[07:42] <t1mp> bzoltan: I don't see changes in UITK that have something to do with that coverage-xml, so I guess something else changed in the image
[07:42] <bzoltan> t1mp: No idea
[07:54] <sil2100> Phew, finally
[07:57] <tvoss> sil2100, ? :)
[07:59] <ogra_> hmm, still a lot of trust-store crashes in smoke testing ...
[08:00] <ogra_> and a new unity8 one as well
[08:00] <brendand> sil2100, no movement on camera app at the end of last week?
[08:01] <tvoss> ogra_, I haven't patched the trust-store for the test crash, yet
[08:02] <ogra_> tvoss, ah, ok, no worries then
[08:02] <ogra_> (as long as someone looks into it all it fine :) )
[08:02] <ogra_> *is
[08:03] <sil2100> brendand: hmm, what do you mean by 'no movement'?
[08:04] <brendand> sil2100, i mean it still fails - so i think my fix didn't make it to the store
[08:04] <sil2100> That's hm, impossible
[08:04] <sil2100> We had binary built and published specifically for this
[08:04] <sil2100> Let's poke popey when he's here ;)
[08:05] <brendand> sil2100, unless they fail for another reason ...
[08:05] <brendand> sil2100, i'm flashing mako to investigate
[08:05] <sil2100> brendand: thanks!
[08:05] <brendand> sil2100, i can certainly see that my fix got in
[08:05] <brendand> but why is it not working
[08:05] <sil2100> brendand: it's for sure in trunk, but I'm not sure if it got released to the store... maybe some earlier revision ;/
[08:06] <sil2100> Or that
[08:06] <brendand> sil2100, well the store revision is 347, which matches my fix
[08:07] <Mirv> it's in the #180 indeed
[08:09] <brendand> i just tried on 'the other device' #183 and it seems camera app is still taking a long time to load
[08:09] <brendand> and doesn't show the location dialog
[08:10] <Mirv> on mako #183 I got the popup
[08:11] <ogra_> i have that here too
[08:11] <ogra_> (the popup)
[08:11] <ogra_> on 181 ...
[08:12] <brendand> is anyone noticing that sometimes the intro still crashes after the first screen, and then you're left on a black screen?
[09:00] <brendand> Saviq, there are some really strange compositing issues in recent images
[09:00] <Saviq> brendand, hit me
[09:00] <brendand> Saviq, i can only reproduce them with autopilot tests so far, not yet manually
[09:00] <popey> sil2100: brendand what were you going to poke me for?
[09:01] <brendand> popey, for sh**s and giggles?
[09:01] <brendand> popey, or were you expecting a poke?
[09:01] <popey> 09:04:48 < sil2100> Let's poke popey when he's here ;)
[09:02] <brendand> popey, might have been about camera app, but i think we already established that isn't a problem with the app version
[09:02] <popey> ok
[09:02] <brendand> popey, yeah that was it - the version is right but the tests still fail in CI. not locally, just in CI
[09:03] <brendand> Saviq, when running weather_app - https://plus.google.com/u/1/110434705244077414661/posts/agE2vKMmSjJ?pid=6046229873227353938&oid=110434705244077414661
[09:05] <tvoss> sil2100, could you try to land silo 12 again? mps are approved now
[09:05] <Saviq> brendand, you owe me for a chiropractor
[09:06] <brendand> Saviq, ?
[09:07] <Saviq> brendand, photo orientation
[09:07] <Saviq> brendand, had to twist my head to be able to comprehend it
[09:07] <brendand> Saviq, fixed :) https://plus.google.com/u/1/110434705244077414661/posts/agE2vKMmSjJ?pid=6046229873227353938&oid=110434705244077414661
[09:07] <Saviq> brendand, too late, owe me anyway! :P
[09:08] <brendand> Saviq, i saw the same thing in gallery on friday
[09:08] <Saviq> brendand, it *looks* to me like the app became transparent...
[09:08] <brendand> Saviq, yes it does
[09:08] <Saviq> brendand, oh hmm, that's indeed quite weird
[09:09] <Saviq> brendand, please file a bug, and if you come up with steps to reproduce, please let us know
[09:09] <Saviq> brendand, from just an image like that it's quite impossible to find out what's going on
[09:09] <Saviq> brendand, but next time you see it, please try and right-drag to spread
[09:09] <Saviq> brendand, so that we can see whether it's indeed transparent or does it actually draw the dash inside the app..
[09:11] <brendand> Saviq, well you can run an autopilot suite like gallery or weather and it should happen at least once
[09:11] <brendand> Saviq, i'll try and catch it next time
[09:14] <brendand> Saviq, the spread shows part of the window as black
[09:14] <brendand> Saviq, and that seems to be where it's drawing the shell
[09:14] <brendand> Saviq, actually i saw this before in autopilot tests - but it was always just black, rather than being able to see the shell through it
[09:15] <Saviq> brendand, ok so not new, just now the dash is an app, and it's behind the app
[09:15] <Saviq> so it's just visible through the transparent parts of the app
[09:16] <Saviq> which is somewhat of a bug since only one app should ever be visible when focused
[09:16] <Saviq> but issue itself is not new, and suggests it's happening in apps themselves, not composition
[09:43] <alf_> cihelp: Any ideas about the failure in https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-utopic-armhf/191/console . It's blocking all of or CI/autolanding jobs.
[09:52] <Mirv> tvoss: what's up with the silo 012 location-service? I see the 2nd branch got approved <1h ago, just wondering whether you'd like to publish it then
[09:52] <Mirv> as I see Robert tried to publish it on Friday but it didn't work since approvals were not yet there
[09:52] <tvoss> Mirv, yup, pinged sil2100 in the morning
[09:53] <tvoss> Mirv, yup, feel free to publish
[09:53] <Mirv> tvoss: yeah, he's away for a bit atm, so I'll do that. thanks!
[09:56] <tvoss> Mirv, can I push clean, yet?
[09:57] <Mirv> tvoss: only after it has migrated to release pocket. but if it helps your workflow, we can take a risk (of it not migrating properly, needing manual trunk fixing or such) and I can clean it for you
[09:58] <Mirv> these days it's useful to ask whether saving 1h is worth it :)
[09:58] <tvoss> Mirv, ah no, let's just wait. Need to rebuild silo 14 once 12 is merged
[09:58] <Mirv> tvoss: ok
[10:01] <davmor2> morning all
[10:02] <davmor2> sil2100: I had an issue over the weekend all of a sudden mako said I had no sim
[10:02] <davmor2> sil2100: quite a big problem :)
[10:03] <davmor2> I'm going to fresh flash it and see if it is just a software issue and if it is try and figure out what went wrong
[10:03] <cjwatson> sil2100: So - is there anything we can try re-landing on the RTM branch?
[10:04] <Mirv> davmor2: I've a SIM that says no SIM on Mako, I should probably finally flash Android back and test if it's similar there (=hw problem or such) or if there are some cases where there Ubuntu-specific problems
[10:05] <Mirv> my normal mako usage is that I tether wifi from Jolla :) but I'd have mostly non-used SIM with unlimited data transfer available, it just doesn't work
[10:06] <Mirv> it does work on Nexus 7 where it's normally used
[10:12] <bzoltan> sil2100:  do you know somebody who could help me with Jenkins. The UITK autolanding stopped working. Kind of showstopper... because we can not land anything for days
[10:14] <Mirv> psivaa: ^ can you help bzoltan? (there's no specified vanguard at the moment)
[10:14] <psivaa> Mirv: sure
[10:14] <psivaa> bzoltan: a jenkiins job link would be helpful
[10:15] <bzoltan> psivaa:  I have a problem that all UITK autolending jenkins job fails like this
[10:15] <bzoltan> psivaa: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-utopic-armhf/4436/console
[10:15] <davmor2> I now have a recognised sim again
[10:15] <bzoltan> psivaa: make: *** No rule to make target 'coverage-xml'.  Stop.
[10:15] <sil2100> cjwatson: give me some time till the afternoon
[10:15] <davmor2> I just have no scopes
[10:15] <sil2100> davmor2: uh
[10:16] <t1mp> psivaa: I have more jenkins jobs with the same failure, if you are interested
[10:16]  * sil2100 goes back to his books
[10:16] <sil2100> I'm a bookie today
[10:16] <psivaa> t1mp: bzoltan: i think we saw this issue last week too, and i dont think it's the make file issue
[10:16] <cjwatson> sil2100: sure, just want to make sure we run something through before I go on holiday
[10:16] <davmor2> sil2100: apparently the popup for no storage is maybe blocking the guide from appearing so you just get a black screen
[10:17] <psivaa> it's 'Build timed out (after 180 minutes). Marking the build as failed. '
[10:17] <bzoltan> psivaa: I have no idea what causes that. All coverage related stuff in the UITK is like 1y old
[10:17] <psivaa> and we think it's caused by the new gcovr that landed on Friday, i think
[10:18] <psivaa> bzoltan: t1mp. this new gcovr is causing all the pbuilder jobs to go super slow, making the jobs to timeout
[10:18] <t1mp> psivaa: so the solution is to fix gcovr or revert the change?
[10:19] <cjwatson> It's not just a foolish version check or something, is it?
[10:19] <bzoltan> psivaa: sounds like a perfect reason to sack that  gcovr
[10:20] <psivaa> bzoltan: t1mp: probably.. i need to find a way to exclude/revert that
[10:21] <Mirv> tvoss: cleaned 012 and kicked a rebuild of location-service in 014 (https://ci-train.ubuntu.com/job/landing-014-1-build/138/console)
[10:21] <bzoltan> psivaa: Thank you.
[10:21] <tvoss> Mirv, awesome, thank you
[10:21] <t1mp> psivaa: cool, thanks. Keep us informed please so that we know when it makes sense to retry to autoland our MRs
[10:21] <psivaa> t1mp: sure. will do
[10:22] <psivaa> alf_: btw, http://s-jenkins.ubuntu-ci:8080/job/mir-mediumtests-builder-utopic-armhf/196/console is now progressing. one cyclops node was in a bad state
[10:22] <tvoss> brendand, for pre-seeding of the test database: A command line executable would be fine for you?
[10:23] <cjwatson> psivaa: I suggest asking mterry to investigate, since he synced the new gcovr
[10:23] <brendand> tvoss, at a pinch, yes
[10:24] <tvoss> brendand, ack, on it
[10:24] <psivaa> cjwatson: ack, thank you. mterry does not seem to be online. I'll ping him once he comes online
[10:25] <tvoss|lunch> but first: lunch :)
[10:25] <brendand> tvoss, it needs to be packaged somewhere though
[10:25] <brendand> or maybe we can just include it with the autopilot code - not really ideal though
[10:25] <brendand> it would probably be generally useful so it would be great if it were packaged
[10:51] <Mirv> pete-woods: you can't use CI Train to land MP:s for apps that don't release .deb:s to archives. also for some apps like camera, gallery, you need to ask a .click to be uploaded in addition to the deb release, since they are click-only on the phones.
[10:53] <Mirv> pete-woods: so for click-only apps like https://code.launchpad.net/~dropping-letters-devs/dropping-letters/trunk you'll need to just get the change accepted into trunk, after which a .click will be autobuilt at jenkins and can be uploaded to the store (by me, for example)
[10:53] <sil2100> pete-woods: right, as per what Mirv mentioned - you need to talk with the owners of those projects to get some info if they are click only or not
[10:53] <sil2100> pete-woods: since click-only ones have their own auto-merger instead
[10:56] <Mirv> (...and yes it's confusing)
[10:59] <sil2100> (+1 on that)
[11:01] <pete-woods> bleurgh
[11:01] <pete-woods> okay, will start doing that once I can work up the will
[11:01] <pete-woods> thanks guys
[11:03] <cjwatson> Mirv: One of those days maybe I will see if we can figure out how to build/release click packages in LP ...
[11:05] <pete-woods> cjwatson: yes. it would be super handy if there was some agreed upon behaviour (defined by whatever LP expected) that click packaging build scripts had to follow
[11:05] <cjwatson> Originally I didn't define that because having to fit into an existing source package format was one of the things third-party app developers complained about with .debs
[11:06] <cjwatson> But there should probably at least be something you can fit into if you want to use build infrastructure
[11:06] <pete-woods> sounds logical to me
[11:08] <alf_> psivaa: thanks
[12:07] <Mirv> bregma: typo on line 33 https://code.launchpad.net/~bregma/unity/lp-1345296/+merge/22760
[12:07] <Mirv> assuming 3 at the end and retrying
[12:08] <bregma> Mirv, yeah, cut-n-paste error
[12:08] <Mirv> not a huge leap of assumption needed
[12:24] <popey> Mirv: /72
[12:24] <popey> bah!
[12:25]  * ogra_ wonders what popey tries to do when dividing Mirv by 72
[12:25]  * sil2100 wonders about the end result of this operation
[12:26] <popey> MOAR MIRV!
[12:26] <ogra_> well, just many small Mirvs
[12:26] <popey>  /join #pedants
[12:26] <ogra_> lol
[12:28] <popey> erk http://s-jenkins.ubuntu-ci:8080/label/calxeda-pbuilder/load-statistics looks busy
[12:31] <Mirv> hmm..
[12:32] <Mirv> 72 small Mirvs would make this apartment a rather crowded place
[12:33] <Mirv> or busy at least, even if in theory all of me:s would consume the same volume altogether
[12:33] <ogra_> your cats would like it i bet :)
[12:36]  * Mirv contributed cats to https://www.flickr.com/groups/canonical-offices/ (oldish pic already, though)
[12:56] <bzoltan> psivaa: sorry to bug you, but is there any news about the gcovr problem?
[12:57] <psivaa> not yet, waiting for mterry to come online
[12:57] <psivaa> bzoltan: ^ sorry
[12:58] <popey> fginther: http://s-jenkins.ubuntu-ci:8080/label/calxeda-pbuilder/load-statistics?type=min looks to be getting worse, is this normal?
[13:04] <fginther> popey, that's not that unusual. I do see an occassional spike like this a few times a day. We are seeing higher usage in general, but it hasn't approached a problem state yet were lots of builds are waiting for more than an hour
[13:05] <popey> fginther: is there a view which shows what's in the queue?
[13:06] <fginther> popey, I use this: http://s-jenkins.ubuntu-ci:8080/computer/  It shows the full build queue, I haven't found a way to just show the queue for a specific label
[13:06] <jgdx> cihelp: can anyone take a look at this build failure? http://pastebin.ubuntu.com/8017000/
[13:10] <psivaa> jgdx: *looks like a test failure: 'FAIL!  : BluetoothTest::testGotAdapter() Caught unhandled exception' but if you could give me the link to the job, would be able to take a look more
[13:15] <Saviq> davmor2, hey, forgot to ask, is your video carousel back to normal?
[13:15] <davmor2> Saviq: one second and I'll let you know
[13:16] <Saviq> davmor2, thanks
[13:17] <davmor2> Saviq: yeap much better :)
[13:17] <Saviq> davmor2, was a UITK issue, will mark invalid
[13:18] <davmor2> \o/
[13:18] <kenvandine> has anyone figured out what's up with the CI hangs and gcov?
[13:18] <kenvandine> retoad, did you get any further on that?
[13:19] <davmor2> Saviq: ouch
[13:19] <Saviq> davmor2, too early?
[13:19] <davmor2> Saviq: had to reboot and got Unity 8 is loading
[13:20] <Saviq> davmor2, the dash you mean?
[13:20] <davmor2> Saviq: Yeap
[13:20] <Saviq> davmor2, that's expected if you unlock very soon after the greeter showed up
[13:20] <Saviq> davmor2, the dash is a separate process now
[13:20] <Saviq> basically an app
[13:20] <davmor2> But not pretty
[13:21] <Saviq> davmor2, your shell starts that much faster though 'D
[13:21] <davmor2> haha
[13:22] <retoad> kenvandine, I didn't get any further with it. cjwatson suggested to psivaa earlier today to check with mterry on the gcovr issue
[13:23] <jgdx> psivaa, argh, sorry, wrong link. pastebin http://pastebin.ubuntu.com/8017107/ and job https://jenkins.qa.ubuntu.com/job/ubuntu-system-settings-ci/1183
[13:23] <cjwatson> (that's because mterry was the person who synced gcovr recently)
[13:23] <mterry> retoad, kenvandine, psivaa: hello!  Yeah, I synced gcovr and it's causing problems?
[13:23] <mterry> cjwatson, throwing me under the bus for getting ubuntu in sync!  ;)
[13:23] <retoad> mterry, it seems to just hang and causes jobs to time out.
[13:23] <cjwatson> mterry: I think you misspelled "making it your responsibility to debug" ;-)
[13:24] <mterry> cjwatson, :)
[13:24] <mterry> retoad, hrm -- which package build can demonstrate the issue?
[13:25] <retoad> mterry, kenvandine should be able to point you at jenkins jobs that are failing.
[13:25] <jgdx> psivaa, seems to happen to a lot of the uss ci jobs, e.g. the ci for this unrelated mp https://jenkins.qa.ubuntu.com/job/ubuntu-system-settings-ci/1175
[13:28] <kenvandine> http://jenkins.qa.ubuntu.com/job/ubuntu-system-settings-ci/1185/
[13:28] <kenvandine> mterry, ^^
[13:28] <kenvandine> mterry, afaict, every jenkins job is failing :)
[13:28] <kenvandine> well, everything building with gcov, which seems to be everything i care about
[13:29] <kenvandine> mterry, it hangs until the job times out after 2 hours
[13:29] <kenvandine> so we can't get CI to pass anything
[13:31] <mterry> kenvandine, yeah but I want to just replicate this at home.  Is there a package build or test I can run?
[13:32] <mterry> oh I see you pointed me at u-s-s already
[13:33] <kenvandine> mterry, afaik it only happens in jenkins
[13:33] <mterry> kenvandine, guh
[13:33] <kenvandine> i'm not sure if i've done a pbuilder build since it started hanging
[13:33] <mterry> I'll try
[13:38] <psivaa> jgdx: i think the reason for the actual failure in those jobs are due to the jobs timing out, which we suspect due to the new gcovr that mterry and kenvandine are discussing ^. the 255 return code in your paste can also be seen in passing jobs: https://jenkins.qa.ubuntu.com/job/ubuntu-system-settings-utopic-amd64-ci/362/consoleFull
[13:38] <kenvandine> jgdx, yeah, all CI jobs are timing out after 2 hours
[13:38] <kenvandine> at least all uss jobs
[13:38] <kenvandine> and i think the indicators
[13:38] <kenvandine> probably more
[13:44] <seb128> kenvandine, speaking of settings, do you want to do a landing? We have a stack of approved changes, I was pondering looking at doing one, don't want to dup work though
[13:45] <seb128> kenvandine, oh, hey btw, happy monday ;-)
[13:45] <davmor2> popey: can you confirm something very quickly,  set a pin number on devel-proposed,  once set tap the power button a couple of times so you are at the welcome screen, now knock the phone into plane mode give it a second and turn it back on, then swipe the welcome screen and log in does the cellular reactivate?
[13:45] <kenvandine> happy monday seb128!
[13:46] <kenvandine> seb128, feel free to do a landing if you can
[13:46] <seb128> kenvandine, ok, might want to get the gcovr issue fixed first
[13:47] <kenvandine> i think that only affects CI, which I'd suspect the approved branches were from before gcovr broke CI?
[13:47]  * kenvandine hasn't really looked at what's approved
[13:48] <seb128> kenvandine, no, we got a few approved today
[13:48] <seb128> kenvandine, I'm also hopping to get some of my few liners bugfixes in
[13:48] <kenvandine> seb128, ah... my battery_gps branch, i removed the top approval just now, we need the location-service fix first
[13:48] <seb128> kenvandine, ok
[13:48] <kenvandine> although showing the switch isn't bad...
[13:49] <kenvandine> it just doesn't throws the indicator state off a bit :)
[13:49] <kenvandine> charles, how's that fix coming?
[13:49] <popey> davmor2: no. it doesn't re-activate here
[13:50] <kenvandine> seb128, CI's been failing since friday... basically we had one day of passing tests after dealing with the otto problem before this happened
[13:50] <kenvandine> what a week!
[13:50] <davmor2> popey: thanks I'll bug it in a second, if it say offline you can restart to get it back up
[13:51] <jgdx> psivaa, awesome thanks
[13:51] <jgdx> kenvandine, I thought this was due to my schema shenanigans. Phew!
[13:51] <kenvandine> jgdx, :-D
[13:54] <kenvandine> mterry, i can't reproduce it in sbuild :/
[13:54] <kenvandine> so looks like only on jenkins
[13:54] <mterry> kenvandine, well..  it's not a build thing
[13:54] <kenvandine> oh... right
[13:54] <mterry> kenvandine, I think CI manually runs make coverage-xml
[13:56] <kenvandine> mterry, i bet you are thrilled you synced gcovr :)
[13:56] <mterry> kenvandine, and manually adds -DCMAKE_BUILD_TYPE=coverage to debian/rules
[13:57] <mterry> kenvandine, man...  debian even just took our previous version and bumped the version...  I did nothing an autosync would have done
[13:58] <Saviq> retoad, hi, I see gcovr is still blocking the vms, is there anywhere I could track progress on this issue? shall I file a bug with ubuntu-ci-services-itself?
[13:58] <Saviq> (and where's your -ed?)
[13:59] <mterry> Saviq, kenvandineand I are working on it, above ^
[14:04] <thostr_> sil2100: can you give me a helping hand with silo 3?
[14:04] <sil2100> thostr_: sure, what's up?
[14:04] <thostr_> sil2100: wondering about the non matching versions...
[14:05] <sil2100> thostr_: let me take a look
[14:07] <mterry> kenvandine, OK...  looks like I can reproduce with "make -C obj-x86_64-linux-gnu/ coverage-xml" after adding the debian/rules bit
[14:07] <kenvandine> good
[14:07] <mterry> kenvandine, this is in a pbuilder, but maybe it would work outside too, with the above logic
[14:09] <sil2100> thostr_: ok, seems like a trivial thing
[14:09] <retoad> Saviq, what mterry said :-) and my disappeared somewhere over the weekend; need to fix that.
[14:11] <sil2100> thostr_: so, it seems slangasek released a direct upload that needs to be synced up in trunk
[14:12] <sil2100> thostr_: I could probably do that and commit to trunk directly, so you can then just rebuild quickly
[14:12] <mterry> kenvandine, the -r argument to gcovr, which we use looks to have changed meaning in 3.1?  https://github.com/gcovr/gcovr/blob/master/CHANGELOG.txt  Not entirely sure if related, but might be
[14:12] <mterry> kenvandine, (we were previously using 2.4)
[14:15] <mterry> kenvandine, especially since we seem to be stuck in a "datafiles = get_datafiles(options.root, options)" call, traversing a tree of files
[14:16] <kenvandine> mterry, that does sound suspect
[14:19] <sil2100> thostr_: you can rebuild your silo, should be ok now
[14:19] <thostr_> sil2100: ok, thanks
[14:20] <pmcgowan> kenvandine, are we still hanging jenks jobs?
[14:21] <kenvandine> pmcgowan, yeah, that's what mterry and i are talking about
[14:21] <kenvandine> an issue with the updated gcovr
[14:24] <Mirv> managed to flash-all android and flash back ubuntu, now my mako works with SIM card too.
[14:24] <Mirv> I wonder what should I do if I don't receive MMSs
[14:25] <Mirv> also, Ubuntu store is empty and stays empty even if I search something there
[14:26] <ogra_> is your 1 account set up ?
[14:26] <ogra_> *U1 account
[14:26] <mterry> kenvandine, got a fix.  Some missing brackets
[14:26] <Mirv> yes it is. progress bar moves at the bottom
[14:26] <mterry> kenvandine, was treating the root path as an array, so searched "/" for files
[14:26] <kenvandine> mterry, woot!
[14:26] <kenvandine> i had just reproduced it in a local build :)
[14:27] <Mirv> of course if the store is several megabytes or such, the slow connection (limited to 256kbit/s -> cheap) might explain
[14:27] <kenvandine> oh...  / :)
[14:27] <kenvandine> nice
[14:27] <Mirv> progress bar stopped moving around, still empty
[14:30] <mterry> kenvandine, any bug for that?
[14:30] <kenvandine> i don't think so
[14:32] <Mirv> ok, store works after reboot. but it didn't work on the first boot after --bootstrap flash even with all the network connectivity, and such a problem is not listed eg. even on ToyKeeper's "old bug round-up"
[14:33] <mterry> kenvandine, uploaded
[14:34] <kenvandine> woot, thx!
[14:34] <Mirv> I'll add a note to myself to test it again at some point to see if it's reproducable. the only special thing was that I was on 3G only, wifi disabled.
[14:34] <mterry> kenvandine, we actually just got unlucky.  Upstream fixed this in 3.2.  But Debian only has 3.1.  Bad time to sync
[14:34] <kenvandine> indeed :)
[14:34] <davmor2> popey: https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1355218
[14:35] <popey> davmor2: oh, i misunderstood your description
[14:35] <Mirv> davmor2: is it normal that PIN code isn't asked automatically, but I need to select unlock SIM from indicator instead?
[14:36] <popey> davmor2: still can't reproduce it though
[14:37] <davmor2> Mirv: pass, I don't design these things :)
[14:38] <Mirv> :)
[14:39] <Mirv> found, bug #1333121
[14:42] <Mirv> and, nice that we have piiramar onboard, since I found bug #1350209 being under progress too
[14:59] <oSoMoN> sil2100, hey, can I have a silo for line 36 ?
[15:01] <Mirv> oSoMoN: sure
[15:02] <Mirv> if a core-dev reads this, a packaging ack would be welcome for https://ci-train.ubuntu.com/job/landing-006-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity8-desktop-session_1.0.12+14.10.20140811-0ubuntu1.diff
[15:02] <seb128> Mirv, looks fine to me
[15:03] <seb128> bregma, shouldn't we drop the x11 session btw?
[15:03] <Mirv> thank you seb
[15:03] <seb128> yw
[15:04] <jhodapp> sil2100, can I get a silo for line #37?
[15:06] <Mirv> jhodapp: done ^
[15:06] <jhodapp> thanks Mirv
[15:06] <Mirv> sil has some bookkeeping to do today or such
[15:12] <bregma> seb128, yes, dropping the X11 session is on the agenda, #1296733, but priority is getting the Mir version working again
[15:13] <oSoMoN> Mirv, thanks
[15:13] <seb128> bregma, when did it stop working?
[15:13] <bregma> seb128, last week when the dash-as-app branch landed
[15:13] <seb128> bregma, and what update make it stop working?
[15:13] <seb128> bah
[15:13] <seb128> why isn't the unity8 team testing that their landing don't screw the desktop session?
[15:14] <seb128> Saviq, ^
[15:14] <Saviq> seb128, yeah, our fault :|
[15:14] <Saviq> seb128, I could come up with excuses, but it's not really worth it
[15:14] <bregma> seb128, we simply need to automate testing of the desktop-next ISO
[15:14] <seb128> right
[15:14] <seb128> bregma, well, that wouldn't help much if they don't look at the results and land anyway
[15:14] <bregma> that will be our next big goal
[15:42] <kenvandine> wow jenkins is busy...
[15:46] <charles> kenvandine, apparently there were some changes in silo-014 since Friday because tvoss asked me if I could re-test
[15:46] <charles> kenvandine, when silo-014 lands that should fix https://bugs.launchpad.net/location-service/+bug/1348334 wrt indicator-location's action states being exported on the bus
[15:46] <charles> (and with location-service having a state to export ;)
[15:47] <tvoss> charles, is 14 good to go?
[15:48] <kenvandine> charles, there's still an issue though right?  where the states get out of sync when changing in the indicator and in settings?
[15:48] <charles> tvoss, yes, I tested it on a fresh v183 flash and it looks the same as friday
[15:48] <charles> kenvandine, yes, the ui sync bug is still there
[15:48] <kenvandine> ok... i wonder if that should block me landing showing the switch in settings
[15:48] <charles> kenvandine, I haven't had time to chase that down yet, I spent friday trying to get indicator-datetime's haptic feedback fixed & landed
[15:49] <kenvandine> charles, it only gets out of sync in the indicator right?
[15:49] <tvoss> sil2100, ping
[15:49] <charles> kenvandine, I can't remember if I mentioned this in #phablet, but it looks like indicator-network has a similar issue. This /may/ be a ubuntu-ui-tookit issue
[15:49] <kenvandine> yeah, i think you did
[15:49] <charles> kenvandine, if you toggle GPS from u-s-s, both controls stay in sync
[15:49] <charles> kenvandine, if you toggle the GPS from the indicator, they fall out of sync
[15:50] <kenvandine> but i seem to recall the state stays in sync in settings, just the indicator gets out of whack
[15:50] <kenvandine> ah... right
[15:50] <sil2100> tvoss: pong
[15:51] <charles> kenvandine, iirc tvoss and pmcgowan and I decided on friday that the UI issue wouldn't block silo 014, we'll pick that issue up separately
[15:51] <tvoss> kenvandine, +1 from my side
[15:52] <kenvandine> yeah, i'm just trying to decide if i should land the settings branch that shows the switch
[15:52] <kenvandine> i think i will
[15:52] <kenvandine> it works... just can trigger the UI bug :)
[16:06] <sil2100> brendand: ping
[16:07] <brendand> sil2100, hey
[16:08] <sil2100> brendand: meeting1
[16:10] <bfiller> robru: could you reconfig silo 4 please?
[16:12] <robru> bfiller, done
[16:12] <bfiller> robru: thanks
[16:12] <robru> bfiller, you're welcome
[16:13] <brendand> sil2100, sorry - i couldn't join. something to take care of at home
[16:14] <pmcgowan> kenvandine, yes lets land
[16:16] <oSoMoN> robru, hey, can you please publish silo 12 when you have a moment?
[16:16] <robru> oSoMoN, lemme look
[16:17] <kenvandine> tvoss, did you see the publishing failure for silo 14?
[16:23] <sil2100> olli: ping
[16:23] <olli> sil2100, pong
[16:24] <tvoss> kenvandine, ack
[16:26] <bzoltan> sil2100:  I am checking this http://ci.ubuntu.com/smokeng/utopic/touch/mako/183:20140811:20140809/9605/calendar_app/ and running the same tests with phablet-test-run calendar_app  on a stock 183 image. I see 4 failures the dash has one.
[16:27] <bzoltan> psivaa: Is there any news?
[16:27] <sil2100> bzoltan: right, so... there is a reason for that
[16:27] <sil2100> bzoltan: I need to update the testing wiki page, but right now you have to install an additional package before running the test to get those passing ;/
[16:27] <sil2100> bzoltan: as you know currently there's no way to force fetching dependencies for click packages when testing
[16:28] <sil2100> bzoltan: one moment
[16:28] <sil2100> bzoltan: address-book-service-dummy is the package
[16:28] <cjwatson> bzoltan: looks like https://launchpad.net/ubuntu/+source/gcovr/3.1-1ubuntu1 should fix that, so I think you can retrigger the build since that's in utopic now
[16:30] <psivaa> bzoltan: yea, looking at the backlog mterry appears to have uploaded a fix for that
[16:30] <psivaa> ohh yea, just noticed cjwatson message too. thanks :)
[16:31] <bzoltan> cjwatson: psivaa: mterry: \o/ thank you all. If it all looks good I can start rolling out cool Toolkit fixes.
[16:32] <mterry> yay
[16:32] <sil2100> brendand: so! Did you have any progress on camera-app and the other failures?
[16:39] <kenvandine> mterry, confirmed... your gcovr fixed it :)
[16:40] <kenvandine> mterry, thanks!
[16:40] <bzoltan> sil2100:  Ahh... that explains
[16:40] <mterry> kenvandine, awesome
[16:41] <bzoltan> psivaa: What is the way to trigger a Jenkins build?
[16:41] <oSoMoN> Mirv, robru: hey, can silo 16 be landed?
[16:41] <oSoMoN> s/landed/published/
[16:42] <Mirv> oSoMoN: sure (although I'm already heavily investing myself into USB dongle search)
[16:43] <oSoMoN> Mirv, thanks!
[16:45] <psivaa> bzoltan: i've just kicked off #4567 in http://s-jenkins.ubuntu-ci:8080/job/generic-mediumtests-builder-utopic-armhf/
[16:45] <psivaa> bzoltan: if you have access to that jenkins, you could trigger a 'rebuild' in a failed job and that should do
[16:46] <bzoltan> psivaa: let me see if I have access
[16:47] <cjwatson> sil2100: Do you know of a reason why silos 0, 5, and 16 aren't configured to build against -proposed right now?
[16:49] <cjwatson> I guess 0 isn't important for this
[16:49] <bzoltan> psivaa:  I think I have access, at least I found my qa lab vpn settings... what was the ip address of then s-jenkins?
[16:51] <psivaa> bzoltan: not sure if you'd be able to log in thoug.. 10.98.3.13 is the ip
[16:52] <psivaa> bzoltan: https://wiki.canonical.com/UbuntuEngineering/CI has the info of setting the ci vpn and dns setup
[16:52] <bzoltan> psivaa:  I am in
[16:52] <psivaa> great :)
[16:52] <bzoltan> psivaa: I used to use it some time ago...
[16:52] <psivaa> ack, ack
[16:59] <cjwatson> sil2100,robru: The full set of ubuntu-rtm silos exists now, all configured appropriately (devirt, extra processors, -proposed except for 0)
[16:59] <cjwatson> So you can try the train against them any time
[17:03] <brendand> sil2100, camera-app is still a mystery
[17:04] <brendand> sil2100, i'd like some help from plars/psivaa on that one
[17:04] <brendand> sil2100, the others, well i couldn't reproduce the same failure in weather_app
[17:04] <brendand> sil2100, and somehow i got more failures in gallery than CI did
[17:04] <brendand> sil2100, so still no clear cut answers unfortunately
[17:04] <brendand> not today
[17:05] <plars> brendand: going back a few images, it looks like camera did fail like it is now, then pass, then fail again. So it might be that it doesn't fail every time
[17:05] <plars> brendand: I can try it locally
[17:05] <brendand> plars, you can do that - but i already did several times and couldn't manage to reproduce it
[17:05] <sil2100> cjwatson: thanks!
[17:06] <sil2100> brendand: ok, so in overall I guess those are mostly non-issues from the user perspective
[17:06] <sil2100> brendand: do you think we could promote while facing those issues, or you prefer not to risk it?
[17:07] <plars> brendand: oh, I thought you said you wanted help from me on it.
[17:07] <brendand> plars, i was hoping you could shed some light on what might be different in CI
[17:07] <brendand> plars, or they could just be failing intermittently, i guess
[17:08] <sil2100> Oh, actually...
[17:10] <sil2100> hmm
[17:11] <sil2100> ogra_: did we have an image kicked? ;p
[17:11] <sil2100> Or did we only end up talking about it? ;p
[17:11] <ogra_> sil2100, not by me, should i ? (i thought you would, sorry)
[17:13] <davmor2> sil2100: you were talking to brendand before you kicked a new image
[17:17] <sil2100> ogra_: I will, sorry, I think I'm just used to not being able to build still ;)
[17:17] <ogra_> heh
[17:24] <sil2100> davmor2: so, no promotion checking of 183 sadly, it seems there might be some things we need in 184
[17:24] <imgbot> [17:33] <plars> sil2100: brendand isn't around now, but I think the problem with camera app is the same as we discussed last week - I'm seeing a popup asking for permission to let camera app access the location. Probably he's allowed it at some point, and that's why he can't reproduce it
[17:47] <pmcgowan> plars, the popup is a feature - whats the issue?
[17:48] <plars> pmcgowan: it prevents the tests from running, because the autopilot test doesn't account for it
[17:49] <pmcgowan> plars, there was a fix last week, I think an env var or something to turn off the prompt
[17:49] <pmcgowan> for testing
[17:49] <pmcgowan> sil2100 knows of it
[17:49] <plars> pmcgowan: I've not checked yet, but the other problem as pointed out last week by davmor2, is that the location should be disabled by default for pictures. So why does it even need to request permission for that at all
[17:49] <sil2100> plars: that's strange, the workaround should work and it was working locally for brendand
[17:49] <plars> pmcgowan: ok, I've not heard about that yet
[17:49] <pmcgowan> plars, thats a valid point
[17:49] <plars> sil2100: so did he have the test implement the workaround?
[17:50] <sil2100> plars, pmcgowan: yeah, that's a bit of a more complicated thing, I guess tvoss mentioned the reasons for why it's like that now
[17:50] <sil2100> plars: yes, the current click package has a workaround implemented, it sets a specific evnrionment variable on test start that's disabling the popup
[17:50] <sil2100> (and location in overall)
[17:51] <sil2100> plars: from what Brendan mentioned, it seemed to work for him locally when he even tested today, but fails on smoketesting...
[17:51]  * sil2100 needs to drive home, brb in an hour
[17:51] <plars> sil2100: os.environ['TRUST_STORE_PERMISSION_MANAGER_IS_RUNNING_UNDER_TESTING'] = '1'
[17:51] <plars> is that it?
[17:58] <pmcgowan> plars, yes
[18:00] <plars> ua_location_service_create_session_for_high_accuracy: Error creating instance: virtual com::ubuntu::location::service::session::Interface::Ptr
[18:01] <plars> so it appears to be getting set in the version of the test that was pushed to the device, but it's still failing
[18:02] <plars> when brendand comes back, I'll try to help him debug, but I can reproduce it easily at home also
[18:14] <davmor2> ogra_: do you still run boot charts
[18:14] <davmor2> ogra_: if so is it me or have recent images slowed down
[18:14] <ogra_> davmor2, not until i can move the developer mode code from that device
[18:15] <ogra_> and i havent run mako in a while
[18:15] <davmor2> ogra_: hahahaha
[18:38] <Saviq> robru, can I ask for a publish on silo 11 please :)
[18:38] <robru> Saviq, hmmm yeah I saw that, I just published qtmir though. I think it would be wise to kick an image between those landings.
[18:39] <robru> although we *just* kicked an image...
[18:39] <robru> ok
[18:39] <Saviq> robru, yeah, and silo 2 is like... 65 lines diff...
[18:39] <robru> Saviq, please approve the merges https://ci-train.ubuntu.com/job/landing-011-2-publish/81/console
[18:40] <Saviq> robru, fixed, sorry
[18:40]  * Saviq blames pstolowski
[18:46] <robru> Saviq, so uh hey...
[18:46] <Saviq> robru, ohnoes, silo went awry
[18:46] <robru> Saviq, what did you do in silo 11? citrain seems to think there's only unity8 in there. the others "aren't built" and WATCH_ONLY build doesn't even notice them
[18:47] <Saviq> robru, I reconfigured it in the mean time to change the list of MPs for unity8, nothing else :|
[18:47] <robru> hm
[18:48] <robru> Saviq, ok well the only thing I can think to try is reconfigure again and then WATCH_ONLY build again, gimme a sec
[18:49] <Saviq> robru, indeed the reconfigure here https://ci-train.ubuntu.com/job/landing-011-0-reconfigure/26/console
[18:49] <Saviq> ah no actually not, it does have all the branches
[18:49] <Saviq> and even mentions all the scopes
[18:50] <robru> Saviq, yeah this is messed up.
[18:51] <robru> Saviq, https://ci-train.ubuntu.com/job/landing-011-1-build/155/console it doesn't even try to build anything but unity8.
[18:51] <robru> Saviq, so I only see two options here: get a core dev to pocket-copy the packages to distro (bypassing citrain entirely) or turf the silo and rebuld everything from scratch in a new silo.
[18:53] <Saviq> robru, ugh :|
[18:54] <Saviq> rsalveti, can I bug you for helping with a b0rked silo
[18:54] <rsalveti> Saviq: sure, whats up?
[18:54] <Saviq> robru, except... that will probably fail to push to trunks?
[18:54] <robru> Saviq, right you'd have to manually merge all the MPs
[18:54] <Saviq> ;(((
[18:54] <robru> Saviq, maybe a new silo will be easier?
[18:55] <Saviq> robru, yeah, probably, rsalveti sorry for bugging you
[18:55] <robru> Saviq, ok, will turf it and reassign
[18:55] <rsalveti> Saviq: no worries, let me know if there's something I can do to help
[18:57] <robru> Saviq, ok you're in 6 now, looks like it knows all the projects: https://ci-train.ubuntu.com/job/landing-006-1-build/188/console
[19:04] <sil2100> robru: just got your e-mail
[19:04] <sil2100> robru: I didn't land anything, but let me take a look
[19:05] <robru> sil2100, ok, turfed the silo and started a new one, seems ok now. no idea what went wrong in 11 though
[19:05] <sil2100> robru: was that a whole silo rebuild? Did you know if you could force building the other source packages by mentioning them explicitly?
[19:06] <robru> sil2100, ah no i didn't check that... but they shouldn't need a force rebuild, they should have just appeared in the WATCH_ONLY
[19:07] <robru> sil2100, the weird part I guess is that the silo dashboard showed all 4 projects, so the backend json knew of all four. but the build job could only see unity8
[19:07] <robru> brb
[19:07] <sil2100> robru: I noticed this happens sometimes, sadly - usually the problem is that due to some error (or a bad abort) the information for some packages just gets deleted
[19:09] <imgbot> [19:09] <imgbot> [19:14] <Saviq> robru, when silo 6 builds, I'll do a quick sanity check
[19:15] <pmcgowan> what goodness is in 184?
[19:16] <davmor2> pmcgowan: can't tell you it's a secret shhhhhh
[19:17] <kenvandine> Chipaca, mind if i hijack your settings row on the spreadsheet and add more stuff?
[19:17] <Chipaca> kenvandine: check with ralsina; he's preparing that one
[19:18] <kenvandine> ralsina, do you mind?
[19:18] <Chipaca> kenvandine: there is a branch there that needs to land coordinated with push
[19:18] <kenvandine> i was about to request one which included your branches
[19:18] <Chipaca> kenvandine: i don't mind you piggibacking on it
[19:18] <ralsina> kenvandine: no problem
[19:18] <Chipaca> kenvandine: ah. that would be bad, wrt the push one
[19:18] <kenvandine> ralsina, so what about the push one? is that ready?
[19:18] <ralsina> kenvandine: not quite yet, I have one more branch testing that I want in
[19:19] <davmor2> Chipaca: hey dude where is my green messaging ping telling me there is a new image already damn it ;)
[19:19] <kenvandine> ralsina, eta?
[19:19] <ralsina> which is the branch that adds a lot of autopilot tests... maybe 1 hour
[19:19] <kenvandine> debating if i should do a separate landing
[19:19] <kenvandine> ralsina, ah... ok
[19:19] <kenvandine> ralsina, so you don't mind me adding some more settings branches?
[19:19] <ralsina> kenvandine: I don't mind
[19:19] <kenvandine> cool
[19:20] <popey> davmor2: do you know if we have a bug for the fact that notifications appear over the top of the dash, making it hard to use search or OSK?
[19:22] <davmor2> popey: I think I filed one for the fact that if you went into the google account screen and selected the syncs you then couldn't get back to the accounts page.  But I can't remember if that was filed or an email conversation it was so long ago
[19:22] <popey> no, i mean they obscure the search button
[19:22] <popey> like you can't tap through them like you can on the desktop
[19:23] <davmor2> popey: ah but that is because you can interact with the new ones
[19:23] <popey> yes, i know _why_
[19:23] <davmor2> popey: so no
[19:23] <popey> I'm saying it means you can't use the dash when one is on screen
[19:23] <popey> ok, I'll file one
[19:24] <popey> hmm, snap decisions bugs... unity8?
[19:24] <davmor2> popey: yeap iirc
[19:24] <davmor2> popey: just blame Saviq
[19:24]  * davmor2 runs
[19:25] <Saviq> no you don't
[19:25] <pmcgowan> popey, lol same as desktop
[19:26] <kenvandine> ralsina, can you ping me when it's ok to create the silo?
[19:26] <Saviq> popey, *my* approach would be to allow you to swipe them away
[19:26] <ralsina> kenvandine: will do
[19:26] <kenvandine> thx!
[19:26] <Saviq> popey, but that's not what design wanted, but I think they can be convinced nowadays ;)
[19:27] <sil2100> pmcgowan: the commitlog for 184 is here: http://people.canonical.com/~lzemczak/landing-team/184.commitlog <- but besides that some android changes were pulled in IIRC
[19:28] <davmor2> Saviq: but we blame you and magically it's fixed, aka you must be the magic man :D
[19:28] <popey> Saviq: indeed, i can swipe away iOS ones
[19:29] <pmcgowan> ooo scopes debugging
[19:30] <davmor2> popey, Saviq: what would be nice is to be able to tap on the thing in the background that you were using, ie dash/app etc and have that come to the top again maybe?
[19:32] <Chipaca> davmor2: you didn't get it?
[19:33] <davmor2> Chipaca: nope and not on a reboot either
[19:34] <Chipaca> I didn't either -- but because i haven't configured wifi on this reinstall
[19:35]  * Chipaca configures
[19:36] <nik90> Chipaca, davmor2: I didn't get it either for image 184
[19:36] <Saviq> davmor2, so you mean like the notification layer would actually become an app...
[19:36] <popey> dammit, no notifications appearing for me now!
[19:36]  * popey reboots device hoping for a slew of notifications
[19:37] <Saviq> popey, there's example notifications in lp:unity-notifications that you can use (assuming you have RW image and can install python-notify)
[19:37] <Saviq> davmor2, interesting idea, please add as comment to the bug popey will file :)
[19:38] <Chipaca> hmmm
[19:39] <Chipaca> Saviq: popey: make sure you're both talking about the same thing when you say "notifications"
[19:39] <popey> the things that popup at the top of the screen
[19:39] <Chipaca> davmor2: right now i'm getting i/o timeouts
[19:39] <Chipaca> davmor2: can you check your client logs?
[19:39] <Chipaca> popey: notifying you of what?
[19:39] <popey> email, tweets
[19:39] <popey> you know, notifications
[19:40] <Chipaca> popey: are these things appearing in the messaging menu but not as a popup?
[19:40] <popey> no
[19:40] <popey> they appear as popups
[19:40] <Chipaca> popey: or are they also not appearing in the messaging menu?
[19:40] <popey> usually both
[19:40] <davmor2> popey: actually thinking about it I didn't get my slew of twitter pms
[19:40] <popey> i asked people to tweet me and I haven't seen any
[19:41] <popey> this is the opposite of the bug I filed where I get too many notifications! ☻
[19:41] <Chipaca> popey: so either ubuntu-push-client is dead, or the pollod magnífico is dead
[19:41] <popey> phablet   1563  0.2  0.4 894128  9312 ?        Ssl  20:37   0:00 /usr/lib/ubuntu-push-client/ubuntu-push-client
[19:41] <popey> is magnífico a backend thing?
[19:42] <Chipaca> popey: account-polld
[19:42] <popey> phablet   1605  0.0  0.3 869672  6008 ?        Ssl  20:37   0:00 /usr/bin/account-polld
[19:42] <popey> both running
[19:42] <Chipaca> popey: and the device has network?
[19:42] <popey> phablet@ubuntu-phablet:~/.cache/upstart$ ping bbc.co.uk
[19:42] <popey> PING bbc.co.uk (212.58.246.103) 56(84) bytes of data.
[19:42] <popey> 64 bytes from fmt-vip132.cwwtf.bbc.co.uk (212.58.246.103): icmp_seq=1 ttl=52 time=17.3 ms
[19:42] <popey> 64 bytes from fmt-vip132.cwwtf.bbc.co.uk (212.58.246.103): icmp_seq=2 ttl=52 time=22.8 ms
[19:43] <Chipaca> I'll take that as a "yes", only because there it matches *wtf.bbc.co.uk
[19:43] <popey> ☻
[19:43] <popey> i dont host bbc.co.uk domains on my phone, so yeah, it has network ☻
[19:43] <Chipaca> sergiusens: ^
[19:44] <Chipaca> popey: can you pastebin ~/.cache/upstart/ubuntu-push-client.log ?
[19:45] <sergiusens> davmor2: popey: only tweets from when the app was started reach you: design choice
[19:45] <davmor2> Chipaca: I see i/o timeout
[19:45] <sergiusens> s/app/dameon/
[19:45] <sergiusens> daemon
[19:45] <popey> i have had quite a few
[19:45] <Chipaca> davmor2: yes, something is wonky with the push client right now
[19:45] <sergiusens> popey: I got yours
[19:45] <popey> 20 in the last 10 mins
[19:45] <Chipaca> sorry, push server
[19:45] <Chipaca> but that shouldn't affect pollod
[19:46] <sergiusens> popey: there's a current bug where if the phone goes to deep sleep, you won't get them
[19:46] <popey> it was awake
[19:46] <popey> wide awake
[19:46] <ogra_> pollod ? a daemon made of chicken ?
[19:46] <sergiusens> popey: was the twitter webapp open?
[19:46] <popey> 2014/08/11 20:42:47.454527 DEBUG getting authorization for https://push.ubuntu.com/
[19:46] <sergiusens> why are we discussing this on ci?
[19:46] <popey> 2014/08/11 20:42:47.985490 DEBUG trying to connect to: 91.189.92.86:443
[19:46] <popey> 2014/08/11 20:42:48.303329 DEBUG Connected 91.189.92.86:443.
[19:46] <Chipaca> ogra_: only the best free range chicken
[19:46] <popey> 2014/08/11 20:42:48.304122 DEBUG Session connected after 1 attempts
[19:46] <popey> 2014/08/11 20:45:13.361857 ERROR session exited: read tcp 91.189.92.86:443: i/o timeout
[19:46] <popey> lots of that
[19:46] <ogra_> Chipaca, lol
[19:46] <popey> oh, sorry.
[19:47] <popey> sergiusens: for some of the time, yes
[19:47] <Chipaca> popey: yes, push server has issues, but it shouldn't affect account-polld
[19:47] <popey> ok
[19:47] <popey> Chipaca: http://paste.ubuntu.com/8020054/ your pastebin
[19:47] <Chipaca> popey: thank you kind sir
[19:47] <popey> np
[19:47]  * Chipaca looks
[19:47] <sergiusens> popey: if webapp is open; notifications may not show up
[19:47] <popey> wait, what?
[19:48] <popey> you just said only if the app is open i get them
[19:48] <Chipaca> popey: it says there that it showed you notifications at 2014/08/11 20:19:04.38
[19:48] <popey> which is it?
[19:48] <sergiusens> popey: no, I said the opposite
[19:48] <Chipaca> hah
[19:48] <popey> Chipaca: these are long after that
[19:48] <popey> boom, appearing now!
[19:48] <Chipaca> popey: you only get notifications after the phone is booted
[19:48] <Chipaca> popey: and only if the app is not open
[19:48] <popey> someone touched something!
[19:49] <popey> now I'm getting gmail notifications I didnt get earlier
[19:49] <sergiusens> popey: nobody; it's your phone...
[19:49] <sergiusens> going to ask design to change that fwiw
[19:49] <Chipaca> sergiusens: the pollod has logs :)
[19:49] <popey> still no tweets
[19:49] <popey> sergiusens: either way, I have had both the app open and closed and had no tweets come in
[19:49] <Chipaca> i presume ~/.cache/upstart/account-polld.log
[19:49] <Chipaca> but i don't know for sure :)
[19:50] <sergiusens> popey: https://wiki.ubuntu.com/Process/Merges/TestPlans/account-polld
[19:50] <popey> 2014/08/11 20:37:03 Error while polling 5: Get https://api.twitter.com/1.1/statuses/mentions_timeline.json: dial tcp: lookup api.twitter.com: no such host
[19:50] <Chipaca> 2014/08/11 20:37:00.665111 ERROR Failed gettting current state: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
[19:50] <Chipaca> WAT
[19:50] <popey> it lies
[19:51] <Chipaca> popey: your network might be in an interesting state
[19:51] <Chipaca> your network manager seems to be having fun
[19:51] <popey> OH RLY?
[19:51] <popey> i have rebooted a couple of times in the last hour
[19:51] <Chipaca> popey: seems to have fixed itself towards the end of the log you pasted
[19:52] <Chipaca> ahm... maybe this is before the "start on started unity8"  change?
[19:52] <sergiusens> Chipaca: 2014/08/11 20:19:04.378251 ERROR GetWindowStack call returned Signature too small
[19:52] <Chipaca> popey: what do you have in /usr/share/upstart/sessions/ubuntu-push-client.conf ?
[19:53] <Chipaca> sergiusens: that's fixed (not sure whether landed or not)
[19:53]  * Chipaca checks
[19:53] <popey> http://paste.ubuntu.com/8020089/
[19:53] <Chipaca> yes, looks like it's landed (but obviously not in popey's image yet)
[19:53] <sergiusens> Chipaca: when are you landing start on started unity8 ?
[19:54] <Chipaca> popey: ah, ok, so maybe those network manager errors were during your most recent boot
[19:54] <Chipaca> sergiusens: ralsina is doing that as we speak
[19:59] <davmor2> ToyKeeper: any chance you can give 184 a good going over please and post the results to the mailing list.  Many thanks.
[20:00] <sergiusens> robru rsalveti mind publishing 1 ?
[20:07] <popey> davmor2: bug 1355422
[20:07] <robru> sil2100, ah, makes sense, aborting jobs would make the python script exit prematurely and not save whatever state is necessary.
[20:07] <ToyKeeper> davmor2: Sure, I can do that.
[20:08] <robru> sergiusens, on it
[20:08] <sergiusens> popey: you should change the description to notification bubbles as it can be confused with notifications messaging menu
[20:08] <sergiusens> robru: thanks
[20:09] <popey> sergiusens: i call them notifications because that's what they're called in system settings -> accounts
[20:10] <ralsina> kenvandine: found a bug in that last push branch, so it will take a few minutes more.
[20:10] <kenvandine> ralsina, ok, thx
[20:10] <sergiusens> popey: yeah, but a notification means a vibration and/or sound and/or bubble and/or messaging menu
[20:10] <Chipaca> popey: the bubble is just one aspect of the notification
[20:11] <Chipaca> popey: if you go to system settings -> notifications and disable them, you stop getting them
[20:11] <popey> ok.
[20:12] <Chipaca> popey: but you stop getting the whole thing, not just the bubble
[20:12] <popey> thats not the bug
[20:12] <Chipaca> i know
[20:12] <popey> ok ☻
[20:12] <Chipaca> (that's part of my point)
[20:12] <Chipaca> (and sergiusens')
[20:14] <sergiusens> popey: in other words, you can't dismiss the vibration, sound or bubble but you can dismiss the notification in the messaging menu
[20:14] <sergiusens> popey: I'm just helping you not to get your bug marked incomplete or invalid by the unity8 guys
[20:14] <popey> i can't swipe the bubble away
[20:14] <popey> its in the way
[20:14] <sergiusens> popey: and that's fine
[20:14] <sergiusens> popey: as in; just update your bug to say notification bubble
[20:15] <Saviq> robru, ok, it looks fine, please publish silo 6
[20:15] <popey> i have ☻
[20:15] <popey> bug 1355422
[20:15] <sergiusens> popey: ah; then it's all ok
[20:15] <popey> \o/
[20:15] <sergiusens> popey: and you can't dismiss them and it's been a pain everywhere for me (even desktop)
[20:16] <Saviq> popey, btw, do you get more than one notification per-service at any given time?
[20:16] <robru> Saviq, thanks for rechecking, sorry for the hassle
[20:16] <Saviq> robru, nw
[20:17] <Saviq> robru, it was easy with citrain device-upgrade ;)
[20:17] <Chipaca> Saviq: depends what you mean by notification
[20:17] <Saviq> Chipaca, notification == bubble ;)
[20:17] <popey> Saviq: no
[20:17] <Chipaca> no, notificaiton == bubble, but ok :)
[20:17] <sergiusens> popey: Saviq: that is possible
[20:17] <Chipaca> bubbles, i've never seen more than one
[20:18] <Saviq> Chipaca, well, it sure is possible
[20:18] <sergiusens> Saviq: I get them
[20:18] <Chipaca> Saviq: they seem to be queued (or maybe it's got to be from different apps?)
[20:18] <Saviq> Chipaca, what I'm asking is whether you'd send separate ones if you got two pushes within a few seconds
[20:19] <Saviq> Chipaca, because what you *should* do is update the existing one (i.e. group them per app / service / whatnot)
[20:19] <Chipaca> Saviq: yes, we send separate ones
[20:19] <sergiusens> Saviq: how would the push server know or control that?
[20:19] <Chipaca> Saviq: when building that, the reusable id thing didn't work
[20:19] <Saviq> sergiusens, not the server
[20:19] <Saviq> sergiusens, the post office
[20:19] <sergiusens> Saviq: the client I mean
[20:20] <Saviq> sergiusens, well, it knows when a notification is queued, it's not a fire'n'foget thing
[20:20] <Saviq> sergiusens, so if there is one in queue, or on screen even, it should update that one
[20:20] <sergiusens> Saviq: yeah, how would it know how to group them?
[20:20] <Saviq> sergiusens, by service
[20:20] <sergiusens> Saviq: yeah, I'm talking about the grammar and semantics in the payload
[20:21] <Saviq> sergiusens, well, it knows what's title, what's summary
[20:21] <Saviq> sergiusens, it could just concatenate those and display "2 messages" as the title, and then short excerpts from the titles
[20:22] <sergiusens> Saviq: for the bubble only? and populate the messaging menu with the independent cards?
[20:23] <sergiusens> I sort of like it if it's that way
[20:23] <Saviq> sergiusens, yeah
[20:23] <sergiusens> Saviq: that means I don't need to do the consolidation in account-polld
[20:23] <Saviq> sergiusens, we have limited real estate for notifications, not so much for messaging menu
[20:24] <Saviq> sergiusens, in messaging menu they should probably be grouped by conversation or so
[20:24] <Saviq> sergiusens, it would be rather easy to send group-id or something with the push
[20:25] <Saviq> to have control of that on the remote side even
[20:26] <sergiusens> Chipaca: is that doable ^ ?
[20:26]  * Chipaca reads
[20:27] <sergiusens> Saviq: for gmail I do the grouping by thread id in the plugin itself; for facebook and twitter not much yet
[20:27] <Chipaca> so, when we tried to do that at the start of all this, the reusable id was disregarded
[20:27] <Chipaca> Saviq: ^
[20:28] <sergiusens> well sans group id, is this doable at all?
[20:28] <Chipaca> "group id"?
[20:28] <Saviq> Chipaca, "reusable id" you mean for bubbles?
[20:28] <Chipaca> Saviq: yes
[20:28] <Saviq> Chipaca, that's unlikely, we have ap tests checking that works
[20:29] <Chipaca> it worked on the desktop, but not in unity8
[20:29] <Chipaca> this was a while back though, and i haven't rechecked
[20:29] <pmcgowan> jibel, Ursinha-afk did the otto job issue get resolved?
[20:29] <Chipaca> but we do hold on to the id, so it would be doable
[20:29] <Saviq> Chipaca, but it worked, like... always :/
[20:30] <Chipaca> Saviq: can you get design signoff on that? updating the text of something that is already displayed is a bit of an antipattern afaik
[20:30] <Chipaca> Saviq: maybe we were doing it wrong in a way unity8 didn't cope and the desktop did?
[20:30] <Saviq> Chipaca, http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tests/autopilot/unity8/shell/tests/test_notifications.py#L635
[20:31] <Chipaca> Saviq: i wasn't doubting your word
[20:32] <Chipaca> Saviq: i can probably show you the non-working code that we were using, if i dig
[20:32] <Saviq> Chipaca, yeah, could be useful to debug with MacSlow
[20:41] <Chipaca> davmor2: popey: puhs servers should be happier now
[20:41] <popey> super
[21:01] <Chipaca> Saviq: got to go get dinner, i'll dig that up for you tomorrow
[21:09] <kenvandine> ralsina, how's it going?
[21:09] <ralsina> kenvandine: landing the last branch into push-client, then I'll propose the merge to trunk, and ask for the silo. So... 30' or so at most
[21:10] <kenvandine> ok, i need to head out for a bit, so just ask whoever's around for a silo
[21:10] <ralsina> kenvandine: will do, thanks
[21:11] <kenvandine> ralsina, thank you!
[21:34] <ralsina> robru, can I get a silo for line 29 in the spreadsheet?
[21:34] <robru> ralsina, one sec
[21:38] <ralsina> thx robru!
[21:42] <robru> ralsina, you're welcome