[06:56] <bzoltan> Mirv:  would it be possible to push these MRs to the trunk? https://requests.ci-train.ubuntu.com/#/ticket/705
[07:00] <Mirv> bzoltan: in general we want to see it doesn't get stuck in proposed migration. train will do the merge in around 1h if there's no trouble.
[07:00] <Mirv> bzoltan: I mean, the forced merging needs to be an exception for some specific purpose, not a general rule.
[07:00] <bzoltan> Mirv:  all right .. so it is not weeks
[07:01] <Mirv> bzoltan: nope, depends how many autopkgtests which I belive q-p-u has none, and if any of those have problems
[07:01] <bzoltan> Mirv:  of course, no problem then, false request :) I can totaly wait an hour... the IDE build will start after that and will take 10 hours anyway
[07:01] <Mirv> bzoltan: ok, let's see. it's published in proposed 10 mins ago so we should know more within 30 mins
[07:11] <bzoltan> Mirv:  in the meantime I join the autopilot QtC plugin to the train... ^
[07:14] <Mirv> bzoltan: ok!
[07:26] <bzoltan> Mirv:  höhh... the qtcreator-plugin-autopilot does not exist in the archive ... so the CI train build failes ^ as it can not find the orig.tar.gz
[10:01] <Mirv_> davmor2: could you have time at some point to do a bit of side-by-side comparison with your devices on silo 12 (https://wiki.ubuntu.com/Touch/QtTesting) with/without PPA? All known regressions are now pretty much fixed and I'm warming up to landing Qt 5.5 to xenial.
[10:02] <davmor2> Mirv: no :P
[10:03] <davmor2> Mirv: I'll schedule it in somewhere I'm sure :)
[10:03] <Mirv> davmor2: ok :D I can do without, I've tried to compare as much as I can by memorizing how bad it's on stock xenial and if it's any worse with 5.5
[10:04] <davmor2> Mirv: xenial boots now at least :)
[10:07] <Mirv> davmor2: let's see when you have time or if I should just land it when I'm happy with it
[10:08] <Mirv> jibel: do you want to dave to have a look before landing? just so that I know if to consider it a requirement or not
[10:09] <Mirv> ETA could be late next week during our sprint
[10:10] <Mirv> before holidays anyway
[10:11] <davmor2> Mirv: I can probably have a look tomorrow or later today
[10:15] <Mirv> davmor2: oh, ok
[10:21] <jibel> Mirv, if there is no silo left to land in vivid, why not, but it is not a requirement for xenial and our plate is already full
[10:26] <Mirv> jibel: yes I can understand that. if davmor2 has a bit of time I appreciate a quick comparison but no priority
[10:33] <sil2100> Qt 5.5 yay \o/
[11:48] <jibel> sil2100, Kaleo do you know if the gallery app approved yesterday has been published to the store?
[11:48] <Kaleo> jibel, no clue
[11:48] <Kaleo> jibel, bfiller is off for thanksgivign
[11:49] <sil2100> hm, I'm not aware of that
[11:49] <sil2100> Ah, today is turkey day in the US, right?
[11:49] <jibel> Kaleo, yeah that's why I ask, it would have been nice to land it before he's off
[11:49] <Kaleo> jibel, maybe he did, dunno
[11:50] <jibel> I don't tihnk he did. anyway now it'll wait
[11:52] <jibel> Kaleo, regarding silo 48, the test plan has not been updated with the new options
[11:52] <Kaleo> jibel, oh my
[11:52] <Kaleo> jibel, good eye!
[11:52] <davmor2> jibel: I see camera, music, twitter and today scopes as updates on my dogfood so I'm gonna say he didn't
[11:54] <Kaleo> jibel, doing it now
[12:02] <robru___> well that's just great
[12:06] <Kaleo> jibel, the wiki is not letting me authenticate to paste the test :/
[12:07] <jibel> Kaleo, uh, what type of access is required?
[12:07] <Kaleo> jibel, just login to edit
[12:07] <jibel> just an LP account?
[12:07] <Kaleo> jibel, yes
[12:07] <Kaleo> jibel, it's just broken
[12:07] <Kaleo> jibel, :/
[12:07] <Kaleo> jibel, hopefully it's  temporary
[12:08] <jibel> Kaleo, it works here
[12:08]  * jibel is not proposing to update the test plan ;)
[12:08] <Kaleo> jibel, must be specific to my account for whatever reason
[12:08] <Kaleo> jibel, I have the test here
[12:08] <davmor2> boiko_: I'm just looking at silo 35, the address-book-service test plan still talks about eds is that still used in addressbook?
[12:08] <Kaleo> jibel, just want to paste it :)
[12:09] <Kaleo> jibel, http://pastebin.ubuntu.com/13514083/
[12:09] <Kaleo> jibel, 4th attempt to login, still waiting
[12:09] <Kaleo> jibel, AH AH
[12:09] <boiko> davmor2: I have no idea, renato or bfiller might know it better, but I think it is still used, I think only syncevolution got dropper
[12:09] <jibel> robru___, I'm sure testing IRC clients at 4AM is really great :P
[12:09] <Kaleo> jibel, working !
[12:09] <davmor2> boiko: ah thanks
[12:09] <robru> jibel, what else would I do at 4AM? you want me to break the train instead? ;-)
[12:10] <jibel> robru, well, 4AM is still time to socialize or sleep
[12:10] <robru> pffff
[12:12] <Kaleo> jibel, one test added, other one coming up
[12:12] <jibel> Kaleo, add a comment on the card once it's done, and we'll unblock it
[12:13] <Kaleo> jibel, ok, thanks
[12:51] <Mirv> popey: I wonder if you can get http://s-jenkins.ubuntu-ci:8080/job/dropping-letters-click/lastSuccessfulBuild/artifact/com.ubuntu.dropping-letters_0.1.2.2.69_all.click to the store? see https://code.launchpad.net/~dropping-letters-devs/dropping-letters/trunk (four lines removed)
[12:52] <popey> ooh, that landed finally?
[12:52] <popey> Sure will!
[12:53] <Mirv> popey: ok, thanks! what about the clock? rev 411 would have its similar part done https://code.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/trunk . I don't see a .click successfully built anywhere however. but it seems the UITK 1.3 is still in a separate branch so I guess it wouldn't be conflicting.
[12:53] <Mirv> popey: that said, I can't set alarms on xenial anyway so right at the moment it's no difference...
[12:53] <popey> they moved to https://core-apps-jenkins.ubuntu.com/
[12:54] <popey> will take a look
[12:54] <popey> i cant get to s-jenins
[12:57] <Mirv> popey: ok I don't see other than branch builds there
[12:57] <Mirv> popey: what about https://private-fileshare.canonical.com/~tjyrinki/droppingletters/com.ubuntu.dropping-letters_0.1.2.2.69_all.click ?
[12:58] <Mirv> popey: it tries to build clock too in s-jenkins but fails with /trunk_dir/backend/modules/Alarm/sound.cpp:27:56: error: 'AppDataLocation' is not a member of 'QStandardPaths'
[12:59] <Mirv> but in that job there hasn't been a successful clock build for at least three months
[13:00] <Mirv> heh, sudo pbuilder --execute --basetgz /var/cache/pbuilder/utopic-armhf.tgz --bindmounts out -- click_build.sh
[13:01] <Mirv> sudo pbuilder --execute --basetgz /var/cache/pbuilder/utopic-armhf.tgz --bindmounts out -- click_build.sh
[13:01] <Mirv> maybe it's that outdated clock job, I try commenting out and modifying to be more like the dropping letters job
[13:01] <popey> Don't worry, I can build fine
[13:02] <popey> It's just that I cant see that server
[13:06] <Mirv> ok
[13:21] <Mirv> davmor2: FYI tested citrain on 12 which I claim to be problematic on QtTesting page. it seems to work (thanks to the recent fixes in the citrain tool) but I needed additional rm -rf ~/.cache/QML/Apps/ via adb shell still before it booted properly up
[13:54] <jibel> Kaleo, it seems that the shutter sound option doesn't work, if I turn it off I still hear the sound
[13:57] <ogra_> you're just holding it wrong
[13:58] <ogra_> (just hold it in a way that your finger covers the speaker and it will work ;) )
[14:01] <Kaleo> jibel, hmmmm, I'm going to guess it's a security thing and I tested in debug mode
[14:01] <Kaleo> nerochiaro, ^
[14:04] <nerochiaro> Kaleo: jibel: what do you mean with debug mode ?
[14:04] <Kaleo> nerochiaro, forget what I said about that
[14:04] <Kaleo> nerochiaro, can you verify again that your code works?
[14:04] <nerochiaro> Kaleo: sure
[14:04] <jibel> Kaleo, I removed the pre-installed click, installed the new one, and rebooted, then played with the camera
[14:04] <nerochiaro> jibel: if you restart the app, does it change anything ?
[14:05] <Kaleo> nerochiaro, does it not work the very first time?
[14:05] <Kaleo> nerochiaro, maybe gsettings key not there yet?
[14:06] <jibel> nerochiaro, no restarting the camera with shutter sound off, or restarting the device then the camera doesn't change anything
[14:06] <nerochiaro> Kaleo: that's my thinking (though it is not a gconf key, it is a QSettings key). let's see what jibel says
[14:06] <jibel> sound is still playing
[14:06] <nerochiaro> Kaleo: jibel: ok, i will look into it some more
[14:06] <jibel> and the QML cache seems to be broken too btw
[14:06] <nerochiaro> jibel: krillin ?
[14:06] <jibel> nerochiaro, yes krillin 189
[14:06] <jibel> rc-proposed
[14:07] <Kaleo> jibel, QML cache?
[14:07] <Kaleo> jibel, nothing to do with the camera right? :)à
[14:07] <jibel> Kaleo, no nothing
[14:07] <Kaleo> ok :)
[14:08] <jibel> Kaleo, I was just checking if the cache from previous version could confuse the app
[14:08] <jibel> Kaleo, but there was none for the camera
[14:08] <Kaleo> right
[14:08] <Kaleo> oh
[14:08] <Kaleo> that's bad
[14:08] <Kaleo> very bad
[14:08] <Kaleo> unless you never ran the previous version?
[14:08] <jibel> Kaleo, it seems to be cleared on boot
[14:08] <Kaleo> ah I heard something like that before
[14:09] <jibel> Kaleo, I tried with the gallery too, verify that there is a cache, reboot, and then .... nothing
[14:09] <Kaleo> :(
[14:09] <seb128> it's on purpose I think
[14:09] <jibel> we already had such regression last cycle but I think it had been fixed
[14:10] <seb128> don't remember the details, but it ensures there is no stalled buggy cache or at least that reboot fixes issues with those
[14:10] <jibel> seb128, is the a bug or a reference somewhere?
[14:10] <jibel> hm, okay
[14:10] <seb128> could also be that it ensures caches are rebuilt after a qt update
[14:12] <jibel> seb128, ah no it was bug 1500372, cache was cleared on stop not reboot, clearing it on boot is fine I suppose
[14:24] <mardy> jibel: I see that you marked bug 1418090 as committed, but according to https://requests.ci-train.ubuntu.com/#/ticket/614 the silo is still under QA
[14:24] <mardy> jibel: just wondering if it was a mistake
[14:30] <jibel> mardy, let me check
[14:32] <jibel> mardy, it is fixed in  ubuntu-system-settings-online-accounts (0.7+15.04.20151120-0ubuntu1)  published yesterday which should be on today's image
[14:32] <jibel> according to the changelog
[14:33] <jibel> mardy, and this is the version on krillin rc-porposed 189
[14:34] <jibel> trainguards do you know why https://requests.ci-train.ubuntu.com/#/ticket/614 is not set to landed while the package is in the archive?
[14:35] <sil2100> jibel: because the xenial package is still in -proposed
[14:35] <sil2100> Autopkgtests are failing
[14:35] <sil2100> http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#ubuntu-system-settings-online-accounts
[14:35] <jibel> sil2100, ack
[14:35] <jibel> mardy, ^
[14:35] <sil2100> Failing autopkgtests are making me a saad panda
[14:35] <sil2100> :(
[14:36] <mardy> sil2100, jibel: did you just do something to that ticket? Before, it was not telling me about this problem; it was in "Ready for QA" state, that's why I was asking
[14:36] <sil2100> No, I just looked at it
[14:37] <jibel> me too
[14:38] <mardy> sil2100: weird. Anyway, in this case anyway the autopkgtests have a good reason to fail: I forgot to update them according to the latest changes
[14:39] <mardy> sil2100: what should I do now? Fix them in the same branch, or something else?
[14:39] <sil2100> mardy: you can fix them and re-release the same silo
[14:39] <mardy> sil2100: excellent, thanks
[14:54] <rvr> brendand: charles: Silo 27 approved
[14:54] <brendand> great
[14:56] <rvr> jgdx: Do you know how to reproduce crash on silo 39?
[14:56] <jgdx> rvr, I think so.
[14:58] <jgdx> rvr, let me produce some steps
[15:00] <jgdx> rvr, 1. Select worst data connection (cellular/bad wifi). 2. Open System Settings -> Updates 3. As soon as you've pressed the updates icon in System Settings, enable Flight Mode from the indicators.
[15:01] <rvr> jgdx: Thanks, I'll try
[16:03] <mardy> sil2100: about this error: https://ci-train.ubuntu.com/job/ubuntu-landing-058-1-build/17/console
[16:03] <mardy> sil2100: does it mean that I should take the published package and apply the same changes to trunk?
[16:04] <sil2100> mardy: so that's the version that is blocked in proposed, right?
[16:04] <mardy> sil2100: exactly
[16:04] <sil2100> mardy: if that's the version and you're using the very same silo for re-releasing, then just use the force_rebuild flag
[16:04] <mardy> sil2100: if I sync that to trunk, there's nothing left to merge...
[16:05] <mardy> sil2100: ah, perfect
[16:05] <sil2100> mardy: since you'll be re-releasing with some new changes on top :)
[16:14] <tvoss> sil2100, https://launchpadlibrarian.net/227692032/buildlog_ubuntu-vivid-ppc64el.trust-store_2.0.0%2B15.04.20151126-0ubuntu1_BUILDING.txt.gz
[16:14] <tvoss> sil2100, seems like a ppc64el hiccup, do I just retrigger?
[16:18] <sil2100> tvoss: what silo is it?
[16:18] <tvoss> sil2100, 47
[16:20] <sil2100> tvoss: it *might* be a hiccup, or an issue with the system on ppc64el - retriggering in the meantime
[16:24] <sil2100> tvoss: yeah, looks good now
[16:25] <sil2100> jibel, davmor2, robru: anything to discuss on the landing meeting?
[16:25] <jibel> sil2100, not really
[16:25] <davmor2> sil2100: well there is congratulating a new core dev and more important seeing cats but other than that not really
[16:28] <tvoss> sil2100, thanks
[16:53] <cjwatson> tvoss,sil2100: Just a hiccup, there are some known guest memory corruption issues *hides* but fortunately they're quite rare.
[16:53]  * tvoss notes that mentioning ppc64el is a very good way for calling out to cjwatson :)
[16:53] <tvoss> cjwatson, thx :)
[16:54] <cjwatson> tvoss: More that I tend to look into hiccups people report with Launchpad :)