[07:43] <pitti> good morning
[07:44] <pitti> cihelp: can I please have screen (or even better, byobu) on wazn?
[08:03] <pitti> cihelp: unping, jibel installeld screen for me (thanks!)
[08:48] <renato> fginther, hi
[08:48] <renato> fginther, could you help me to understand what is happening on this build: https://jenkins.qa.ubuntu.com/job/address-book-service-trusty-amd64-ci/38/console
[08:51] <renato> I do not have any idea what is causing the error,
[08:52] <renato> only if this is mixing different headers
[09:26]  * cjwatson unsticks hud from trusty-proposed, again
[10:01] <didrocks> cjwatson: sorry, I didn't follow why it was blocked the first time (just mentionned it in the call), is there anything we should change?
[10:02] <didrocks> or is it again the tests being stuck while building? (not all processes killed)
[10:03] <Laney> The previous upload built packages for more architectures than the current one
[10:05] <didrocks> ah ibgsettings-qt-dev
[10:05] <didrocks> l*
[10:05] <didrocks> and so Qt 5.2
[10:06] <didrocks> it's all Mirv's fault! :)
[10:07]  * didrocks chases dbus-cpp build-dep now
[10:08] <didrocks> sil2100: I assumed that properties-cpp was Mir, wasn't it the case?
[10:08] <didrocks> sil2100: that's why it can't see it's build-dep
[10:08] <didrocks> its*
[10:10] <cjwatson> didrocks: it was only "again" because the revert brought the previous full set of architectures back after I removed them the first time
[10:10] <cjwatson> I wasn't complaining, it was all reasonable, just mentioning
[10:10] <didrocks> cjwatson: ah ok, was confused. Yeah, I noticed it this morning that it was blocked after the freeze. Thanks for looking at that! :)
[10:12] <sil2100> didrocks: aaah!
[10:13] <sil2100> didrocks: ok, makes sense - there's a MIR for that, but doko asked for it to be 'pulled in' by something so he can MIR approve it
[10:13] <sil2100> didrocks: https://bugs.launchpad.net/ubuntu/+source/process-cpp/+bug/1270234
[10:13] <didrocks> sil2100: so, I guess you can ping him :)
[10:13] <sil2100> didrocks: what does it mean 'needs a team subscriber'? ;p
[10:15] <didrocks> sil2100: need a team to susbcribe to the bug reports
[10:15] <sil2100> didrocks: ah, in LP you mean?
[10:15] <didrocks> yeah, against the package
[10:19] <sil2100> didrocks: ok, this will sound really noobish, but how can I do that ;)?
[10:19] <didrocks> sil2100: go to the package LP page: https://launchpad.net/ubuntu/+source/properties-cpp
[10:20] <didrocks> click on subscribe to bug mail (in the upper right)
[10:20] <sil2100> Aaaaaaaaaa
[10:20] <didrocks> and you can subscribe bug mail recipient, (teams included)
[10:20] <didrocks> you need to have someone part of that team subscribing of course
[10:20] <sil2100> So you can actually subscribe something else than just myself?
[10:20] <sil2100> Got it, thanks!
[10:21] <Mirv> didrocks: Qt 5.2 should not yet be affecting anything unless the fixes made around the packages somehow break some archs. actually, after Qt 5.2 Qt should build on more archs because getting rid of V8 engine :)
[10:21] <didrocks> Mirv: yeah, I was just kidding telling "we need it to be able to build on all archs" :p
[10:22] <Mirv> ok :)
[10:22] <cjwatson> build on more archs> that is indeed the point
[10:22] <cjwatson> looking forward to it for the arm64 and ppc64el stats :)
[10:42] <tsdgeos> guys, is there any way i can get shell access to the machines running https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/2262/? ?
[10:42] <tsdgeos> it's failing constantly in CI but i can't reproduce neither in my desktop nor in my phone
[10:42] <tsdgeos> ev: ↑↑↑
[10:47] <ev> tsdgeos: looking into your test failure now
[11:02] <psivaa> didrocks: so rerunning the maguro tests impacted by qmlscene crash does not help. the crash is reproducible and the tests are failing again.
[11:02] <psivaa> tried twice.. running once more
[11:03] <sil2100> I jump out for some minutes to buy insurance for the trip
[11:04] <didrocks> psivaa: thanks for the head's up, seems a promotion blocker then
[11:04] <didrocks> psivaa: can you try to revert the content of the image one by one?
[11:04] <didrocks> (and then, the previous image)
[11:04] <didrocks> psivaa: weird that's it's "reliable" :/
[11:06] <sil2100> ;/
[11:07] <psivaa> didrocks: ack, will do that.
[11:08] <didrocks> psivaa: keep us posted! thanks! ;)
[11:09] <didrocks> Mirv: tell us when you got more infos/debugs from ricmm
[11:10] <Mirv> sure
[11:28] <tsdgeos> ev: is there no change i get access to the machine instead of you looking at it? It'd be probably faster if i do the research than if you do (no offense) since i know more about unity8 and it's stuff
[11:28] <tsdgeos> s/change/chance
[11:37] <renato> hey guys, could you help me with this build: https://jenkins.qa.ubuntu.com/job/address-book-service-trusty-amd64-ci/38/console
[11:37] <renato> the error is very strange, looks like jenkins is trying to use a old header .h with a new .cpp file
[11:40] <renato> looking at the build log looks like jenkins does some file copies and updates, what I guess is that the header file has moved in the new version but jenkis did not notice that and now I have 2 headers
[11:44] <renato> '
[11:44] <ev> tsdgeos: no, I really do not want to start handing out access to these machines. I'd much rather we solve the underlying problem of there being inconsistencies between what you're seeing on your local machine and what we're seeing in the CI infrastructure.
[11:44] <renato> renato
[11:44] <renato> alo123ola
[11:44] <tsdgeos> ev: ok
[11:44] <renato> sudo reboot
[11:44] <ev> It should be dead-simple to reproduce the same environment.
[11:44] <tsdgeos> renato: that looks bad :D
[11:44] <renato> alo123ola
[11:45] <tsdgeos> ev: yes, should is always the magic keyword :-)
[11:45] <ev> :)
[11:46] <renato> tsdgeos, hi
[11:47] <tsdgeos> renato: i think we saw your password or something
[11:47] <renato> :D
[11:48] <renato> yeah, my machine freezes :D, I changed that already
[11:50] <tsdgeos> oki
[12:14] <didrocks> psivaa: any luck yet?
[12:15] <psivaa> didrocks: not yet. i remember we had qmlscene crash with 143 as well so going thorough http://people.canonical.com/~ogra/touch-image-stats/20140122.1.changes as well
[12:16] <didrocks> psivaa: yeah, but it' wasn't 100% of the time like that one
[12:16] <didrocks> davmor2: hey, meanwhile, can you dogfood latest of latest? :)
[12:17] <psivaa> didrocks: yea, just to make sure if any combination of this list in 20140122.1 and those in 20140123.1 is causing it
[12:18] <didrocks> ok ;)
[12:20] <davmor2> didrocks: sure
[12:20] <didrocks> thanks!
[12:47] <davmor2> seb128: on the bluetooth setting page if you turn blutooth off should you see the spinner for searching still?
[12:47] <seb128> davmor2, I guess not
[12:48] <davmor2> seb128: I'm assuming it isn't searching and it's just the spinner spinning for no reason just looks odd
[12:49] <seb128> davmor2, seems like  a bug, please open one ;-)
[12:49] <davmor2> seb128: certainly I'll do it at the end of the testing :)
[12:51] <didrocks> psivaa: seems this time was better on the dashboard?
[12:52] <psivaa> didrocks: the failures have gone down but the crash still occurred
[12:52] <didrocks> psivaa: hum, interesting…
[12:52] <psivaa> didrocks: yea, quite confusing as to what's causing this crash..
[12:53] <tsdgeos> ev: so did you have any luck finding out what is wrong?
[12:53] <didrocks> psivaa: maybe, we just got lucky yesterday?
[12:53] <didrocks> psivaa: try upgrading everything again, and run, BUT with fingers crossed? :p
[12:53] <ev> tsdgeos: no, it's taking forever and a day to bootstrap my environment
[12:53] <didrocks> psivaa: to see if it's really 100% or if crossing fingers influence ;)
[12:53] <ev> I'm going to have to hand this off to the next vanguard as I'm coming up on the end of my shift
[12:54] <psivaa> didrocks: :), quite possibly
[12:54] <ev> tracking it here https://app.asana.com/0/8736198969650/9782553540311
[12:54] <tsdgeos> oki
[12:56] <tsdgeos> ev: how do i login there, with my canonical sso?
[12:56] <ev> oops, need to add you as a follower on the task
[12:56] <ev> but yes, canonical sso
[12:58] <ev> should work now
[12:59] <tsdgeos> tx
[13:01] <davmor2> seb128: feel free to unsub yourself but you seem the obvious target for system settings :) https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1272317
[13:02] <seb128> davmor2, I'm subscribed to the package so I get the new bugs anyway, not need to subscribe me, but thanks
[13:03] <davmor2> seb128: assign no subscribe sorry wrong term
[13:04] <seb128> davmor2, oh ok, it's one for charles (he wrote the bluetooth panel), I'm got to reassign, no worry
[13:05] <davmor2> seb128: thanks
[13:10] <davmor2> didrocks: 146 is looking pretty stable here looks like popey is seeing the same
[13:10] <popey> +1
[13:12] <davmor2> popey: have a look at you national rail app and see if you can set a date for travel :)
[13:13] <popey> k
[13:15] <popey> works for me
[13:16] <davmor2> popey: last night I wanted to check times and prices for the trip down I had a floating list view of numbers
[13:16] <popey> screenshot?
[13:16] <davmor2> popey: I'll grab one in a second
[13:18] <didrocks> popey: davmor2: great! thanks guys :)
[13:19] <didrocks> psivaa: it's on you now, to know if we can promote (like the crash magically disappeared and we were just unlucky) or really reliable
[13:19] <davmor2> popey: oh so now the date works but doesn't change unless you change another bit
[13:19] <psivaa> didrocks: ack, give me about 30-45 mins..?
[13:20] <didrocks> psivaa: perfect :)
[13:37] <didrocks> ricmm: hey, did you get any luck looking at psivaa's stacktrace on qtubuntu?
[13:37] <davmor2> popey: slowly the script gets more refined, now errors out nicely when there is no device attached :)
[13:37] <didrocks> (qmlscene crash)
[13:37] <popey> davmor2: make it work with more than one device attached ☻
[13:37] <popey> e.g. two phones or one phone and the emulator
[13:38] <davmor2> popey: it's probably possible but I doubt my head can handle it :)
[13:38] <popey> davmor2: ping me the link to the code I'll look
[13:39] <davmor2> popey: https://code.launchpad.net/~davmor2/+junk/is_there_an_update  nice and simple
[13:40] <popey> kk
[13:43] <Mirv> didrocks: status update with bug #1271879 is that we replied to ricmm about that yes it's multiple apps and on maguro, no further updates at the moment
[13:43] <didrocks> Mirv: ok, thanks, let's see once ricmm is freed
[14:04] <psivaa> didrocks: qmlscene the crash keeps occurring, no luck with reverting packages. Since the crash has been occurring even before 144, i dont see why we should not promote 146
[14:05] <didrocks> psivaa: well, it wasn't happening everytime in previous images
[14:05] <didrocks> now, it does
[14:05] <didrocks> ricmm_: this is blocking promotion FYI
[14:16] <fginther> morning
[14:18] <sil2100> didrocks: a batch of packaging ACK's required o/
[14:22] <sil2100> didrocks: http://paste.ubuntu.com/6808577/ :)
[14:25] <sil2100> ogra_: maybe you have a momento for some packaging ACKs? These all seem to be related to the introduction of unity-control-center
[14:25] <sil2100> ogra_: I prepared for non-VPN access
[14:25] <sil2100> ogra_:
[14:25] <sil2100> ogra_: http://paste.ubuntu.com/6808584/
[14:27] <didrocks> sil2100: +1 for all
[14:36] <ricmm_> psivaa: what apps does it happen with
[14:36] <ricmm_> all? or just that one
[14:36] <psivaa> ricmm_: calendar and clock apps easily reproducible on maguro
[14:36] <ricmm_> can you reproduce on mako?
[14:37] <davmor2> psivaa: balloons was looking at calendar yesterday with some testing help from me I think he got the issue mostly resolved then tried to tweak it and broke it again :(
[14:38] <davmor2> ricmm_: ^
[14:39] <psivaa> davmor2: but it does not explain the crash during clock app tests
[14:39] <psivaa> ricmm_: no, the crash has not occurred on mako
[14:40] <davmor2> psivaa: ah sorry are you talking crashes not tests fails sorry
[14:40] <psivaa> davmor2: np :)
[14:41] <psivaa> ricmm_: the qmlscene crash that we see now has never occurred on mako iirc
[14:41] <ricmm_> but it doesnt happen every single time, right?
[14:42] <balloons> psivaa, clock is crashing on maguro?
[14:42] <ricmm_> tedg: did we (you/gerry) ever resolve that timing issue with upstart signals and the shell's authroization or processes?
[14:42] <ricmm_> tedg: sounds like it could be it ^
[14:42] <psivaa> ricmm_: with 146 almost every calendar and clock AP tests
[14:42] <psivaa> balloons: it's not clock but qmlscene crashes during clock AP tests
[14:42] <psivaa> and calendar
[14:43] <tedg> ricmm_, Yeah, we created two events.  We block on Unity replying before starting the app.
[14:43] <tedg> It does have a timeout of 2 seconds.
[14:43] <tedg> Perhaps that timeout is getting hit on the emulator.
[14:43] <ricmm_> its maguro thats crashing
[14:43] <tedg> (seems like a long time though)
[14:44] <tedg> Hmm, probably not timing out.
[14:44] <tedg> Is there anything in the application log?
[14:44] <davmor2> psivaa: I think this might be the issue I saw. Due to the low memory on the maguro if you close an app and the memory level is not fully released and you reopen the app it locks up and your screen goes grey but the app never fully opens.
[14:45] <ricmm_> why are we testing maguro
[14:45] <ricmm_> if asac deemed it EOL'd
[14:45] <ricmm_> side question :)
[14:46] <asac> ricmm: because we didnt move over yet
[14:46] <asac> until its dead its alive :)
[14:46] <psivaa> davmor2: probably. any sign of crash files in there when that occurs?
[14:46] <ricmm> asac: understood
[14:47] <davmor2> psivaa: only really in the apps log no really crash report.  I've not had it recently though.
[14:47] <asac> ricmm: once the emulator is ready we do the 4.4. migrate
[14:47] <asac> i hope noone thinks we go earlier to 4.4
[14:47] <asac> at leaast not without discussing
[14:48]  * asac hopes for next week
[14:48] <davmor2> psivaa: if you have a look at the log for calendar it tells you if it failed to open the app let me dig out the bug it had all the logs I could get in place
[14:49] <davmor2> psivaa: https://bugs.launchpad.net/unity8/+bug/1268693
[14:51] <didrocks> davmor2: here the qmlscene is crashing on every try, so it's not random anymore
[14:52] <ricmm> im charging a maguro
[14:52] <didrocks> thanks ricmm
[14:53] <davmor2> didrocks: was less frequent when I reported it though :)  Let me grab htop and run the calendar tests and see what happens
[14:53] <didrocks> davmor2: great!
[14:57] <balloons> davmor2, I guess I'll try my heand again at calendar before you EOD
[14:57] <balloons> I'll let you know
[14:58] <psivaa> didrocks: i've rerun those tests after reverting all the packages that changed between 144 and 146 and still it's the crashes occur with the same freq btw. so we should have been lucky with 144 i guess
[14:58] <davmor2> balloons: cool I'm here till 20:00 UTC
[14:58] <didrocks> psivaa: yeah, really weird, can you try to reinstall directly 144 and rerun?
[14:59] <psivaa> didrocks: ack, will try. (dint think of that :))
[14:59] <didrocks> psivaa: let's see, as rw + revert != flashed image
[14:59] <didrocks> thanks psivaa, keep going :)
[15:07] <ricmm> didrocks: alright so which app is easiest to crash
[15:07] <ricmm> clock? or calendar
[15:15] <ricmm> psivaa: davmor2
[15:16] <davmor2> ricmm: I had issues running tests on calendar
[15:16] <psivaa> ohh ricmm any of the two would do to repro the crash
[15:17] <ricmm> and you were able to reproducing by running qmlscene manually from terminal?
[15:18] <psivaa> ricmm: no, i've been running the AP tests
[15:49] <davmor2> ricmm, psivaa, didrocks: I have the grey screen, I have the _usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash and the memory look like it was climbing whoever the shutdown and startup of the app was making unity8 (I'm assuming mir) leap to the top of the htop and was maxing out the cpu cores. So still looks like a mir/gfx memory/memory/cpu issue which is possibly why we don't see it on mako
[15:49] <davmor2> it took 3 runs for me to grey the screen and get the crash
[15:50] <ricmm> I dont know what you mean by grey scren
[15:50] <ricmm> screen
[15:50] <davmor2> ricmm: https://bugs.launchpad.net/unity8/+bug/1268693 like in the image in here
[15:51] <davmor2> ricmm: the app holder opens but the app itself doesn't
[15:51] <ricmm> oh that
[15:51] <ricmm> yea thats a shell component, nothing solid or to do with mir
[15:51] <ricmm> just the app when it first fails to start, that stays up there
[15:51] <ricmm> because unity/upstart get out of sync on whats currently running
[15:54] <psivaa> davmor2: that sounds like the crash that we see
[16:16] <bfiller> fginther: seems like some CI problems, can you check: https://code.launchpad.net/~bfiller/address-book-app/disable-predictive-text/+merge/202776
[16:16] <psivaa> didrocks: davmor2: ricmm: so i have run clock app test on a maguro with 144 thrice and was able to reproduce the crash each time
[16:17] <fginther> bfiller, looking
[16:18] <fginther> bfiller, some automatic translations were added 2 days ago and it looks like the packaging wasn't updated to match
[16:19] <bfiller> fginther: oh really, shoot
[16:19] <fginther> bfiller, any idea how that is  supposed to work. Appears to be a good way to break the build
[16:20] <bfiller> fginther: no, dpm any idea what is needed for address book packaging to pick up the translations? enabling them seemed to break the build ^^^
[16:21] <dpm> bfiller, otp, will have a look as soon as I'm done. Where's the build log?
[16:22] <bfiller> dpm: thanks, https://jenkins.qa.ubuntu.com/job/address-book-app-trusty-armhf-ci/69/console
[16:23] <bfiller> fginther: sorry to bug you on this one, I should have looked at the log more closely.
[16:25] <fginther> bfiller, no worries. It's always good to keep an eye on these things for the next time it comes up
[16:48] <bfiller> dpm: think I got it, just missing this in address-book-app.install
[16:48] <bfiller> usr/share/locale/*/LC_MESSAGES/address-book-app.mo
[16:58] <dpm> bfiller, ok, I'm off the phone. Did that solve your issue, or do you still want me to look at it?
[16:58] <bfiller> dpm: solved
[16:58] <dpm> ok, cool
[17:00] <davmor2> popey, didrocks, cyphermox: just confirming I will be there Tuesday \o/ so see you all then :)
[17:00] <popey> yay
[17:02] <didrocks> ogra_: plars: coming?
[17:02] <ogra_> yep
[17:02] <didrocks> davmor2: looking forward to see you!
[17:02] <cyphermox> davmor2: cool
[17:02] <davmor2> cyphermox: anything other than the bluetooth headset you want me to bring down?
[17:02] <davmor2> I'll put it on charge Monday :)
[17:03] <plars> didrocks: yes, brt
[17:10] <cyphermox> davmor2: tbh, any bluetooth thingy is cool
[17:11] <cyphermox> I'm bringing two headsets that can do a2dp and hsp, one LE SDK device, and one BT keyboard
[17:11] <davmor2> cyphermox: bt headset/dongle/laptop/ps3 controller it is then
[17:11] <cyphermox> mmm
[17:11] <davmor2> haha
[17:11] <cyphermox> perhaps I could bring a wiimote then
[17:12] <cyphermox> not that those things are very much useful to test
[17:12] <cyphermox> but at least they prove input support works
[17:12] <didrocks> ricmm: if you get any progress, please check to release that with cyphermox/robru
[17:13] <cyphermox> the worst I guess is going to make sure we have batteries
[18:16] <robru> kenvandine, cyphermox: anybody have time for a trivial review? https://code.launchpad.net/~robru/cupstream2distro-config/friends-packages/+merge/203143
[18:18] <kenvandine> robru, done
[18:18] <robru> kenvandine, thanks
[20:52] <mterry> I have a unity8 autopilot test that is failing in jenkins but not on my device.  Is there a special setup to get a more jenkins-like environment?
[21:01] <mterry> fginther, ^ ?
[21:01] <fginther> mterry, is this a touch device?
[21:01] <mterry> fginther, mako
[21:04] <fginther> mterry, I'll send you something, give me a few minutes please
[21:04] <mterry>  fginther, sure thanks!
[21:15] <robru> ricmm, any updates on qtubuntu? ready for testing?