[07:10] ogra_: if you are around, I can't find the lxc-android-config branch, apparently ofono does need it and as it doesn't follow our normal project/branch structure, I can't find it :/ [07:36] popey: once you are around, anyway to revert weather-app? All AP are failing (the SetUp() function is failing on an unknown method) [08:25] cihelp qa-intel-4000 encounter kernel crashes, http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000 are failing or hanging [08:26] cihelp or suceeding for wrong reasons :-/ [08:27] cihelp kernel reverted to previous version [08:32] didrocks: morning [08:32] cihelp new container created to make sure it's aligned with the reverted kernel [08:33] didrocks: well that sucks, they ran fine here [08:34] popey: it's really weird, as you can see from the traceback, it's either they can or can't run :p [08:34] popey: I don't know where the code is, can you check about that function? [08:35] to see if the system isn't using the right autopilot tests? [08:35] i can revert to previous version in the store [08:36] popey: yeah, let's try that first and then, we can understand what happens [08:37] "Changed published version to 1.0.163. [08:37] done [08:37] thanks! [08:37] popey: what's really weird is that the issue is really black or white [08:37] I really wonder if the autopilot tests are not the right one [08:37] do you have the sources handy? [08:38] yes [08:38] lp:ubuntu-weather-app [08:40] http://paste.ubuntu.com/6565596/ [08:40] (diff) - line 43 looks suspicious [08:40] popey: yeah, it's the missing function [08:40] called frmo setUp() [08:40] from* [08:41] I think the fix is just to remove that call, like in tests/test_mainview.py [08:41] but I wonder how this can work for you [08:41] and sergio [08:41] probably because our phones aren't clean? [08:41] yeah, I would like that we dig a little bit, if it was just you, it's a human error, and so ok [08:42] you and sergio at the same time… [08:42] maybe something in the click test runner isn't grabbing the right versions [08:42] well neither of us has a clean phone [08:42] yeah, but maybe we need to understand what happens so that we can add safety guard in the test runner? [08:42] to tell "ohoh, you're not testing with the right things" [08:43] Mirv: I need a new run of say head/qa on q-jenkins to test the reverted kernel/new container is it just clicking Build on http://q-jenkins.ubuntu-ci:8080/job/cu2d-qa-head/ or will I screw something ? [08:47] didrocks: ^ [08:47] vila: you can do that, yeah [08:47] default parameters, don't change anything [08:47] vila: just that, with defaults [08:48] done [08:48] brace yourselves [08:49] cihelp: I think that the daily-build ppa is declaring building on ppc64el when it's not [08:49] I think cjwatson can confirm [08:50] so, it's dep-waiting forever or something that won't build === Ursinha-afk is now known as Ursinha [08:58] didrocks: does that block my head-qa test ? [08:58] vila: it will [08:59] well, the build job will be blocked forever [08:59] unless you skip the arch [08:59] oh, it blocks the current friends-head but will *also* block qa-head, urgh [08:59] didrocks: ^ correct ? [09:00] vila: shouldn't [09:00] didrocks: I'm reviewing and landing the ofono change atm [09:00] rsalveti: thanks, I'll kick an image once ofono is in [09:00] * didrocks publishes the missing qmenumodel now [09:01] didrocks: shouldn't what ? [09:01] vila: shouldn't block [09:20] cihelp, didrocks, Mirv: http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/943/ succeeded [09:21] vila: yeah, but the build job is blocked, right? [09:23] huh, ppc64el - something I didn't see before [09:24] didrocks: I don't see ppc64el building in our PPA, so should I skip the arch for autopilot in QA? [09:24] sil2100: please kill the build job, I think vila isn't responsding [09:24] sil2100: I have the fix for it, but *shrugh* for ppas lying [09:25] Ok, so just killing, right... another workaround for PPA lies [09:25] yeah… [09:25] didrocks: huh, what ? [09:25] sil2100: we were waiting for you yesterday [09:25] vila: 10:21:32 didrocks | vila: yeah, but the build job is blocked, right? [09:26] didrocks: can't see that but maybe sil2100 already killed it ? [09:26] vila: I'll need you to deploy the latest cu2d [09:27] it contains the ignore that arch [09:27] didrocks: you got a job for that no ? [09:27] hum, really? I don't remember the reference, do you have it? [09:27] didrocks: and you still need to sync with your cu2d jobs ? [09:27] vila: not sure what you mean [09:28] didrocks: sorry about that, I guess my Thursdays are really unlucky for evening meetings since the last weeks, been missing on that one frequently, always on the same day ;/ [09:28] vila: I need something pulling latest lp:cupstream2distro [09:28] sil2100: can you warn us in advance please? [09:28] didrocks: fginther create a job for that, not sure if it that has landed but you commented on the MP no ? [09:28] s/create/created/ [09:29] vila: no, this is to deploy stacks [09:29] vila: I'm asking for deploying latest cu2d code [09:30] thanks rsalveti, let's hope a quick migration to the release pocket :) [09:30] didrocks: right, still building for armhf [09:31] ok [09:31] but yeah, should take ~20 min at least :-) [09:31] didrocks: hai! [09:31] asac: didn't you want to join? [09:31] * sil2100 wonders why he has to re-enter all the google credentials everytime now [09:33] didrocks: i am in === ev changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: ev | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [10:01] didrocks, apt-get source ;) ... or use UDD ... [10:01] ogra_: no worry, I found it that they were no real branch :) [10:01] it is a real branch ... several even ;) on my disk [10:01] ahah ;) [10:01] and I got the code from Tony [10:02] so all good [10:02] yeah, that was a trivial change [10:02] i was pinged about it on my last day === mhr3_ is now known as mhr3 [11:00] didrocks: Huh? ppc64el isn't in Launchpad yet (in any meaningful way). I find it very doubtful that a PPA could possibly be doing anything with it ... [11:00] didrocks: URL? [11:01] cjwatson: https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-2.1build/588/console [11:01] see the 2013-12-13 07:43:12,338 INFO arch: ppc64el, status: building [11:02] cjwatson: this is coming from series.architectures [11:02] series coming from get_ubuntu().getSeries(name_or_version="trusty") [11:02] get_ubuntu() is the ubuntu launchpadlib object [11:03] morning all [11:03] hey davmor2 [11:06] didrocks: I'm so happy that awe could reconstitute the crash into something useful :D [11:06] yep ;) [11:06] * didrocks is waiting for ofono to transitio to kick an image build [11:07] didrocks: I added a landing ask. do I need to find someone to action it or can you? [11:10] popey: no, that's fine, I'm just going to assign it [11:10] thanks! [11:10] sweet! thanks. [11:12] yw [11:12] didrocks: hmm, I guess it got flipped to enabled recently in trusty. but shouldn't you be intersecting this with the set of architectures that your PPA can actually build in any case? [11:12] didrocks: you can get that from the "enabled_restricted_processors" attribute on your archive [11:12] which doesn't have ppc64el enabled [11:12] cjwatson: oh, I didn't know that parameter [11:13] cjwatson: ok, I'll interest with that one, I was doing the intersection manually between virtualized and not virtualized [11:13] thanks [11:13] that's *restricted* processors, note - i386 and amd64 get added regardless [11:13] ok, but making sense [11:13] wonder if that's doable without hardcoding [11:14] well, using that parameter from my side will be already a big help :) [11:18] grumble, you can only get at it in an annoying way right now [11:18] didrocks: http://paste.ubuntu.com/6566175/ [11:18] err sorry for unhelpful lack of line-wrapping there [11:19] LP has a link from DAS to Processor, it just isn't exported [11:21] cjwatson: ah, so using that list + the enabled_retristed_preprocessors collection, that should do it, yeah. Thanks for the hint! [11:22] didrocks: https://bugs.launchpad.net/launchpad/+bug/1260695 [11:22] Ubuntu bug 1260695 in Launchpad itself "export link from DistroArchSeries to Processor" [Low,Triaged] [11:22] * didrocks subscribes [11:38] popey, didrocks: I get this from time to time but it is impossible to replicate http://ubuntuone.com/2eWjzdTlxxtVG4eL03pmWY notice that the i key is on top of the q key, if you press the empty space you get an i but it doesn't look pretty [11:39] * popey waits for the picture to load like it's 1998 [11:39] popey: still [11:40] ooh thats interesting [11:40] not seen that before [11:40] popey: ah, you had this feeling too! [11:40] yeah, same, never [11:40] davmor2: I think it's not a new regression, I see nothing that came in that can impact that [11:40] if you hide the keyboard [11:40] and show it again [11:41] is it "fixed"? [11:41] (you should have an azerty keyboard, we never have those bugs :p) [11:42] popey: davmor2: just started to build image #64. I hope it will be THE one [11:42] I'll tell you once published, please prepare to dogfood that one [11:42] ooh, 64, a nice round number [11:42] didrocks: no but if you close the app and a fresh maliit is called it is fixed then [11:42] popey: isn't it! it was all planned! [11:42] :D [11:42] davmor2: interesting [11:42] didrocks: it's been around for a while but no easy way to reproduce it [11:42] yeah [11:42] :/ [11:43] maybe file a bug and talk to the keyboard team? [11:43] didrocks: before it happened maliit I think crashed so I'll look into that [11:43] ok ;) [11:46] popey: in /var/crash do you see _usr_lib_arm-linux-gnueabihf_upstart-app-launch_desktop-hook..crash ? [11:46] yes [11:46] -rw-rw-r-- 1 phablet whoopsie 10K Dec 12 20:34 _usr_lib_arm-linux-gnueabihf_upstart-app-launch_desktop-hook.32011.crash [11:47] didrocks: ^ not sure how important that is :) [11:47] I think this was the click apps regression? [11:48] didrocks: but I did a fresh install of the "Fixed click apps" version and this happened today on R62 for me iirc [11:49] davmor2: ah, please retrace it then [11:49] we'll see how often it is and if that should be a blocker [12:02] didrocks: oh interesting looks like notes triggered it but I haven't opened notes :\ [12:03] davmor2: waow, that's some kind of magic, can you ensure it's not on other click apps as well? [12:04] davmor2: how did you determine what triggered it? [12:05] popey: viewed the crash report ala https://lists.launchpad.net/ubuntu-phone/msg04549.html was about to start the retrace on it if I can figure out what dbgsym I need [12:07] mine was a community app which barfed [12:07] none of ours. [12:08] s/community/3rd party/ (as in, an app from the store, not a core app) [12:08] uhhh [12:08] I just updated my phone and it pulled down #63 [12:09] and when I hit "Install and restart" it showed a message briefly that it can't contact service, but then went ahead and restarted anyway [12:09] bit worrying [12:09] i would have got a screenshot but it was too quick [12:09] popey: urgh, can you check you have image #63 then? [12:09] and not #62? [12:09] will do when it comes back [12:09] current build number: 63 [12:09] can really be system-image 2.0 [12:09] ok [12:09] so it's a false warning :p [12:09] sounds plausible [12:09] just alarming! [12:10] I'll look between image 63 and 64 [12:10] popey: mind filing a bug? [12:10] system-image, barry… [12:12] popey: I saw that, but didn't have enough time to see if it was a warning or if it said phone rebooting now, so I'm happy to confirm it :) [12:12] ok [12:14] popey: did it start with "Apply update failed:" [12:14] yes i think so [12:14] then cannot connect to service or something [12:14] Apply update failed: Can't apply the current update (can't contact service)" [12:14] yes [12:15] from my *excellent* frontend code, that means that the backend doesn't send anymore "ack" reply [12:15] didrocks: should apport-cli crash_file.crash and s for send actually work all the docs say it should but it isn't. [12:15] davmor2: where does it say it works on touch? [12:15] davmor2: from what I know, it doesn't [12:15] davmor2: that's why we retrace that locally [12:16] didrocks: https://lists.launchpad.net/ubuntu-phone/msg04549.html unless I'm reading it wrong [12:17] davmor2: you do that on the retraced crash, right? [12:17] davmor2: bug 1260712 [12:18] bug 1260712 in system-image (Ubuntu) "Apply update failed: Can't apply the current update (can't contact service)"" [Undecided,New] https://launchpad.net/bugs/1260712 [12:18] davmor2: the one you used apport-retrace -S on? [12:18] didrocks: I will be once I get everything on to run the trace yes [12:19] davmor2: so, you need to send that report [12:19] not the one before [12:19] and yeah, that should work (so, on your computer) [12:20] didrocks: right so I do the retrace on the phone then transfer to the computer and then send from the computer, it should say that in the email grrrrrrr :) [12:20] thanks for the info :) [12:24] davmor2: no worry! [12:24] be ready, I guess next image isn't far! [12:26] ev: did you deploy successfully latest cu2d? [12:27] didrocks: I handed it off to vila, since you and I had that call with Alex. So yes, he deployed it. [12:28] ah, excellent! [12:28] thanks [12:28] * ev lunches [12:34] didrocks: so after all that setting up ERROR: report file does not contain one of the required fields: CoreDump DistroRelease Package ExecutablePath for this I blame ev bound to be his fault :D [12:39] didrocks: ... and now I discover the #webops scrollback with the initialisation of ppc64el last night, so that explains that :-) [12:39] (no builders yet, which is what I checked first) [12:40] cjwatson: ok, at least, with the properties you pointed me at, I'll be able to avoid being impacted by it in the future :) [12:41] popey: I don't see the revert in image 64 of weather: http://people.canonical.com/~ogra/touch-image-stats/20131213.1.changes [12:41] excepted, will we have the correct version? [12:44] ☹ [12:45] bug 1257048 still happens for me [12:45] bug 1257048 in unity-mir (Ubuntu) "Screen doesn't auto-blank with mako during first boot (since #43)" [Undecided,New] https://launchpad.net/bugs/1257048 [12:45] just updated to #63 and the phone is sat there with the display on [12:46] popey: yeah, this is expected [12:54] popey: how can we check the click package version installed (once image diff for image 64 will be generated) [12:54] good question! [12:55] alan@deep-thought:~$ adb shell ls -ld /usr/share/click/preinstalled/com.ubuntu.weather/current [12:55] lrwxrwxrwx 1 root root 7 Dec 13 12:08 /usr/share/click/preinstalled/com.ubuntu.weather/current -> 1.0.164 [12:56] there you go [12:56] thats the pre-installed one [12:56] (on my #63) [12:56] http://people.canonical.com/~ogra/touch-image-stats/20131213.changes [12:56] it was updated in the nightly build [12:58] popey: click list [12:59] cjwatson: wont that also show the ones that I have installed which override pre-installed? [12:59] (which we don't want) [12:59] popey: ok, let's cross fingers that it's just not shown in the diff [13:00] granted. if you wanted to overachieve here then you could use click list --all --manifest and filter by the _directory attribute [13:00] popey: we'll know soon, upgrading! === alan_g is now known as alan_g|lunch [13:02] got the apply updated failed again [13:03] got a screengrab this time ☻ [13:03] http://popey.com/~alan/phablet/device-2013-12-13-130247.png [13:03] popey: I fixed it locally [13:03] I'm going to cowboy it to distro [13:03] com.ubuntu.weather1.0.163 [13:03] \o/ [13:03] popey: ^ [13:03] that's what click list tells me [13:03] BOOM! [13:03] * didrocks checks "one pb less" [13:04] popey: tell me if you confirm :) [13:04] lrwxrwxrwx 1 root root 7 Dec 13 13:03 /usr/share/click/preinstalled/com.ubuntu.weather/current -> 1.0.163 [13:04] confirmed [13:04] \o/ [13:04] I think this calls for pompoms [13:04] ok, I'll update the ApplyUpdate() fix [13:04] *\o/* [13:04] \o/\o/\o/\o/ [13:04] * popey lunches [13:04] enjoy :) [13:05] didrocks, fyi, http://people.canonical.com/~ubuntu-archive/click_packages/click_list is the list live-build pulls from [13:06] ogra_: so, you should reflect from 1.0.164 -> 1.0.163 in your diff, right? [13:06] http://people.canonical.com/~ogra/touch-image-stats/20131213.1.changes [13:07] hmm, i use dpkg --compare-versions ... [13:07] the way thats used doesnt currently honor the concept of going backwards in version numbers ... [13:07] ah, indeed ;) [13:08] (since thats usually impossible) [13:10] ogra_: aren't you on holiday already ;) === josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [13:10] davmor2, yeah, do you see me in any work channels ? ;) [13:10] ogra_: yes here :P [13:10] heh [13:11] ogra_: let me guess you're just trying you the irc client you wrote for the phone in your spare time right ? [13:11] lol [13:11] nope [13:11] i cracked my back on my first vacation day ... took the week to recover and did absolutely nothing ... (some book reading etc) [13:12] ogra_: hahaha one way to stop you working I suppose :D [13:12] heh, yeah [13:12] ogra_: A little drastic though [13:13] well, it showed me i need to move more in my work time ... [13:14] ogra_: I got a cheapo step counter if I do less than 4000 I go for a walk around the block till it's over, 4000 isn't a lot but everyday means that I'm moving twice as much as I was :) [13:14] sounds like an idea [13:16] davmor2: can you test GSM on image #64? [13:17] didrocks: I will be, I'm doing a fresh install to lose the modifications I made [13:17] exit [13:18] meh [13:18] damn focus doesn't follow mouse [13:18] vila: no it hasn't for a while I'm surprised you only just noticed ;) [13:19] davmor2: hehe, I know, I stopped using it long ago, but sometimes, I just regret it ;) [13:19] * popey returns [13:19] * popey tests 64 [13:20] * davmor2 now has "It's the return of the pope" in my head Mark Morrison remix :D [13:21] ogra_: also get a decent chair that has a back support in, those 2 combined have meant I've started to losee weight and my back isn't hurting as much :) [13:24] popey: davmor2: just a warning: we won't promote 64 due to barry's bug I guess, I uploaded a fix, but better to have most of the tests done, as this is orthogonal [13:25] camera is broken here [13:25] http://popey.com/~alan/phablet/device-2013-12-13-132507.png [13:25] pfft, closed and re-launched and now it works [13:25] mines still flashing I'll check mine when it is done [13:26] i am also copying music over mtp to it so it's a touch sluggish [13:26] which may contribute to the issue [13:30] https://www.youtube.com/watch?v=ozoTzkCeO-A is now my go-to video for testing video playback on the phone [13:30] so terrible it's great === psivaa_ is now known as psivaa [13:33] popey: it should be http://www.youtube.com/watch?v=ykwqXuMPsoc :D [13:33] i know what that is without clicking [13:33] ☻ [13:33] popey: Narhwals, Narhwals...... [13:39] didrocks: found a bug, fresh flash the screen starts blank, so when you hit the power button, to turn it on you actually switch it to stand by so it looks like you have to hit the power button twice to get the screen up woohoo \o/ [13:40] didrocks: on a plus side 3g is working next sms [13:40] davmor2: is that a reliably failure you didn't get in latest promoted image? [13:40] from what popey posted before, it was already there, right? [13:43] didrocks: quite possibly, I think some bugs have been there for a while, but when you were busy testing core functionality you blank the minor issues, till you are looking at everything :) [13:45] didrocks: sms is working [13:45] great ;) [13:46] popey: did you write a bug for the double tap to start the phone after a fresh install? [13:46] psivaa: what happened on 63? lots of regressions? [13:47] popey, didrocks: can you hit the power button to put the phone into sleep then ring it and see if you get a ring tone? [13:47] didrocks, davmor2: I didn't read all backscroll, but bug #1260079 is a use after free bug [13:47] bug 1260079 in Upstart Application Launcher "upstart-app-launch does not set (at least) TMPDIR correctly" [Critical,In progress] https://launchpad.net/bugs/1260079 [13:47] jdstrand: sorry, I don't get the "is a use after free bug" [13:48] didrocks: g_free(package); [13:48] ah ;) [13:48] didrocks: tmpdir = ... ("%s/confined/%s", ..., package); [13:48] jdstrand: was it already on latest promoted image? (I try to see promotion blockers) [13:49] didrocks: it is in 60 and 62 for sure [13:49] jdstrand: can you try on 58? [13:49] * didrocks looks at uploads meanwhile [13:49] didrocks: I'm actually off today and have to head out to an appt, but I'm sure ted can :) [13:50] jdstrand: the bug is due to latest upstart-app-launch? [13:50] didrocks: not ubuntu3 [13:50] davmor2: double tap? [13:50] davmor2: I get a ring if i suspend phone and ring it [13:51] jdstrand: yeah, so, it's already in latest promoted image, I'll just add to the list of things to get fixed [13:51] plars: weather app failures [13:51] jdstrand: thanks! [13:51] np [13:52] psivaa: yeah, I see - doesn't look like we can expect them fixed in 64 either [13:52] davmor2: popey: so, I don't have on mako the issue of blank screen on image #58 [13:53] * didrocks upgrades to 64 and reboot [13:54] odd. [13:56] can be unity8 maybe [13:56] * didrocks is waiting for the upgrade to finish [13:58] ok, rebooting… [13:59] ok, not the case anymore [13:59] * didrocks puts that in the "random" box === alan_g|lunch is now known as alan_g [14:05] didrocks: it was introduced in 0.2+14.04.20131119-0ubuntu1 which appears to have been in the archive on Nov 26 [14:05] * jdstrand really gone [14:06] jdstrand: you sould really go ;) so yeah, already in the proposed image [14:06] jdstrand: thanks for digging! [14:19] morning [14:22] morning [14:27] * asac worries about the time it takes for system-image to become a Valid Candidate in proposed [14:28] didrocks: webbrowser doesnt look better :/ [14:28] * asac hopes its flaki [14:28] http://ci.ubuntu.com/smokeng/trusty/touch/mako/64:20131213.1:20131211.2/5444/webbrowser-app-autopilot/ [14:28] asac: I don't think we had webbrowser upload, did we? [14:29] it's the issue we discussed I guess, once the env is screwed, it's screwed [14:29] >? [14:29] didrocks: so retrying helps? [14:29] psivaa: ^^ ? [14:29] asac: well, yeah, it would, but please don't [14:29] asac: don't hide bugs [14:29] ok [14:29] we want to get them fixed [14:29] hmm [14:29] so upstream should be better armed against the env [14:29] didrocks: well, but you wanted to check if we have a regressionm [14:30] and the discussion is happening on the ML [14:30] if we previously could get it green with retrying then only retrying will confirm that we didnt sneak something in [14:30] ok [14:30] you can still have the jenkins jobs etc. [14:30] they have all the data [14:30] asac: but then, we loose the data [14:30] (just saying) [14:30] didrocks: no you dont [14:30] just record the jenkins job url [14:30] and not the dashboard [14:30] asac: well, we don't have connection [14:30] but yeah [14:30] file a bug [14:30] retry :) [14:30] asac: anyway, it's not the image we are going to publish [14:30] oh? [14:30] thought it was [14:31] then dont bother [14:31] well, don't we wait for system-image? [14:31] to be published [14:31] even though it would still be good to know if we have a timebomb :) [14:31] maybe… one day… [14:31] didrocks: we dont know about system-image..~. we should finish this image [14:31] so we are prepped [14:31] asac: maguro should tell us :) [14:31] thats very much not the same as you know [14:31] asac: for webbrowser, that shouldn't change [14:31] do whatever you would do to get this image to state where you would promote [14:31] didrocks: you never know [14:32] asac: well, you would be confortable to promote it with the error message on upgrade? [14:32] if you would promote with dashboard in this state, then thats what you should do [14:32] didrocks: you suggested that its not the biggest blocker we could have [14:32] if we do that, yeah [14:32] still its a regressionm [14:32] well, people will see it once [14:33] then, next image won't have it [14:33] as I uploaded the fix [14:33] anyway. if you dont want to consider this image a fall back [14:33] and go all in on the next its fine [14:33] didrocks: you never know what happnes in the meantime [14:33] hostname might make things explode [14:33] well, I'm starting to think that next image will be far far away… [14:33] i really think finishing this image so its in the bank [14:33] is the right thing [14:33]