[02:09] <imgbot> [03:24] <imgbot> [03:24] <imgbot> [09:03]  * sil2100 is flashing
[09:09] <Mirv> sil2100: I can get the error even when running the single add_photo test now. but I don't seem to have big problems creating an album / adding a photo manually.
[09:10] <Mirv> sil2100: something funky though sometimes, like the animation that opens album doesn't open up fully.
[09:10] <Mirv> sil2100: I wonder if it depends on the amount of images, and maybe on whether camera app AP were run before since they take a photo?
[09:12] <Mirv> surely there are some bugs in gallery-app, no doubt about that, but it's not probably that it was broken in #17, fixed in #18-#19 and broken again in #20-#21. I'd more guess that it has been the same but the test errors out in certain environment.
[09:23] <sil2100> hmmm
[09:24] <sil2100> Mirv: thanks! I wonder why it suddenly started being a problem again
[09:27] <popey> cihelp: can someone help me with 91.189.93.70:8080/job/generic-mediumtests-utopic/119/console ? from https://code.launchpad.net/~carlos-mazieri/ubuntu-filemanager-app/app-devel-pre1/+merge/217958
[09:27] <popey> "E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
[09:27] <popey> seems broken.
[09:27] <psivaa> popey: let me take a look
[09:28] <popey> thanks
[09:31] <dbarth> hi
[09:32] <dbarth> sil2100: i have a new request line 32, to rebuild some peripheral OA packages, just in case
[09:32] <dbarth> + 2 upstream bug fixes in there
[09:32] <sil2100> dbarth: ok, still waiting for the MP list and/or sources list :)
[09:32] <Mirv> dbarth: don't set the request to "Ready?" "Yes" before it's actually ready, since there'll be immediate ping on the another channel :) (I mean, currently the MP:s aren't listed yet)
[09:37] <dbarth> uh, the mp list is in my open tabs...
[09:38] <dbarth> sil2100: done
[09:40] <sil2100> dbarth: thanks! Assigned!
[09:45] <alf_> ev: Hi! Any ETA for s-jenkins restart? (I assume this will fix the stuck armhf/mako jobs?)
[10:03] <sil2100> Mirv, ogra_, psivaa: so, I got the same ofono list-modems crash on messaging-app, weather app tests still running
[10:04] <sil2100> davmor2: how's it looking so far?
[10:04] <davmor2> sil2100: well being as I've been on it for a whole 4 minutes ;)
[10:04] <sil2100> davmor2: woot, let's ship it!
[10:04] <sil2100> :D
[10:05] <davmor2> sil2100: my day starts technically as 11:00 so 5 minutes ago :)
[10:05] <sil2100> Hey hey, 11:00 was an hour and 5 minutes ago!
[10:05] <sil2100> ;)
[10:06]  * sil2100 different timezone
[10:06] <davmor2> sil2100: yeah but not in the real timezone :P
[10:07] <sil2100> pfff!
[10:08] <popey> ev: https://code.launchpad.net/~popey/ubuntu-clock-app/fix-1315318/+merge/218067 is failing - i know fginther was setting it up to test on devices rather than desktop, can you help or do I need to wait for him?
[10:08] <davmor2> sil2100: I'm just transferring my data over fresh
[10:08] <sil2100> Damn, 6 failures on weather app
[10:08] <sil2100> davmor2: could you do some additional tests for weather-app?
[10:09] <davmor2> sil2100: sure
[10:09] <sil2100> Thank you :)
[10:16] <sil2100> The weather app autopilot tests make me angrrry
[10:16] <sil2100> Mirv: ok, anyway, could you fill in a bug for this add_photo issue? :)
[10:17] <sil2100> Mirv: let's poke Bill once he's up with that
[10:17] <davmor2> sil2100: minor bug number http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-05-12-111506.png  I'm assuming that red dotty thing should be to the right of the last letter,  It starts under the magnifying lens which I think is the issue
[10:18] <sil2100> davmor2: I wonder what's up with that dotty, I saw it during messaging app tests today as well - when did they add that?
[10:18] <davmor2> sil2100: recently
[10:18] <davmor2> maybe the keyboard changes
[10:19] <sil2100> Don't think it's OSK related, don't remember seeing that change - maybe in UITK?
[10:20] <davmor2> sil2100: could be
[10:30] <nik90> sil2100: I got an update on the https://bugs.launchpad.net/bugs/1314533. It seems recently there was a regression in the UITK which causes pagestack to behave differently. I have been coordinating with t1mp_ to fix this. The fix for the UITK regression has been merged into staging. I am just waiting on it to be merged to trunk and pushed to the phone. When
[10:30] <nik90> that happens, hopefully the clock apps tests should start passing.
[10:31] <nik90> sil2100: The long alarm save times do not seem to happen any more on the latest utopic images after the recent EDS alarm status fix by renato.
[10:31] <nik90> sil2100: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1316736
[10:32] <sil2100> nik90: excellent! Thanks for the info
[10:33] <sil2100> nik90: do you think the UITK regression could have affect on some other tests of other applications?
[10:33] <nik90> sil2100: it could affect application that depend on pagestacks..so yes
[10:41] <sil2100> hm, I guess weather app doesn't seem to be using pagestacks
[10:41] <Mirv> sil2100: so there's already a bug from you https://bugs.launchpad.net/gallery-app/+bug/1304950 , I wonder if that should be reused or a new one filed
[10:41] <Mirv> well that claims it's fixed so I guess a new one is the answer
[10:42] <sil2100> Mirv: hm, I think re-opening might be possible, but maybe a new one could be cleaner. Is the failure looking similar?
[10:42] <sil2100> i.e. MediaSelector issues?
[10:43] <Mirv> sil2100: nope, I think this one is different even though the same test.
[10:43] <sil2100> Then a new bug please :)
[10:48] <davmor2> seb128: who deals with the interaction between online-accounts and the setting-app?  It is doing some really strange stuff of late
[10:49] <Mirv> argh, what is LP doing to my bug report..
[10:50] <Mirv> sil2100: bug #1318596 (with funky hidden comments in between when I tried to hide one and offer a fuller copy-paste in the next comment, but LP decided to for some reason hide _all_ my comments, even the new ones)
[10:53] <sil2100> uh
[10:53] <sil2100> I didn't know one could hide comments in overall
[10:54] <Mirv> maybe LP just wanted to firmly guide me towards using attachment also for the second log
[11:02] <davmor2> popey: can you try a quick test.  Send a message to a phone, have an audible ping, reply to the message from the indicator, Send a second message, lose the audible ping, and lose the ability to return the message from the indicator
[11:02] <seb128> davmor2, mardy
[11:02] <davmor2> seb128: thanks
[11:03] <davmor2> mardy: I'll be upsetting you shortly
[11:03] <mardy> davmor2: mmm... any way to avoid it?
[11:04] <davmor2> mardy: No
[11:05] <mardy> davmor2: OK, if it's fate, I'll accept it ;-)
[11:09] <davmor2> mardy: Is there any work on improving how the accounts app interacts with Settings app.  Currently it's a bit meh.  If you open setting, open accounts, add a new account, add a new <anything_but_ubuntuone> account, when the account setup is mostly complete the account and settings app both seem to minimise, then if you click on the accounts window it completes the account setup, if you hit back you get a black screen for 30 seconds, and the
[11:09] <davmor2> n it has minimised the setting app rather then switching back to it
[11:11] <davmor2> mardy: there are bugs for this that date back so trusty I was just wondering if there was any work scheduled for it
[11:11] <davmor2> s/so/to
[11:12] <ev> popey: sorry for the delay. Today is back to back calls. I'm not sure I follow what the problem is. If I step through the maze of Jenkins links, I end up here: http://s-jenkins.ubuntu-ci:8080/job/generic-click-autopilot-runner-mako/153/#showFailuresLink . It looks like you have real test failures.
[11:14] <mardy> davmor2: yes, this will fix it: https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/signon-ui/+merge/217589
[11:14] <davmor2> mardy: fantastic :) thanks
[11:16] <popey> davmor2: hm, just sent a message, got a ping and notification, nothing showing in incoming indicator, next text just disappeared, no ping, nothing
[11:16] <mardy> davmor2: if you have time to try that branch and leave a comment, BTW, that would be really appreciated, because for reviews I have to borrow alex-abreu from webapps, and he's always busy :-)
[11:16] <popey> davmor2: however i see both in the messaging app
[11:16] <davmor2> mardy: will do latter today
[11:17] <davmor2> popey: as do I and I can reply from the messaging app just not the indicator
[11:17] <davmor2> sil2100: ^
[11:18] <Mirv> sil2100: so, the touch input patch will (naturally) go into utopic first to qtbase, but the patch is touching code (XCB platform plugin) that is not installed on the devices
[11:19] <popey> ev: that's a vpn link which is no good for community people to debug, is there a public url that non-canonical people can get to?
[11:19] <Mirv> sil2100: oh, a correction, it's installed but not used since Mir is used instead
[11:20] <ev> popey: https://jenkins.qa.ubuntu.com/job/generic-click-autopilot-runner-mako/153/#showFailuresLink
[11:21] <popey> thanks
[11:21] <popey> nik90: ^ see these clock failures? is this the alarms taking too long to save still?
[11:22]  * nik90 looking
[11:22] <nik90> popey: It could the UITK regression I was talking about above https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1316736
[11:23] <nik90> popey: after creating an alarm, AP needs to go to the alarm tab to check the alarm count to confirm the alarm creation. However due to the regression, it goes to the clock tab after saving alarm and thus AP gets the wrong alarm count
[11:23] <popey> ah
[11:24] <popey> t1mp_: do you know when the fix for bug 1316736 will land?
[11:30] <t1mp_> popey: we start the new landing today
[11:30] <popey> ok, thanks
[11:33] <psivaa> popey: re: 91.189.93.70:8080/job/generic-mediumtests-utopic/119/console. still working on it. awaiting access to the server.
[11:33] <popey> thanks
[11:37] <cjwatson> ogra_: Can you remind me where the custom "zip" binary (/srv/cdimage.ubuntu.com/utouch-android/zip) used in touch image builds comes from?
[11:37] <cjwatson> Oh, it's identical to /usr/bin/zip on nusakan
[11:37] <ogra_> cjwatson, we dont use, build or provide zips anymore ... just rip it out
[11:38] <popey> https://imgur.com/cekokVt anyone else see that orange pip thing in the search box? davmor2 ?
[11:38] <cjwatson> ogra_: It's certainly still called as part of the build
[11:38] <ogra_> hmm, it shouldnt
[11:38] <cjwatson> But I can at least reduce it to /usr/bin/zip, which simplifies deployment
[11:39] <cjwatson> It's called from the ubuntu_data script
[11:39] <davmor2> popey: yes see #ubuntu-app-devel and the point I made earlier :)  zsombi commented on it
[11:40] <davmor2> popey: nik90 pointed it out
[11:40] <popey> k
[11:40] <ogra_> cjwatson, yeah, but we shouldnt call it, i thought i had disabled it :/
[11:40] <ogra_> ugh
[11:40] <cjwatson> ogra_: We shouldn't call ubuntu_data, or we shouldn't call zip?
[11:40] <ogra_> http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/ looks really odd
[11:40] <ogra_> cjwatson, we shouldn't produce and promote zips
[11:41] <cjwatson> I'll get rid of the stale trusty images from there
[11:41]  * sil2100 in a meeting for now
[11:41] <ogra_> system-image only needs the three img files and a rootfs tarball ... people doing stuff with the images at home should use rootstock which takes the same input files
[11:41] <ogra_> so the zips are obsolete
[11:42] <cjwatson> ogra_: OK, I'm certainly happy to bin that since it will simplify deployment
[11:42] <ogra_> yeah, and it was a mess ...
[11:43] <cjwatson> I suspect that mark-current didn't ditch the trusty images because goldfish and maguro have gone away and it didn't realise that's OK
[11:43] <ogra_> rsalveti, you dont use the zips anywhere anymore in the emulator, right ?
[11:43] <ogra_> (i'm pretty sure he doesnt, but confirmation is better)
[11:44] <davmor2> sil2100: so it looks like there are some serious issues with the incoming indicator and it looks to be getting worse not better
[11:44] <cjwatson> ogra_: Do I need to archive a copy of the last goldfish and maguro images?
[11:45] <ogra_> no
[11:45] <cjwatson> Works for me
[11:45] <ogra_> system-image has the latest images that are still supported ... that should be enough
[11:47] <thostr_> sil2100: why can't I cancel silo 9 build any longer?
[11:50] <thostr_> davmor2: which indicator is that?
[11:51] <ogra_> thostr_, the envelope
[11:51] <ogra_> (messaging)
[11:51] <davmor2> thostr_: indicator-messaging.  You sometime get a notification, other times you don't, sometimes you can reply to message other times you can't
[11:52] <davmor2> thostr_: sometimes you get an audible ping sometimes you don't etc etc
[11:52] <thostr_> davmor2: I see
[11:52] <ogra_> looking at that issue and at the failing alarms/apppointment notifications, i wonder if we arent still seeing some bits of the Qt5 bug that stopped rendering
[11:53] <ogra_> it feels a bit like that was only half fixed
[11:57] <cjwatson> ogra_: I can commit http://paste.ubuntu.com/7452005/ or thereabouts once rsalveti confirms
[11:58] <ogra_> yep, looks good ...
[11:59] <alf_> ev: Hi! Any ETA for s-jenkins restart? (I assume this will fix the stuck armhf/mako jobs?)
[12:00] <ev> retoaded: ^ are you aware of this?
[12:01] <alf_> ev: BTW, I have no idea if a restart is the right thing to do, just read that in the channel header and thought that perhaps it would help with the stuck armhf/mako jobs too
[12:11] <thostr_> can anybody cancel silo 9 build for me (seems my powers are not enough any longer...)
[12:11] <alf_> josepht: ^^ FYI (stuck armhf/mako jobs)
[12:13] <josepht> alf_: I'll take a look
[12:13] <alf_> josepht: thanks
[12:14] <josepht> alf_: do you have a link to a stuck job?
[12:15] <Mirv> bzoltan1: you should have landing-018, not sure why the sheet is not updating
[12:16] <bzoltan1> Mirv: thanks .. the Silo18 is not yet ready for playing
[12:16] <alf_> josepht: e.g. http://s-jenkins.ubuntu-ci:8080/job/mir-team-mir-development-branch-autolanding/652/ is stuck since Friday waiting for a mako builder to become free
[12:17] <alf_> josepht: but there are a lot of other stuck jobs (in red) if you go to the main CI page
[12:18] <alf_> josepht: s/mako builder/mako executor/
[12:20] <Wellark> silo9 is "stuck" at "Building" simply because there is an infinite dependency-wait for gcc-4.7 on ppc64el
[12:20] <Wellark> rebuild would pull in a packaging modification which does not try to use gcc-4.7 on ppc64el
[12:21] <thostr_> can anybody cancel build of silo 9?
[12:21] <retoaded> ev, josepht: just looking through the information now.
[12:23] <sil2100> davmor2: are those new regressions? I mean, was it working better in our earlier promoted images?
[12:26] <Mirv> bzoltan1: did you mean your branch is not ready or that yes for you too you don't see the spreadsheet updated?
[12:26] <bzoltan1> Mirv:  I do not see the spreadsheet updated and yes my branch is ready
[12:26] <sil2100> brb, lunch
[12:27] <Mirv> bzoltan1: running manually then, https://ci-train.ubuntu.com/job/landing-018-1-build/28/console
[12:27] <Mirv> sil2100: FYI ^ spreadsheet does not seem to update
[12:27] <bzoltan1> Mirv:  thanks
[12:30] <didrocks> sil2100: FYI, I'm restoring the anonymous access that webops removed without asking us
[12:30] <didrocks> on ci train
[12:30] <Wellark> maybe they had a valid reason for that..?
[12:31] <didrocks> Wellark: just to workaround the redirection
[12:31] <didrocks> for login users
[12:31] <Wellark> ok.
[12:31] <didrocks> Wellark: but that removes the fact that a public process should be visible by everyone
[12:31] <Wellark> didrocks: thostr_ says he lost his ability to rebuild silo9.. any idea why that happened?
[12:32] <didrocks> ev: as per mailing list
[12:32] <didrocks> Wellark: not sure, I think sil2100 will look at for that one
[12:32] <didrocks> he needs to become familiar with the system :)
[12:32] <didrocks> Wellark: maybe linked to the change the webops guys did…
[12:32] <thostr_> ...once he's back from lunch... :(
[12:32] <didrocks> thostr_: ping him directly or mup him
[12:32] <didrocks> thostr_: not nice he ignored you
[12:32] <thostr_> didrocks: already did so...
[12:32] <didrocks> mup?
[12:33] <thostr_> no, justed pinged
[12:33] <didrocks> thostr_: sms sent
[12:33] <thostr_> didrocks: thanks!
[12:34] <didrocks> yw
[12:36] <didrocks> (anonymous reworks)
[12:36] <didrocks> ev: sil2100: as per email, I restored it ^
[12:38] <ogra_> josepht, i clicked rebuild on https://code.launchpad.net/~ogra/ubuntu-ui-toolkit/improve-haptics/+merge/218966 three days ago, there is still no trace of a re-testing of the CI bot today (i just clicked rebuild again, but seems nothing changed)
[12:39] <josepht> ogra_: I'll take a look
[12:39] <Mirv> thostr_: cancelled 009 build
[12:39] <ogra_> thanks
[12:39] <ogra_> :)
[12:39] <thostr_> Mirv: thanks!
[12:40] <Mirv> thostr_: but the spreadsheet seems stalled or something. so did you need a reconfigure as well, or how was it? I can do it on the backend side.
[12:40] <Wellark> Mirv: just a rebuild
[12:40] <Wellark> is needed
[12:40] <Wellark> the list of MP's has not changed
[12:40] <didrocks> Mirv: would be good to figure out why thostr_ can't cancel anymore though, he should
[12:40] <thostr_> Mirv: didrocks: somebody stole my permissions: "strehl-t is missing the Job/Build permission"
[12:41] <Wellark> flashback of the Nokia times..? just wait for the HR email.. ;)
[12:41] <Mirv> thostr_: :( I was happy that my rights were preserved in the reorganization
[12:41] <Mirv> thostr_: Wellark: rebuild started at https://ci-train.ubuntu.com/job/landing-009-1-build/70/console
[12:42] <Wellark> Mirv: thanks!
[12:42] <josepht> ogra_: we're investigating an issue with stuck jobs on s-jenkins now, this is possibly related.
[12:42] <thostr_> Mirv: so, what happened between Friday and today?
[12:42] <ogra_> josepht, ah, great ... as long as its not me i'm all fine :)
[12:43] <Wellark> well, at least Finland lost to Latvia and Russia on ice-hockey.. that's what happend!
[12:46] <dbarth> sil2100: not sure if it's a known problem, but i seem to have lost build privs on jenkins
[12:46] <thostr_> dbarth: welcome to the club
[12:46] <Wellark> dbarth: thostr_ has the same problem
[12:46] <ogra_> Wellark, ice-hockey has no future anyway in a world with global warming :P
[12:48] <dbarth> didrocks, Mirv: adding myself to the list ^^
[12:49] <didrocks> dbarth: first time you try to do something since Friday?
[12:49] <thostr_> dbarth: try to logout/loging couple of times
[12:49] <dbarth> yes
[12:49] <dbarth> oh
[12:49] <thostr_> dbarth: and try to close your browser in worst case
[12:49] <thostr_> dbarth: after doing that in random order it works again for me
[12:50] <didrocks> you can go on the webops channels, they did change something since Friday
[12:50] <dbarth> indeed, that works
[12:50] <didrocks> ev: FYI ^
[12:50] <Mirv> thostr_: Friday and today? ok, no idea, I only know what I read from e-mails from ev etc.
[12:53] <Wellark> hmm.. why is jenkins always creating a clean environment for each MR when it prepares source packages for upload to silo ppa?
[12:53] <davmor2> sil2100: yes it was working more reliably previously
[12:53] <Wellark> it should just a be simple "merge & bzr bd -S" no?
[12:54] <didrocks> Wellark: you have build-deps requirement in debian/rules
[12:54] <didrocks> debian/rules clean may need debhelper with a higher version the machine running it is on
[12:54] <didrocks> or python
[12:54] <didrocks> like dh_python
[12:54] <didrocks> or python3, go, blablabla…
[12:58] <davmor2> sil2100: on a plus side weather seems fine
[12:58] <Wellark> didrocks: right. OK.. I haven't educated myself on which targets in rules are relevant when simply building a source package
[12:58] <rsalveti> morning
[12:59] <rsalveti> ogra_: cjwatson: yeah, we don't use zip files anymore, safe to remove them
[12:59] <ogra_> yay
[12:59] <cjwatson> rsalveti: Great, will do, thanks
[13:30] <sil2100> didrocks, Mirv: are the spreadsheet problems still happening?
[13:32] <sil2100> cyphermox: looking
[13:33] <Mirv> sil2100: still no updates, line 33 has a silo and line 31 (004) has finished building, from what I know
[13:33] <sil2100> Mirv: ok, looking then
[13:33] <fginther> popey, I'm looking into you're earlier pings
[13:33] <popey> thanks fginther
[13:48] <sil2100> didrocks: could you just check if the triggers are still set-up on your side of the spreadsheet? :)
[13:48] <sil2100> didrocks: since manual execution seems to work, but the auto-refreshing doesn't seem to work
[13:50] <fginther> popey, I'm now looking at the latest comment on https://code.launchpad.net/~popey/ubuntu-clock-app/fix-1315318/+merge/218067
[13:50] <davmor2> thostr_: for the lack of audible notification popey wrote https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1317579
[13:51] <fginther> popey, does that imply that the plan is to attempt to merge this again once the sdk change lands?
[13:51] <davmor2> thostr_: I'll add bugs for the other issues
[13:51] <popey> fginther: yeah, nik90 commented on that here earlier.
[13:51] <popey> I think so.
[13:53] <ogra_> oh, i just got mail for https://code.launchpad.net/~ogra/ubuntu-ui-toolkit/improve-haptics/+merge/218966 which tells me it got merged ... the LP UI tells me something completely different though
[13:53] <ogra_> and there seems to be a CI bot run that negated the "Approved" it did itself 4 min before
[13:57] <Wellark> ugh.. when was the last unity8 landing?
[13:58] <Wellark> oh, wait.. never mind
[14:06] <nik90> popey, fginther: https://code.launchpad.net/~popey/ubuntu-clock-app/fix-1315318/+merge/218067 has got nothing to do with the alarm failure. So that MP can be merged. I was referring to https://bugs.launchpad.net/bugs/1314533 earlier here. That requires the UITK fix.
[14:11] <rsalveti> sil2100: hey, want to land a change in ubuntu-touch-session and trigger a new image after that so we can get a working emulator image
[14:11] <rsalveti> sil2100: are you planning to spin a new image already?
[14:12] <sil2100> rsalveti: hi! We didn't land anything important recently, so I guess we can wait for your change and then triggering a new image, no problem
[14:12] <rsalveti> sil2100: awesome, thanks
[14:12] <rsalveti> ogra_: ubuntu-touch-session is part of silo-02
[14:13] <rsalveti> but I'd guess this silo is not yet ready for landing
[14:14] <ogra_> rsalveti, yeah, thats mterrys nemesis landing :) goes on since montha and months
[14:14] <rsalveti> sil2100: ogra_: should we flush the silo then?
[14:14] <ogra_> talk to mterry to stack the changes on to of yours instead
[14:15] <ogra_> *top
[14:15] <sil2100> rsalveti: we can do what we usually do - we do an 'ignore conflicts' assignment
[14:15] <ogra_> or that
[14:15] <sil2100> rsalveti: since silo 002 is anyway waiting for so long, they anyway need to rebuild constantly
[14:16] <rsalveti> sil2100: right, cool then
[14:22] <ogra_> sil2100, rsalveti oops, see the ML ... someone should defintely ping mterry :)
[14:22] <ogra_> (since he just sent out a request for testing exactly that silo)
[14:23] <rsalveti> right, but we can land this and trigger a rebuild
[14:23] <ogra_> sure
[14:26] <rsalveti> sil2100: would need a silo for 34 then :-)
[14:26] <rsalveti> quick one
[14:26] <sil2100> Sure, uno momento
[14:26] <rsalveti> ogra_: https://code.launchpad.net/~rsalveti/ubuntu-touch-session/removing_runlevel_lightdm/+merge/219210
[14:27] <ogra_> approved on both levels
[14:28] <rsalveti> awesome
[14:30] <fginther> nik90, thanks for clarifying. I'll double check with popey on getting this landed
[14:30] <didrocks> sil2100: you didn't answer to thorst still, but it seems it has been figuring it out
[14:30] <didrocks> sil2100: I can remove the triggers
[14:30] <didrocks> and let you define yours
[14:30] <didrocks> if that can help
[14:31] <sil2100> didrocks: thostr_ said some issue was 'resolved', so I didn't know hat to answer to ;)
[14:31] <sil2100> didrocks: yeah, lets migrate them to my side
[14:31] <sil2100> What triggers do you have defined right now?
[14:37] <thostr_> sil2100: problem was that something was broken with my login so I couldn't trigger builds any longer... anyway, works again
[14:37] <sil2100> thostr_: ok! It seems I've been in a meeting when you pinged, good thing it's resolved already
[14:37] <thostr_> sil2100: we just had some testing rounds on silo 13 and discovered some issues... so, if you need more silos right now feel free to take it for time being as I'm not sure if we still get a fix today
[14:38] <sil2100> thostr_: thanks for the info - we're a bit low, but I think nothing urgent needs a silo right now
[14:38] <sil2100> Anyway, I still have to try and fix up the auto-refresh of the spreadsheet
[14:38] <thostr_> sil2100: ok, up to you.
[15:11] <cyphermox> sil2100: so is anything missing for line 18 after all?
[15:11] <sil2100> cyphermox: no no, spreadsheet issues, let me re-trigger the assignment then
[15:12] <cyphermox> oh, alright then
[15:12] <sil2100> Sorry for that ;)
[15:13] <gatox> seb128, hi! i've fixed the issues in this branch: https://code.launchpad.net/~diegosarmentero/ubuntu-system-settings/click-notifications/+merge/218644 and just tesed it in the phone and it works, could you review it?
[15:14] <seb128> gatox, hey, sure
[15:14] <seb128> gatox, laney was wondering earlier about the "blank page" branch status as well, not sure if you saw
[15:15] <gatox> seb128, yes... i'm working in that one, i can reproduce it, but i don't know what is happening yet
[15:15] <seb128> k
[15:15] <gatox> seb128, i hope to propose a branch for that today
[15:15] <seb128> great
[15:16] <seb128> let's do a landing once that happens
[15:17] <gatox> ack
[15:18] <sil2100> popey: do you know who is responsible for the shorts-app?
[15:19] <sil2100> davmor2: so, I'm a bit 'all over the place' today, but what do you think about #22 promotion-wise?
[15:22] <popey> yes
[15:22] <popey> what's up?
[15:22] <davmor2> sil2100: so the sms incoming issues I think are the only worsening item but it works fine from the messaging app.  So I think it is fine
[15:25] <sil2100> popey: just sent an e-mail regarding the recent autopilot test failures to the ML, want to know who to mention as 'person of contact'
[15:25] <popey> sil2100: well, the app hasn't changed, so is this an AP fail or a UITK fail?
[15:25] <popey> balloons: ^
[15:26] <sil2100> popey: yes, I already mentioned that in the e-mail, just want to know who's best to mention as PoC
[15:26] <popey> me
[15:26] <popey> unless it's an AP fail, in which case balloons ☻
[15:26] <popey> where  are the failures?
[15:26] <sil2100> ;)
[15:26] <sil2100> Let me show you the bug
[15:26] <popey> ci.ubuntu.com/smokeng/utopic/touch/mako/22:20140512:20140506.1/7968/sudoku_app/ is good
[15:26] <sil2100> https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1318700
[15:28] <balloons> doesn't appear to be a feed issue at first glance
[15:28] <balloons> that has happened before and could be unexpected
[15:28] <popey> looks like it's trying to open the toolbar and failing
[15:28] <sil2100> The only risky thing that changed in the image is UITK, so I CC'd poor bzoltan about that in the e-mail
[15:29] <popey> do we not test apps when we land UITK updates?
[15:29] <bzoltan> sil2100: ohh...
[15:29] <bzoltan> popey: sure I do ... according to the testplan
[15:29] <popey> great, is shorts on that list?
[15:30] <popey> (rssreader)
[15:30] <bzoltan> popey: Yes
[15:31] <bzoltan> popey: https://wiki.ubuntu.com/Process/Merges/TestPlan/ui-toolkit
[15:31] <bzoltan> popey: shoot if you want to add/remove/change anything
[15:33] <popey> great!
[15:33] <popey> wonder why it fails on AP tests in the lab then.
[15:34] <sil2100> Not only in the lab
[15:34] <sil2100> I ran the tests locally on my mako #22 and it failed, 3 failures
[15:35] <balloons> I can try the older image
[15:35] <balloons> image #19 I guess
[15:36] <bzoltan> popey: I was instructed to ignore failures what are marked red on the dash or fail on the stock image
[15:38] <popey> davmor2: do you have a bug for sms not appearing in indicator incoming?
[15:39] <davmor2> popey: tedg looks like he just reassigned yours so I'm about to write it to the same process I'm assuming they are a similar root cause
[15:39] <popey> k
[15:44] <balloons> the older image seems to run rssreader fine
[15:57] <davmor2> sil2100, popey: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1318724
[15:57] <sil2100> davmor2: thanks!
[15:57] <sil2100> davmor2: do you know if it's visibly worse than, let's say, the last promoted image?
[15:58] <sil2100> I'll mention it in the e-mail in overall
[15:58] <ogra_> sil2100, still in another meeting, might be late
[15:58] <sil2100> ogra_: ACK
[15:58] <davmor2> sil2100: previously you would miss out on audio pings from time to time but you always got the blue envelope and osd now that isn't happening any more
[15:59] <sil2100> huh, why did that suddenly break so badly :|
[15:59] <davmor2> sil2100: the audio pings is popeys bug which I've highlighted in this bug
[16:00] <davmor2> sil2100: it might not of been suddenly, it might just be that the audio ping missing was the first signs of a race and it was hit hard enough to show the other issues
[16:00] <cyphermox> sil2100: got news for me? still Google issues?
[16:00] <sil2100> cyphermox: it should have been assigned, let me recheck the spreadsheet
[16:00] <sil2100> hmmm
[16:01] <cyphermox> I checked and refreshed, etc, no joy yet ;)
[16:01] <rsalveti> sil2100: ogra_: ubuntu-touch-session is in, we can trigger a new image anytime
[16:01] <ogra_> rsalveti, i'll do right after the landing meeting
[16:01] <rsalveti> ogra_: great, thanks
[16:01] <sil2100> cyphermox: ok, so it seems the auto-refresh still doesn't work ;/
[16:07] <balloons> oO I see the source of failures for shorts :-)
[16:08] <balloons> time to investigate
[16:09] <balloons> plars, is weather app a reported bug somewhere?
[16:09] <plars> balloons: no idea
[16:09] <plars> balloons: I thought so, but I don't have it
[16:09] <balloons> I'd not seen or known they existed until now
[16:11] <plars> balloons: it was mentioned in the 'Landing team 09.05.14' email for sure
[16:12] <plars> balloons: there's not a buglink that I see though
[16:12] <plars> which is weird since there's one for filemanager and clock there
[16:13] <balloons> plars, in the mail I see only clock and fm.. or I'm crazy :-)
[16:14] <plars> balloons: it's mentioned above in the text
[16:15] <sil2100> ev: ;)
[16:15] <ev> :-P
[16:16] <balloons> still don't see it. blah
[16:17] <ogra_> image build triggered ...
[16:17] <sil2100> ogra_: just reminding so that it's not forgotten! #22 promotion plz ;) kthxbye
[16:18] <ogra_> promotion running
[16:19] <sil2100> Thank you!
[16:19] <davmor2> ogra_: man you should of forgot ;)
[16:20] <ogra_> hah
[16:20] <ogra_> i never forget anything ....
[16:20] <ogra_> ... i just store it in a place where i never look for it :P
[16:21] <ogra_> hmm, i wonder why the promotion goes so slow today
[16:22] <davmor2> ogra_: it's because although you typed in the name of the script to run you didn't remember to hit enter after it ;)
[16:23] <ogra_> argh !
[16:23] <ogra_> sil2100, there is no 22 :P
[16:23] <ogra_> system-image claims ...
[16:24] <sil2100> huh?
[16:24] <ogra_> yeah, weird
[16:24] <ogra_> it just failed with a python traceback
[16:24] <sil2100> ogra_: how come? Even your script says there is one!
[16:24] <ogra_> yeah, tell that to s-i
[16:24] <ogra_> :P
[16:24] <imgbot> [16:24] <sil2100> My device as well ;p
[16:24] <ogra_> aha
[16:24] <sil2100> Maybe we broke it after that nasty hack with #20?
[16:24] <ogra_> now it worked
[16:25] <sil2100> phew
[16:25] <sil2100> ;)
[16:25] <ogra_> no, that was no hack at all
[16:25] <ogra_> the hack is that we try to keep the versions in sync actually :)
[16:25] <ogra_> by design system-image wouldnt do that
[16:26] <ogra_> anyway
[16:26] <ogra_> [16:28] <ogra_> bah, or not ... at least not completely ... it didnt promote the x86 emulator image
[16:28]  * ogra_ sighs
[16:29] <ogra_> ok, fixed
[16:31] <sil2100> o/
[16:31] <sil2100> Thanks :)
[16:34] <davmor2> ogra_: haha :)  I like it when a fix comes together
[17:07] <balloons> popey, new reminders is proposed in store
[17:13] <popey> i see it
[17:14]  * popey tests
[17:20] <popey> balloons: dpm approved reminders
[17:20] <dpm> *\o/*
[17:21] <robru> bzoltan, silo 19 ready for your request on line 35
[17:21] <bzoltan> robru: thanks!
[17:21] <robru> bzoltan, you're welcome!
[17:34] <imgbot> [17:34] <imgbot> [18:30] <Wellark> could someone with the powerz trigger a rebuild on silo9? thanks!
[18:32] <rsalveti> ogra_: davmor2: something bad happened with latest image it seems, music and video scopes are always empty, and the other custom scopes are not showing up (weather channel, etc)
[18:32] <davmor2> rsalveti: Hey dude in your mail it say utopic-proposed should it not be devel-proposed?
[18:32] <robru> Wellark, done: https://ci-train.ubuntu.com/job/landing-009-1-build/71/console
[18:33] <rsalveti> davmor2: both should work same way, but devel-proposed is indeed better
[18:33] <davmor2> rsalveti: I see music
[18:33] <davmor2> rsalveti: and grooveshark
[18:33] <rsalveti> hm, empty here (after first flash with bootstrap)
[18:34] <davmor2> rsalveti: did you have internet connection on start up?
[18:34] <rsalveti> yes
[18:34] <davmor2> rsalveti: if not once you have do a search
[18:35] <davmor2> rsalveti: so wikipedia has content, weather has content, amazon has content
[18:35] <rsalveti> nothing yet, let me reboot
[18:35] <rsalveti> davmor2: did you upgrade or did a clean flash?
[18:36] <davmor2> rsalveti: clean install of 21 and an ota from that image
[18:36] <rsalveti> right, 21 was fine here
[18:36] <davmor2> I can do a fresh install though
[18:36] <rsalveti> davmor2: cool, that would be nice
[18:36] <rsalveti> let me reflash again
[18:36] <rsalveti> but the x86 emulator has the same issue
[18:36] <davmor2> rsalveti: oh hang on the latest image is 23 I'm on 22 ofcourse
[18:36] <rsalveti> also with a clean image
[18:37] <davmor2> rsalveti: 22 was the promotion.  Let me try an update first and see what happens
[18:37] <davmor2> rsalveti: can you confirm you are indeed on 23 and not 22
[18:37] <rsalveti> yeah, 23
[18:38] <rsalveti> 22 was fine
[18:38] <Wellark> robru: thanks!
[18:38] <davmor2> rsalveti: yeah I forgot there was an update released right after they promoted 22
[18:38] <robru> Wellark, you're welcome
[18:40] <davmor2> rsalveti: you did a bootstrap right?  ota from 22 shows content in everything
[18:40] <rsalveti> yeah, clean install
[18:41] <davmor2> rsalveti: right give me a few minutes then
[18:48] <rsalveti> davmor2: yeah, flashed 23 again, same issue
[18:49] <davmor2> rsalveti: personally I blame the guy who authorised all the changes for i386 ;)
[18:49] <rsalveti> cannot get metdata from remote registry: unity::scopes::NotFoundException: Registry::get_metadata(): no such scope (name = com.canonical.scopes.onlinescopes)
[18:50] <davmor2> rsalveti: yeap broken
[18:52] <davmor2> rsalveti: http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-05-12-195120.png
[18:52] <rsalveti> yeah, same here
[18:54] <rsalveti>     unity::ResourceException: Error downloading https://dash.ubuntu.com/smartscopes/v2/remote-scopes? - server replied: Internal Server Error
[18:55] <rsalveti> wonder if the server is up still
[18:57] <bzoltan> robru: The Silo19 is good to go
[18:57] <robru> bzoltan, alright, publishing
[18:57] <bzoltan> robru: thanks
[18:58] <robru> you're welcome!
[19:14] <robru> boiko, we're out of silos, so I'm freeing a stagnant one for you now
[19:15] <boiko> robru: nice! I will try to be fast on testing this one too, thanks
[19:15] <robru> boiko, thanks, will ping you once it's ready
[19:15] <robru> soon
[19:21] <robru> boiko, alright, building! https://ci-train.ubuntu.com/job/landing-001-1-build/45/console
[19:22] <boiko> robru: thanks
[19:22] <robru> you're welcome
[20:08] <t1mp_> we have some uitk failures on the dashboard, for example this one http://ci.ubuntu.com/smokeng/utopic/touch/mako/23:20140512.1:20140506.1/7982/ubuntuuitoolkit/1111500/
[20:08] <t1mp_> but I don't see anything in the console log what went wrong
[20:08] <t1mp_> is someone around who can help with that?
[20:09] <t1mp_> fginther: ^any ideas?
[20:09] <fginther> t1mp, looking
[20:10] <t1mp> thanks
[20:10] <t1mp> fginther: on http://ci.ubuntu.com/smokeng/utopic/touch/mako/23:20140512.1:20140506.1/7982/ubuntuuitoolkit/ there are a bunch of failures
[20:10] <t1mp> fginther: the ones I checked seem to fail in the same way, in launch_test_application
[20:11] <bzoltan> fginther: t1mp: I have just run the AP suite for the silo18 and the UITK was all OK
[20:29] <fginther> plars, can you provide any insight into the uitk failures in the dashboard ^ ?
[20:30] <plars> looking
[20:30] <fginther> plars, the uitk failures show up in the last 20 test cases (and they all failed with a similar signature)
[20:30] <fginther> I can't find any evidence of a qml crash or OOM killer or...
[20:31] <plars> they all passed on flo, so it would be weird to have them on mako and not flo
[20:33] <fginther> plars, the autopilot failure indicates that the process ID was not present when it asked for it from dbus
[20:33] <plars> fginther: yeah, which is surprising since there was no crash
[20:33] <plars> fginther: not much I can see from this really, I could rerun them though to see if it's reproducible
[20:35] <fginther> plars, worth a shot, I can't think of any other logs to examine at this time
[21:03] <robru> boiko, how's silo 1 going? need a hand with testing?
[21:03] <boiko> robru: nope, testing it already, should finish soon
[21:03] <robru> boiko, cool thanks
[21:12] <bzoltan> robru: I just finished the test of the silo18
[21:12] <robru> bzoltan, great, thanks!
[21:12] <robru> oh,needs qa signoff
[21:12] <bzoltan> robru:  I have pasted all the AP logs to the Silo18 page
[21:12] <robru> ToyKeeper, can you test silo 18 when you get a chance?
[21:13] <bzoltan> robru: ToyKeeper: this time I made my homework better :) I have linked there all the zillions of test results
[21:13] <robru> bzoltan, thanks bzoltan! I'll publish when ToyKeeper says so
[21:14] <ToyKeeper> Hmm, new branch?  (I think the previous one landed already)
[21:14] <robru> ToyKeeper, yeah, looks like a big new feature if you read line 33 in the spreadsheet
[21:16] <bzoltan> ToyKeeper:  here is the MR https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/landing_120514/+merge/219179
[21:16] <ToyKeeper> Yeah, looking at it now.
[21:17] <ToyKeeper> bzoltan: Thanks for including all the extra detail.  :)
[21:17] <bzoltan> ToyKeeper: I try to speed it up :)
[21:27] <plars> fginther: t1mp: I still get 20 failures when I rerun it
[21:28] <fginther> plars, thanks. I have a freshly flashed mako, I'll give it a try there
[21:35] <Wellark> robru: sorry to bug you, but could you kick off another rebuild of silo9 ?
[21:35] <Wellark> I discovered a bug which is now fixed.
[21:48] <bzoltan> ToyKeeper: I drop out to catch few hours sleep... t1mp might be at yourservice for few minutes still. leave me lines if there is  anything wrong with the UITK
[21:49] <ToyKeeper> bzoltan: Will do...  looks good so far though.
[21:55] <robru> Wellark, sure thing: https://ci-train.ubuntu.com/job/landing-009-1-build/72/console
[22:11] <boiko> robru: sorry for the delay, but landing-001 is tested and ready to go
[22:11] <robru> boiko, no worries! publishing!
[22:12] <fginther> plars, t1mp, I didn't see any failures running the uitk tests stand alone.
[22:13] <asac> bzoltan: did you see the toolkit failures on dashboard that plars confirmed?
[22:13] <plars> fginther: hmm, I can run it a third time, but that's really weird
[22:13] <asac> robru: any idea if someone knows whats going on?
[22:14] <fginther> plars, I'm going to try again with the same list of apps that were tested by jenkins
[22:14] <plars> fginther: on that last run, I had it just do a fresh install and *just* do the ubuntuuitoolkit test
[22:14] <asac> plars: ah you guys are investigating if its infra?
[22:14] <fginther> plars, oh
[22:15] <plars> asac: I don't see any way it's an infrastructure issue at this point
[22:15] <asac> plars: http://people.canonical.com/~ogra/touch-image-stats/23.changes
[22:15] <asac> looks suspiciously small
[22:15] <robru> asac, no i'm not up to speed on the uitk issue. just waiting for toykeeper to do qa signoff on the existing uitk silo
[22:15] <plars> asac: could be that it's just sometimes failing, sometimes not - could even be from a previous build but we were lucky enough not to hit it before
[22:15] <asac> robru: will that fix the APs?
[22:16] <asac> i am not sure if pumping uitk in if its currently red is the best approach :)
[22:16] <asac> but havent followed discussion
[22:16] <robru> asac, yeah, i don't see mention of it in the MP: https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/landing_120514/+merge/219179
[22:16] <asac> robru: guess we might want to check with ToyKeeper if she has checked the APs
[22:16] <t1mp> asac: the changes fix some AP failures in a few applications, but they wouldn't fix the failures that we see on the dashboard now
[22:16] <asac> if those are still green for her that would be interesting and might indicate that its fixed
[22:17] <ToyKeeper> Working on it, but it takes a while.
[22:17] <asac> t1mp: what are those failyres about?
[22:17] <asac> t1mp: do we know yet?
[22:17] <plars> I kicked off a 3rd run in the lab, we'll see what happens there
[22:17] <t1mp> asac: the failures on dashboard? I have no idea. I checked the logs and to me it looks like they are failing when starting a new qml app, before the test really does anything
[22:18] <asac> t1mp: this seems to be NEW and reproducible on image http://people.canonical.com/~ogra/touch-image-stats/23.changes
[22:18] <asac> not many things changed. we shouldnt leave the opportunity pass to check what really happened that caused this change of behaviour
[22:18] <asac> at least i would rather say: stop, what happened :)
[22:19] <t1mp> asac: none of those packages look familiar to me (I don't know what they do or if we depend on them)
[22:20] <asac> what would be next step and who should do that?
[22:20] <robru> asac, yeah, none of those appear related to uitk
[22:22] <asac> plars: thought you reproduced that locally?
[22:22] <asac> t1mp: are you running the AP test suite on the uitk silo?
[22:22] <asac> if so, are those tests failing for you there too?
[22:24] <fginther> plars, I'm trying again locally with just uitk, this time with a flash included
[22:25] <plars> asac: no, my phone here is tied up with a different test, but as soon as I can I'm going to try it here too
[22:25] <t1mp> asac: I didn't (and its past midnight for me so I'm not starting new tests now), but zoltan did and he didn't have UITK failures
[22:25] <asac> t1mp: do you know when he did the last rrun? was that on top of #23?
[22:26] <asac> plars: well, if zoltan didnt see it and if fginther didnt see it and given the very small list of changes that feels very unlikely to have an impact on this
[22:27] <asac> i guess our best guess is double checking what is up in infra for a bit first :)
[22:27] <t1mp> asac: from the timestamp of the pastebin http://pastebin.ubuntu.com/7454338/ it seems a few hours ago
[22:27] <asac> so yeah, what you are doing is probably right
[22:27] <asac> also check if any type of change was rolled to the infra
[22:27] <t1mp> asac: I am not sure which image he used
[22:27] <asac> after 22 image run
[22:28] <asac> phablet-test-run could echo some meta info about the image it runs on i guess :)
[22:28] <t1mp> asac: yes good idea
[22:28] <asac> unfortunately sergio isnt on :)
[22:30] <asac> t1mp: filed bug 1318836
[22:30] <asac> hehe
[22:31] <t1mp> asac: :)
[22:32] <asac> plars: maybe there is ac rash?
[22:32] <asac> hmm. not accoding to dashboard
[22:32] <asac> i thoght maybe woopsie upload changed behaviour on crash in a way that causes more noise
[22:33] <asac> not: just a desparate straw to refer this back to a real change, rather than infra flakiness :P
[22:35] <t1mp> plars: you could reproduce the failures? can you run a single test, for example ubuntuuitoolkit.tests.custom_proxy_objects.test_checkbox.ToggleTestCase and see how it fails?
[22:36] <asac> plars: arent our tests getting spread to different devices? maybe the red zone was on a broken device?
[22:36] <asac> well, might not explain why we have two greens before the last red
[22:36] <asac> assuming that those are not null ops :)
[22:37] <asac> i mean the green ones :)
[22:38] <t1mp> could this mean something? /var/log/syslog: {{{
[22:38] <t1mp> May 12 21:13:33 ubuntu-phablet kernel: [ 1452.086555] healthd: battery l=99 v=4374 t=27.4 h=2 st=2 c=-162 chg=u
[22:39] <t1mp> all the failed tests I checked so far have some healthd in the syslog
[22:39] <asac> maybe heat?
[22:39] <asac> ChickenCutlass: ^
[22:39] <asac> is that a throttle message?
[22:40] <ChickenCutlass> asac: healthd is very chatty
[22:40] <ChickenCutlass> asac: we need to quiet it down
[22:40] <ChickenCutlass> asac: should have nothing to do with it.
[22:40] <ChickenCutlass> get those messages on all phones
[22:41] <asac> t1mp: guess red herring
[22:41]  * asac wonders why we dont see those for the green tests
[22:41] <ChickenCutlass> you should always see those
[22:41] <asac> do we only extract syslog info for failed tests?
[22:41] <asac> fginther: do you kno?
[22:45] <t1mp> no uitk failures on flo
[22:49]  * t1mp eod
[22:50] <asac> thanks!
[22:51] <asac> robru: so not sure, but so guess if ToyKeeper cant see the AP failures either we can continue oeprating assuming that plars and CI team will fix it somehow magically. if this persists tomorrow we can still have folks look deeper
[22:51] <robru> asac, sure thing, I'll run some tests myself shortly (just flashing now)
[22:51] <asac> fginther: plars: guess you agree with that assess/recommendation?
[22:53] <robru> bfiller, got you silo 14 for keyboard stuff
[22:53] <bfiller> robru: cool, thanks
[22:53] <robru> bfiller, you're welcome
[23:04] <fginther> asac, agreed, the manual testing is all indicating that nothing is broken (my 2nd run passed as well)
[23:04] <fginther> asac, and I'm pretty sure the syslog data is only saved for failed tests
[23:05]  * fginther steps away again, will check IRC in a couple hours