[09:31] <didrocks> popey: coming?
[09:37] <Mirv> psivaa: what's the latest crash link?
[09:38] <psivaa> Mirv: http://q-jenkins.ubuntu-ci:8080/job/trusty-touch-maguro-smoke-ubuntu-weather-app-autopilot/128/artifact/clientlogs/_usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash/*view*/
[09:43] <Mirv> psivaa: thanks I'll try retracing and submitting to LP that, and then we can assign to bug to some package if it's again QtUbuntu visible in the trace for example
[09:43] <psivaa> Mirv: ack, thx
[09:50]  * didrocks stares at the phone for a minute now
[09:51] <ogra_> does Qt use any od libatspi ?
[09:51] <ogra_> *of
[09:51] <didrocks> popey: working here
[09:51] <popey> yeah, trying to reproduce the sequence of events here
[09:52] <didrocks> popey: you shouldn't use your phone before listening music :)
[09:52] <popey> hah
[09:52] <popey> its a single-use device
[09:52] <popey> play music
[09:52] <popey> _or_
[09:52] <popey> make phone calls
[09:52] <didrocks> right!
[09:52] <didrocks> :)
[09:52] <didrocks> yeah, 2 minutes here, ok, so another bug, but probably not a regression
[09:52] <popey> just like android, 4 years ago
[09:52] <ogra_> yay multitasking
[09:52] <didrocks> so, one less :p
[09:52] <didrocks> popey: rohhh ;)
[09:53] <didrocks> ok, one less
[09:53] <didrocks> 2 other issues to go :p
[09:55] <didrocks> psivaa: while the retracing is occuring, I see no crash on maguro on image 138, can you try to install latest image and revert one after another the 139 diff?
[09:56] <psivaa> didrocks: ack, on it
[09:58] <didrocks> thanks
[09:58] <psivaa> http://people.canonical.com/~ogra/touch-image-stats/20140120.2.changes is what i'm looking at
[09:58] <psivaa> didrocks: mako notes has finished all pass.
[09:59] <didrocks> psivaa: ok, so flakyness
[10:00] <didrocks> psivaa: ack on the .changes, yeah
[10:00] <didrocks> psivaa: as it seems that 138 didn't get any failure
[10:00] <didrocks> psivaa: maybe, as ogra_ mentionned, starts with libatspi2.0-0
[10:00] <didrocks> and then glib-*
[10:00] <psivaa> didrocks: ack, thanks
[10:07] <Mirv> ok similar no-good-retrace of unity8 + qmlscene crashes, but now I'll wait until the LP retracer comes and saves the day
[10:11] <didrocks> Mirv: you mean, you have no good retrace localy, but LP retracer are working?
[10:12] <Mirv> didrocks: yes, that seems to be the case. earlier I used to have good retraces locally (with the lp:daisy instructions), but now it seems not but the previous time LP retracer still got a good retrace.
[10:12] <didrocks> Mirv: have you tried a direct retrace on the phone?
[10:12] <didrocks> or let's wait for LP anyway, do you have the link? :)
[10:13] <Mirv> didrocks: not recently, since it worked when I did "view+save" on the phone and then the rest of it on host
[10:13] <Mirv> yes, bug #1271110 and bug #1271113
[10:13] <didrocks> great!
[10:14] <didrocks> failed retrace
[10:14] <didrocks> for the first one
[10:15] <popey> didrocks: dogfooding 140 is fine.
[10:15] <didrocks> popey: thanks! so only this qmlscene crashers are what prevents us for releasing right now
[10:19] <psivaa> didrocks: reverting libatspi2.0-0 to 2.10.1-0ubuntu1 appear to make the qmlscene crash go away. have run twice with no crash, once more to confirm
[10:20] <didrocks> psivaa: please please confirm! :)
[10:20] <psivaa> running :)
[10:20] <didrocks> seb128: mind if we are going to revert atspi? :p
[10:22] <seb128> didrocks, revert is hype around it seems ;-) sure, go for it...
[10:22] <didrocks> seb128: I can't blame on that one, it's only creating a lot of crashes on maguro, not mako
[10:24] <seb128> didrocks, https://git.gnome.org/browse/at-spi2-core/log/?h=gnome-3-10 ... the new version has only 3 commits, and each are a few liners, should be easy to find out what creates issues
[10:24] <didrocks> seb128: merge from debian as well
[10:24] <seb128> well, I doubt packaging has an impact (also nothing weird in https://launchpadlibrarian.net/162894971/at-spi2-core_2.10.1-0ubuntu1_2.10.2-2ubuntu1.diff.gz)
[10:24] <seb128> do you have a debug stacktrace of the issue?
[10:24] <didrocks> seb128: I would appreciate theMuso doing the investigation work, as it's on a device I don't own, the turnaround is taking time
[10:25] <seb128> sure
[10:25] <didrocks> seb128: can't retrace it :/
[10:25] <seb128> but I'm not sure TheMuso has a maguro either
[10:25] <didrocks> not Mirv, psivaa could (and LP either :/)
[10:25] <seb128> anyway revert, then we can discuss how to debug/fix it
[10:25] <didrocks> yeah, let's be quick and try to get back in shape
[10:26] <seb128> still would be good if somebody would get a debug bt
[10:26] <didrocks> yep
[10:26] <didrocks> at least, it's identified and quite easy to reproduce when running all tests on maguro
[10:26] <didrocks> it's a start
[10:26] <didrocks> I would suggest the QA team, having maguro phones, helping on this
[10:27] <Mirv> didrocks: interestingly, a qmlscene crash was properly retraced a week ago, maguro clock-app one bug #1269080
[10:27] <didrocks> Mirv: not the same apparently, as at-spi new version entered yesterday
[10:28] <didrocks> psivaa: once the third run is done, can you try reupgrading to ensure it's the cause?
[10:28] <Mirv> right
[10:28] <psivaa> didrocks: third run has also finished with no crash. upgrading it now and running to confirm it occurs again
[10:28] <didrocks> psivaa: thanks!
[10:43] <psivaa> didrocks: upgrading libatspi2.0-0 makes the crash occur again
[10:45] <didrocks> psivaa: \o/
[10:45] <didrocks> ok, reverting, thanks psivaa
[10:46] <psivaa> didrocks: yw, i'm now trying to retrace it from the phone itself. could take a bit
[10:46] <didrocks> psivaa: yeah, that would be nice for themuso
[10:52] <didrocks> revert uplaoded
[10:52] <didrocks> ogra_: the first who see it published kick an image ^
[11:25] <davmor2> didrocks: Morning good sir whats the plan for today?
[11:26] <didrocks> davmor2: waiting for image 141 to be kicked in and published, and then, test while crossing fingers :)
[11:26] <davmor2> didrocks: haha
[11:32] <davmor2> asac: do we know when agps is likely to land, and do we know if there will be a big push to make bluetooth work more reliably?
[11:33] <ogra_> davmor2, BT is on the list for the sprint
[11:33] <davmor2> ogra_: nice which one :)
[11:33] <ogra_> i think tvoss had AGPS on his TODO
[11:33] <ogra_> davmor2, core ... next week
[11:33] <davmor2> ogra_: oh nice :)
[11:33] <davmor2> be nice to fix at least mine and popey 's BT woes
[11:34] <popey> \o/ I so want to be "that guy" walking around taking into a bt headset ☻
[11:34] <ogra_> the whole phonedations team willl bring their BT devices to test
[11:38] <popey> and ogra_ will take an ouya controller, right? ☻
[11:39] <davmor2> popey: of course it's important to us that bt game pads connect to the phone plugged into the big tv in your living room :D
[11:45] <ogra_> popey, heh, yes
[11:45] <ogra_> and a wiimote
[11:46] <ogra_> (as well as my zeemote joystick)
[11:50] <davmor2> ogra_: and a ps3 remote and a steam do it properly ;)
[11:50] <ogra_> dont have them ... you have to bring them to bluefin ;)
[11:52] <davmor2> ogra_: oh you in London then? I was maybe looking at coming down as a couple of guys are coming in from the states
[11:52] <ogra_> yep, we are
[11:53] <davmor2> ogra_: I can certainly provide a ps3 remote then I don't play enough games to warrent a steam box :D
[11:54] <ogra_> do they actually sell the controllers yet ? i thought they were still prototyping
[11:58] <popey> ogra_: london next week?
[11:58] <popey> i might pop in
[11:58] <ogra_> cool
[12:00] <davmor2> popey: what day be nice to see you too, I'm thinking Tuesday as it stands.
[12:00] <popey> Tuesday is good.
[12:06] <davmor2> popey: I just need to find out now when my Uncles funeral is likely to be to confirm I can travel now :(
[12:07] <popey> ☹
[12:07] <popey> I've only ever been to funerals on fridays.
[12:08] <davmor2> yeah I have the thursday and friday as my last 2 days from last year.  I'm hoping it will be one of those to be honest
[12:12] <sil2100> didrocks, Mirv: can anyone review? https://code.launchpad.net/~sil2100/cupstream2distro-config/new_extra_pkgs_phone_n_apps/+merge/202441
[12:13] <didrocks> done
[12:14] <sil2100> Sanks!
[12:54] <psivaa> didrocks: Mirv: I reported bug #1271154 with some more traces for qmlscene, that has got duplicated to an older one bug #1269080
[12:54] <didrocks> psivaa: if you feel you have more infos on that one, you can dedpu it or dup the other way around
[12:56] <psivaa> didrocks: ack, not much more info in the new one as of now. but i'll install more dbgsym to see if that trace improves
[12:56] <didrocks> great ;)
[13:05] <didrocks> ogra_: just kicked image #141 now that at-spi2-core is just published
[13:05] <ogra_> good
[13:05] <didrocks> popey: davmor2: once published, can you give it some dogfooding love? ^
[13:05] <didrocks> psivaa: please try to ease the tests if needed ^
[13:05]  * didrocks now goes for a run
[13:06] <popey> sure thing
[13:06] <Mirv> psivaa: so that one is the same that I filed earlier it seems
[13:06] <davmor2> didrocks: no worries won't be till after lunch though
[13:10] <davmor2> talking of which Lunch
[13:17] <alecu> hi, how do I ask for a jenkins rebuild of this branch? https://code.launchpad.net/~mikemc/unity-scope-click/cxx-dlmgr-creds-test/+merge/202138
[13:18] <alecu> btw, I don't have access to s-jenkins.ubuntu-ci. Is that something that's easily available?
[13:19] <sil2100> alecu: hi! You need QA lab VPN access to do that
[13:20] <sil2100> alecu: but since there seems to be a new commit in that branch, CI should run itsel in a moment
[13:20] <sil2100> hm, although I see something wrong there
[13:20] <sil2100> alecu: want me to trigger the rebuild for you?
[13:21] <alecu> sil2100: the latest commit is from 18 hours ago. And it's rev 110, but jenkins says it's built rev 112, 20 hours ago.
[13:21] <alecu> sil2100: so, yes, something seems wrong
[13:21] <alecu> sil2100: yes, please
[13:22] <sil2100> alecu: rebuilt pressed - but I see that even in the rebuild function it wanted to use rev 112 by default (which does not exist?)
[13:24] <alecu> sil2100: it's really weird. If it fails, I'll ask about it to the owner of that branch. He should be starting his day in about two hours
[13:25] <alecu> but that branch is fixing an issue that's preventing many branches from landing, so that's why I wanted to push it forward
[13:47] <sil2100> didrocks: could you take a look at this? https://code.launchpad.net/~sil2100/process-cpp/packaging_mir_requirements/+merge/202462
[13:47] <sil2100> didrocks: since we were also asked to remove the per-arch symbol files, so I used this notation instead to not duplicate - is this ok?
[14:01] <bfiller> sil2100: I think I figured out the keyboard problem
[14:01] <sil2100> bfiller: \o/ what do you think is causing all?
[14:01] <bfiller> sil2100: the language plugins were being built with "all" rather than "any"
[14:02] <bfiller> sil2100: I think that was causing the issue somehow
[14:02] <bfiller> sil2100: because ubuntu-keyboard-<lang> creates an .so but was producing _all.deb package not arch specific packages
[14:03] <sil2100> bfiller: hah! Right, makes sense now, that's the problem for sure
[14:03] <bfiller> sil2100: for some reason it works with the debs built on jenkins and the ones I build on the device but not sure why. So I updatd the MR and will merge it when after it builds
[14:04] <sil2100> bfiller: good catch - it might have worked in jenkins depending on how the CI is set up
[14:10] <cyphermox> davmor2: I'm working on bluetooth already, looking into a way to get rid of hci_qcomm_init and have something that works more reliably
[14:11] <cyphermox> davmor2: popey: if you could bring a bluetooth device to the sprint it would be helpful so we can figure out why your devices in particular we're having trouble with
[14:11] <davmor2> cyphermox: no worries
[14:12] <davmor2> popey: test for you being as you have 2 phones.  switch one off and send a text from the other
[14:13] <popey> cyphermox: yes
[14:13] <cyphermox> though so far, I manage to get the BT address written fine without hci_qcomm_init, I have some trouble with HSP still, and I need to figure out whether it's because of that or something else
[14:13] <davmor2> popey: switch it back on after a minute.  see if you ever receive the text
[14:13] <popey> davmor2: how do I switch off my phone
[14:14] <popey> (semi serious question)
[14:14] <davmor2> popey: hold the power button
[14:14] <davmor2> popey: about 3-5 seconds I think
[14:14] <popey> will test in a bit
[14:19] <popey> davmor2: confirmed
[14:21] <popey> davmor2: now it arrived
[14:21] <popey> bit late, but it got through (after a message sent after it)
[14:23]  * popey afk
[14:24] <fginther> morning
[14:33] <sil2100> fginther: morning!
[14:36] <fginther> sil2100, \o
[14:39] <davmor2> popey: ah so it might be that the second message triggered it then maybe?
[14:39] <popey> maybe, but it came way later
[14:45] <kgunn> didrocks: ping
[14:48] <didrocks> kgunn: pong
[14:49] <davmor2> didrocks: hmmm screenlock seems to be kicking in on phone calls again
[14:49] <didrocks> sil2100: perfect! Thanks a lot (and jenkins is happy too) :)
[14:49] <didrocks> davmor2: is it a regression, you mentionned it before, right?
[14:50] <davmor2> didrocks: it has happened before but got fixed so is a regression.
[14:51] <didrocks> davmor2: is it reliable?
[14:51] <didrocks> popey: do you see that as well? ^
[14:51] <didrocks> davmor2: I see nothing in the recent images that could have impacted this…
[14:51] <davmor2> didrocks: I've had 2 20 minute calls and I've had to unlock the phone both time
[14:51] <sil2100> didrocks: yay! Actually, I found another thing in another package and I wanted to check something with you...
[14:52] <sil2100> didrocks: since indeed unity-scopes-shell now wants to pull in the latest dee-qt, and I think I found the reason why
[14:52] <davmor2> didrocks: let me see if it kicks in on short calls
[14:52] <didrocks> davmor2: yeah, I'm afraid it's more "random" and we just didn't get it
[14:53] <sil2100> didrocks: I checked the dee-qt's sources and... I found something worrying there, which is in sources since a year already!
[14:53] <sil2100> didrocks: I mean, in packaging
[14:53] <sil2100> didrocks: debian/rules has dh_makeshlibs -V as override_dh_makeshlibs
[14:54] <didrocks> sil2100: yeah, it was at the time we didn't know how to unmangle C++ symbols
[14:54] <sil2100> didrocks: it causes a forceful depenedency bump now, since anything that links with it builds using the latest version strict
[14:55] <sil2100> didrocks: since the shlibs that's generated now has libdee-qt5 3 libdee-qt5-3 (>= current_version_that's_installed)
[14:55] <didrocks> sil2100: yeah, it was the only way to do it
[14:55] <didrocks> sil2100: so, no worry if we can release latest dee-qt
[14:55] <didrocks> sil2100: but a symbols file would be nice!
[14:56] <sil2100> didrocks: I'll try working on this - but I'll maybe publish latest dee as well I guess
[14:56] <sil2100> Not to block on this ;)
[14:56] <didrocks> sil2100: dee-qt you mean, not dee? ;)
[14:58] <davmor2> didrocks: yeap happens on a call that is long enough for the screensaver to kick in normally so 1 minute plus, anything less and the phone behaves as normal.  so looks like it might of been an issue for a while and the calls weren't long enough to notice :(
[14:58] <didrocks> davmor2: can you bisect between last good image and that one?
[14:58] <didrocks> davmor2: starting with latest promoted image?
[15:00] <sil2100> dee-qt
[15:01] <sil2100> didrocks: yes ;p
[15:01] <didrocks> sil2100: feel free :)
[15:02] <sil2100> didrocks: btw. are we OK with releasing stuff now?
[15:02] <davmor2> didrocks: I can but I need to do some other stuff too so I'll flick between them and let you know in a nice bug report :)  Other than that the image looks pretty good? popey do you agree
[15:04] <didrocks> sil2100: not until we know from davmor2's results
[15:04] <didrocks> davmor2: well, the whole production is blocked righ tnow
[15:04] <didrocks> right now*
[15:05] <sil2100> didrocks: ok, so I'll prepare everything for release then
[15:05] <didrocks> davmor2: I really think it's the priority to at least checking if we have that on the last promoted image
[15:05] <didrocks> (to know if we unblock the whole pipeline or not)
[15:07] <davmor2> didrocks: yeap I'm on it currently flashing the device while doing other stuff but I might need to finish the app I'm doing before I test so there will only be a few minutes delay it won't be anything massive
[15:07] <didrocks> ok
[15:07] <didrocks> as long as it's not 30 minutes… ;)
[15:08] <davmor2> no :)  might take that long for the flash though ;)
[15:14] <dobey> cjohnston: can you re-trigger the builds for https://code.launchpad.net/~alecu/unity-scope-click/check-valgrind/+merge/202380 ? http://s-jenkins.ubuntu-ci:8080/job/unity-scope-click-ci/176/rebuild is the jenkins link in the comment
[15:15] <dobey> cjohnston: the failure was due to c++ scopes api breaking again, and that was fixed in another branch that's merged to unity-scope-click trunk now.
[15:17] <cjohnston> dobey: done
[15:18] <didrocks> davmor2: the end of the pain period for you on maguro is almost over :)
[15:18] <dobey> cjohnston: thanks
[15:18] <cjohnston> dobey: sure thing
[15:18] <davmor2> didrocks: bring on mako and all of it's pain instead rigfht :)
[15:18] <davmor2> right even :)
[15:18] <didrocks> davmor2: well, different kind of pain :p
[15:18] <davmor2> still much nicer hardware though
[15:24] <davmor2> oh the timing is perfect now just wait for the reboot
[15:24] <bfiller> sil2100: can you review this please: https://code.launchpad.net/~bfiller/ubuntu-keyboard/packaging-updates/+merge/202474
[15:27] <davmor2> didrocks: hmmm another one I just noticed. The keyboard is English yet in the settings app seems to be set to Dansk I'm assuming because it is the first layout listed (that might be an old issue that I've only just noticed though)
[15:28] <sil2100> bfiller: thanks! Going to look at it now
[15:28] <davmor2> didrocks: and of course it goes without say that I blame ogra_ completely for that :D
[15:28] <didrocks> ahah ;)
[15:28] <seb128> davmor2, didrocks: that's a known issue/should be fixed with the next ubuntu-keyboard/u-s-s landing
[15:28] <didrocks> davmor2: hum, english here
[15:28] <seb128> (the dansk issue)
[15:29] <didrocks> ah keyboard
[15:29] <didrocks> ok
[15:29] <didrocks> seb128: do you have a bug to track it?
[15:29] <davmor2> seb128: ah cool thanks
[15:29] <didrocks> davmor2: so, this is on the previous promoted image, right?
[15:30] <davmor2> didrocks: I'm just looking at that image now
[15:30] <seb128> didrocks, no, but I noticed it and it was discussed with bill&co, see https://code.launchpad.net/~bfiller/ubuntu-keyboard/ubuntu-keyboard-active-language/+merge/201990
[15:30] <didrocks> davmor2: I mean, the settings things?
[15:30] <didrocks> seb128: do you know? likely to be on Friday's image, right? ^
[15:30] <davmor2> didrocks: that was on current on my mako
[15:31] <seb128> didrocks, not sure, it needs work on the settings side and synced landing between projects
[15:31] <seb128> but I guess so
[15:31] <didrocks> davmor2: ok, as you refreshed, can you check that as well?
[15:31] <seb128> didrocks, it's not a new issue and only a display bug in the settings
[15:31] <davmor2> didrocks: will do
[15:31] <didrocks> seb128: just trying to assess if it's a "visible" regression from latest promoted image
[15:33] <bfiller> didrocks: it's not a regression really, more a settings UI for languages appeared but doesn't work entirely correctly yet
[15:33] <seb128> didrocks, that never worked
[15:33] <bfiller> didrocks: it will work correctly once u-s-s and ubuntu-keyboard land together
[15:33] <didrocks> seb128: I remember to have set it in French, a while ago
[15:33] <seb128> didrocks, well, as said it's just a display bug of what's the current value
[15:34] <seb128> didrocks, before we didn't have that info in the settings at all
[15:34] <didrocks> ah ok then, thanks for the additional infos seb128, bfiller!
[15:35] <seb128> yw
[15:35] <davmor2> didrocks: screen blanked on r132, so not a regression on the current promoted
[15:38] <didrocks> davmor2: "great" :p well, just need a nice bug report I guess to stamp that ;)
[15:38] <davmor2> didrocks: will do
[15:38] <didrocks> let's wait on popey's result for bug #141
[15:38] <didrocks> image*
[15:39] <davmor2> seb128: so the reason it is on dansk, is that just that it is the first in the list?
[15:40] <seb128> davmor2, yes
[15:40] <davmor2> seb128: okay cool thanks.  It's only so I can keep an eye on it for the change :)
[15:41] <didrocks> davmor2: or learn a new keyboard layout!
[15:42] <davmor2> didrocks: it was more if it doesn't change from that to the selected then there might be an underlying issue, But Dansk souds like great fun to not have a clue in as any other language :)
[15:43] <didrocks> davmor2: exactly! you can start as an intermediate with an azerty layout of course!
[15:43] <didrocks> strongly encouraged :)
[15:43] <sergiusens> can we add phablet-tools to daily release spreadsheet?
[15:44] <didrocks> sil2100: ^
[15:44] <davmor2> didrocks: foreigners with their wrong keyboards ;)
[15:44] <didrocks> sergiusens: starting next week, you will have self-service!
[15:44] <sergiusens> didrocks, sounds good, but what about this week :-)
[15:45] <didrocks> davmor2: it's not because we have to use Shift + & to get "1" and Alt Gr + ' to get { that's it's a wrong layout! :)
[15:45] <sil2100> sergiusens: I can add it ;) didrocks is that what you ^'ed? :)
[15:45] <didrocks> sergiusens: I'll add it for tonight ;)
[15:45] <didrocks> sergiusens: can you release the calendar app btw?
[15:46] <sergiusens> didrocks, sure
[15:46] <didrocks> thanks!
[15:46] <sergiusens> didrocks, again though?
[15:46] <didrocks> trading release ;)
[15:46] <didrocks> hum
[15:46] <didrocks> I added it like next Thursday
[15:46] <didrocks> to fix some AP flackyness
[15:46] <didrocks> didn't notice, you release it since?
[15:46] <sergiusens> didrocks, next or prev?
[15:46] <didrocks> prev
[15:46]  * didrocks broken
[15:46] <sergiusens> didrocks, :-)
[15:46] <didrocks> ;)
[15:46] <sergiusens> yes; with popey on Friday after blockade was lifted
[15:47] <sergiusens> let me see if there's anything new in trunk
[15:47] <didrocks> oh, you didn't update the landing spreadsheet!
[15:47] <sergiusens> didrocks, darn, sorry
[15:47] <didrocks> sergiusens: bad bad bad ;)
[15:47] <didrocks> sergiusens: excellent, in that case, I will call that closed ;)
[15:47] <sergiusens> didrocks, with all the news of that going away I just trashed it in my mind :-)
[15:47] <didrocks> no worry :)
[15:47] <didrocks> let me look at the image diff
[15:47] <didrocks> to find which image has it
[15:48] <sergiusens> wrt that; I tested on the emulator as well; issues seem to be related to why they fail on maguro
[15:48] <didrocks> sergiusens: did you generally get more issues on the emulator btw?
[15:48] <didrocks> seeing how slow it is, it can reveal a lot of timeout races
[15:48] <sergiusens> didrocks, http://people.canonical.com/~ogra/touch-image-stats/20140118.changes
[15:49] <didrocks> sergiusens: excellent, 134 then :)
[15:49] <sergiusens> yup and we might need to increase the autopilot wait time of 10 seconds
[15:49] <didrocks> yeah, would make sense
[15:49]  * ogra_ ften has the feeling that the emulator is faster than maguro once it is boted
[15:49] <ogra_> *often
[15:49] <didrocks> ogra_: hum
[15:49] <didrocks> not here
[15:49] <sergiusens> ogra_, run the calendar; does a lot of weird stuff ;-)
[15:49] <didrocks> and i7, 8G of ram
[15:50] <ogra_> same here
[15:50] <ogra_> but i still have an old emulator here
[15:50] <sergiusens> ogra_, do some IO ;-)
[15:50] <didrocks> (the android, arm emulator is slightly faster to me though)
[15:50] <ogra_> need to upgrade that
[15:50] <sergiusens> ogra_, yeah, you have click disabled most likely
[15:50] <davmor2> didrocks: https://bugs.launchpad.net/dialer-app/+bug/1271210
[15:50] <didrocks> davmor2: fantabulous!
[15:50] <ogra_> sergiusens, i think my install even predates that
[16:02] <sil2100> didrocks: did you publish robru's libusermetrics?
[16:03] <didrocks> sil2100: no, I'm waiting for popey +1 on the dogfooding for #141 first
[16:03] <sil2100> didrocks: ok ;)
[16:03] <Mirv> didrocks: ok won't join the hangout now since I just finished mumble and started 11h ago plus we've another hangout in an hour :S
[16:04] <didrocks> Mirv: ok ;)
[16:04] <didrocks> no worry, no new question on the system?
[16:04] <sil2100> xnox: phew, wanted to poke you about the direct autopilot upload-without-changelog-syncing-in-bzr but I see you synced it up now, thanks :) !
[16:04] <xnox> sil2100: yeah, sorry for the delay.
[16:05] <sil2100> xnox: as long as it's in, it's all cool!
[16:08] <Mirv> not yet, about the system, need to use it first
[16:17] <ogra_> xnox, oh, btw, the dependency change you did for autopilot-touch before going on vacation adds 10MB to the zip (~30MB uncompressed) ... next time pmcgowan hunts me down about image size dont be surprised if i forward him to you :P
[16:17] <popey> didrocks: been afk, back and testing now
[16:17] <didrocks> popey: thanks!
[16:18] <ogra_> (effectively we need to unseed all that autopilot stuff in the long term)
[16:18] <pmcgowan> ogra_, yeah seems temporary for good reason
[16:18] <ogra_> should become unconfined click packages or so
[16:18] <xnox> ogra_: excellent! and I'll pass on the batton, to get all of barrys port to python3 branches merged for all autopackage tests. ASAP!
[16:18] <xnox> =)
[16:19] <xnox> drop all of python2 off the image, and regain all the space back.
[16:19] <ogra_> heh
[16:19] <ogra_> well, i would like to drop all of autopilot :)
[16:19] <ogra_> that really shouldnt be in production images
[16:20] <ogra_> but we need a working concept for still being able to test without making the image rw (like unconfined click autopilot packages etc)
[16:20] <xnox> yeah.
[16:21] <xnox> we could push pre-fetched packages and run them from home folder, whilst keeping the image RO.
[16:21] <ogra_> sounds a bit hackish, but yeah, that might work
[16:22] <xnox> we'd need to set LD_PRELOAD path however, which i'm not sure we'd be able to do without disabling more bits of apparmor.
[16:23] <ogra_> or use something like a fakechroot container or so
[16:23] <ogra_> hmm, though we are able to be root ... could just be an actual chroot or container
[16:25] <ogra_> if we only had overlayfs support ...
[16:25] <ogra_> we could build an autopilot img along with the rootfs and just mount the overlay to have everything available
[16:26] <popey> didrocks: 141 is good
[16:26] <didrocks> \o/
[16:26] <didrocks> ogra_: promoting?
[16:27] <ogra_> didrocks, dont you want to wait until utah is done ?
[16:27] <ogra_> the dashboard doesnt even show half the tests yet
[16:29] <didrocks> ogra_: oh sorry, I saw it done, yeah yeah, you're right
[16:29] <didrocks> ogra_: I was on 140
[17:01]  * popey tickles didrocks 
[17:01] <didrocks> popey: in meeting
[17:01] <didrocks> sil2100: please get image 141 promoted if test results are good
[17:01] <didrocks> then publish everything we prepare
[17:01] <didrocks> and add the new requests to the list
[17:01] <didrocks> thanks!
[17:19] <robru> sil2100, time for a trivial review? https://code.launchpad.net/~robru/cupstream2distro-config/fix-friends-packages/+merge/202513
[17:20] <sil2100> robru: sure, let me take a look
[17:20] <sil2100> robru: approved!
[17:21] <sil2100> robru, cyphermox, kenvandine: just in case so that you know - cu2d is still in manual mode (all job is disabled), so if you have any releases you want to do, remember to run the builds of components before testing
[17:21] <sil2100> (if the PPA is not up-to-date)
[17:21] <robru> sil2100, ok, thanks
[17:22] <kenvandine> thx
[17:47] <sil2100> Are we there yet? (with the test results ;p)
[17:47] <dobey> Mirv: where is ubuntuone-credentials failing to build in a PPA against qt 5.2 from a recipe?
[17:51] <sil2100> Modem restart, brb
[17:57] <dobey> Mirv: your recipe is wrong and has nothing to do with native versions or split mode
[17:57] <dobey> Mirv: and why the heck are you adding an epoch to the version?!
[18:03] <dobey> to all the versions even
[18:08] <plars> ogra_: the security test results haven't shown up yet, but all tests passed on mako
[18:09] <ogra_> great ... and maguro doesnt look worse than last time i reloaded :)
[18:11] <sil2100> ogra_: ...promotion? ;)
[18:11] <ogra_> stop being pushy !
[18:11] <ogra_> :P
[18:11]  * ogra_ is on it 
[18:11] <ogra_> :)
[18:12] <plars> at this point, it's not possible for the ci results on maguro for 141 to be worse than the ones for 140
[18:13] <ogra_> yep
[18:14] <ogra_> [18:14] <ogra_> happy upgrading
[18:16] <didrocks> ogra_: \o/
[18:16] <didrocks> was about to say it :)
[18:17] <ogra_> :)
[18:21] <sil2100> \o/
[18:21] <sil2100> didrocks: I'm jumping out now to the store, but I'll publish some of my packages once back :)
[18:21] <didrocks> sil2100: great, enjoy! :)
[18:37] <ogra_> hmm
[18:37] <ogra_> if i start an app the toolbar comes up empty here
[18:38] <ogra_> (webapp)
[18:38] <ogra_> popey, ^^
[18:38] <ogra_> native seems fine
[18:40]  * popey looks
[18:40] <popey> +1
[18:43] <davmor2> ogra_: you are doing it wrong you are meant to find the faults before we promote them ;)
[18:43] <ogra_> davmor2, nah, you are :P
[18:43] <davmor2> ogra_: I'd need more time to find all the faults
[18:43]  * ogra_ was wrangling with other stuff on his dev phone today, i couldnt flash 
[18:44] <ogra_> so i didnt see 141 before it arrived on my stable phone
[18:45] <davmor2> ogra_, popey: oddly if you open the amazon app.  Click on an image so there is a page to go back to.  Pull up the hud there is a back option there the toolbar then shows a faded back button
[18:45] <ogra_> yeah
[18:45] <ogra_> i use that all the time in the G+ app
[18:45] <ogra_> since the maintainer is to lazy to add a toolbar back button :P
[18:45]  * ogra_ looks at xnox 
[18:46] <davmor2> ogra_: yeah but g+ isn't using the webapps and ubuntu mobile naming anyway
[18:47] <davmor2> ogra_: oh interesting it looks likt this might be an issue with the webapp not being a page now maybe?
[18:49] <xnox> ogra_: yeah, i haven't touched my webapps since i've uploaded them. and am not on top of latest webappy developments.
[18:50] <ogra_> davmor2, could be
[19:41] <sil2100> kenvandine: are you around for some packaging ACKs?
[19:42] <sil2100> cyphermox: or maybe you are around for some packaging ACKs?
[19:42] <cyphermox> yes of course
[19:42] <sil2100> \o/
[19:43] <sil2100> cyphermox: http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-scopes-api_0.2.0+14.04.20140120-0ubuntu1.diff and http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-scopes-shell_0.2.0+14.04.20140120-0ubuntu1.diff for starters
[19:43] <sil2100> Thank you!
[20:01] <veebers> Is there anyone available here that is able to help with any self-service CITrain issues?
[20:01] <veebers> sil2100: potentially you? ^
[20:03] <cyphermox> sil2100: I'm still looking at it, the diff is huge.
[20:16] <cyphermox> sil2100: yeah, all good.
[20:49] <sil2100> cyphermox: thanks!
[20:49] <sil2100> veebers: hmm... I'm near my EOD, and the feature is still new, but what's up?
[20:51] <veebers> sil2100: awesome cheers :-) I'm trying to do the 'Build' step with a silo that didrocks provided for me, but the jenkins job is throwing an error and I'm not sure if it's canonistack/network issues or jenkins job issue or something on my end (But, it's just an MR right?)
[20:52] <veebers> sil2100: http://162.213.35.73/job/landing-002-1-build/
[20:58] <sil2100> veebers: indeed it looks to me like a hm, network issue
[20:59] <veebers> sil2100: ok, well at least I'm not doing anything dumb :-) I'll try again later
[21:26] <sil2100> Ok, it's almost midnight here, so see you tomorrow!