=== chihchun_afk is now known as chihchun === marcusto_ is now known as marcustomlinson [07:11] Sure is quiet [07:38] heh [07:39] jibel: I'm sad to say we're here again - sync-monitor has two commits from renato that were never built [07:39] sil2100: ^ [07:39] if I see it correctly, those are removal of two debug message outputting and a whitespace fix [07:41] jibel: so if http://bazaar.launchpad.net/~renatofilho/sync-monitor/sync-by-acount/revision/59 seems safe, I could rebuilt it manually and publish without additional QA being involved since nothing functional changes [07:42] heh, I can't publish UITK because of a change I submitted [07:42] Mirv: yeah that code that checks those unbuilt revisions is something I poked at a bit recently, but I double checked and indeed some commits are legitimately not built [07:45] Maybe the upstreams can revert those commits? [07:46] If they're not important [07:55] sil2100: or that, that's why I was asking jibel which we he wants it [07:55] we can also do the revert [07:55] s/we/way/ === oSoMoN_ is now known as oSoMoN [08:10] rvr, good morning, are you going to take over https://trello.com/c/yanKnskV/2388-529-ubuntu-landing-010-webbrowser-app-osomon ? [08:21] Mirv, if the 2 lines in the diff are the only changes, don't revert and push the change [08:24] jibel: ok, I'll rebuild it then and push it in (unless something else pops up) [08:24] and double-check the actual diff is as shown there [08:39] sil2100: I got OTA-7 on my retail krillin. it says "Install and reboot" but actually did "Install and shutdown". I had to power it back on myself. Seen that? [08:39] diff looks good http://paste.ubuntu.com/12875462/ [08:40] popey: my retail krillin did reboot at least this morning [08:40] hm [08:40] popey: mine did reboot [08:40] not a ig deal. just odd [08:40] thought maybe the battery died, but it's ~60% [10:33] ubuntu-qa: is anyone looking at silo 10, or do I have to wait for alesage to get online? [10:34] oSoMoN: Alan will pick it back up I believe [10:34] oSoMoN: If someone is looking at silo 10, you would see a face in its card [10:35] can I stick a ☺ on the card ? ;) [10:45] sil2100: seeing complaints that some people haven't had OTA-7 yet, is phasing complete? [10:55] popey: let me triple check, but it should have ended at night [10:55] popey: maybe those people already upgraded yesterday? [10:55] I mean, last week [10:57] popey: confirmed that both arale and krillin are 100% phased percentage, so everyone should see the update [10:57] ok, odd. [11:30] sil2100, did you reenable daily builds for rc-proposed? [11:30] sil2100, last build on arale is Oct 16th === _salem is now known as salem_ [11:51] jibel: hm, I thought I did, let me confirm [11:52] jibel: ok, it got reverted, re-enabled again [11:52] And kicked a manual build [11:52] sil2100, on a (probably) related note, see my e-mail to ubuntu-phone, did you re-enable it for krillin as well? [11:53] oSoMoN, there is no new build for krillin either [11:53] oSoMoN: now it should be properly re-enabled - and the delta you mention is normal as we had an OTA-6-based image kicked in rc-proposed [11:53] since 16th [11:53] oSoMoN: your image no 149 is a bit old, #151 was 'going back in time' to OTA-6 [11:54] Then 152 was back to future [11:54] sil2100, okay, so updating now will get me a recent image, not an old one, right? [11:54] oSoMoN, when did you receive the notification that 152 was available? [11:55] oSoMoN: yeah, recent one, although I'm building an even more recent image now [11:55] jibel, a few days ago, but I held off updating because it seemed like a big update, so I was waiting for the dust to settle [11:55] ah okay [11:55] I’ll wait for 153 that’s currently building then, I’m not in a hurry === xavigarcia is now known as xavigarcia_lunch === alan_g is now known as alan_g|lunch [12:08] boiko: I need read permissions in the click packages of silo 11 [12:09] rvr: oups, sorry, let me fix that [12:09] sil2100: popey: I haven't got any notification update for OTA7 yet in my personal krillin [12:10] rvr: hmm, all packages are set with read permissions for everybody already [12:11] Oh, chinstrap [12:11] rvr: huh? [12:11] rvr: what image are you on? [12:11] sil2100: 25 [12:11] rvr: what if you poll manually in system-settings? [12:12] sil2100: Only file manager available [12:12] hm, not good, I wonder if it's something wrong with the client and percentage handling [12:12] We need barry to help out here [12:13] rvr: I suspect the problem might also be in people receiving the notification last week already [12:13] rvr: could you reboot your phone, want to check if that helps [12:14] Rebooting [12:14] boiko: I used wget instead the browser to download the click packages, everything's fine [12:15] rvr: ah yeah, you need to authenticate [12:20] sil2100: Downloading [12:21] sil2100: I didn't get notification, but new image is available in Update settings page [12:21] rvr: you would probably get the notification after it's downloaded [12:21] Eh, we'll have to inform people to reboot their phones to get the update ;/ [12:22] Let me reboot again and wait a little bit more without installing the update [12:27] pmcgowan: hey, I have a theory that krillin users that got the last-weeks OTA-7 update notification but didn't manage to update might not get the notification without rebooting their phones [12:30] sil2100, does the phone home happen only on reboot or also when network comes up [12:31] pmcgowan: not sure, but I suppose that system-settings remembers that it got an invalid notification for image #26 and doesn't recognize the proper image #26 as appearing - rvr said that a reboot fixed it [12:32] I have network [12:32] sil2100, it would be the system image code if anything [12:32] sil2100, jibel, hi, I noticed that silo 19 was merged thanks. Do you know if it will be part of next dev image? [12:32] I could see how it would retain the state util a reboot [12:33] but the notification doesn't appear ... still waiting, maybe eventually [12:33] rvr: did it download the image already? [12:33] sil2100: I stopped it [12:33] rvr: you won't get a notification before it's downloaded [12:33] sil2100: But at least appears in the Updates page [12:34] sil2100: ?? [12:34] rvr: IIRC the update notification only appears when the image is fully downloaded [12:34] rvr, sil2100 depends on the auto download setting [12:34] if auto is off you will get it before downloading [12:34] Automatic download... using wifi [12:34] I'm in wifi [12:36] rvr, I think it wont reload it now that you stopped it [12:37] sil2100, your theory sounds plausible, we can confirm with barry [12:37] rvr: in that case it's as pmcgowan said, you won't get a notification if it doesn't download completely [12:37] sil2100, but manually checking I would expect to work [12:37] But anyway, seems like reboot helped [12:37] pmcgowan: rvr said it didn't help ;/ [12:38] renatu: sure it will part of the next image that will be build in roughly 12h [12:38] Seems like indeed something not handled too well in either system-settings or the system-image client itself [12:38] Mirv, ok thanks. I will send a e-mail to the ML [12:38] sil2100, admitedly though this case shouldnt happen [12:39] pmcgowan: true, again sorry for that [12:39] Won't happen next time === alan_g|lunch is now known as alan_g [12:40] But I'm thinking if we should maybe send out an announcement somewhere about rebooting [12:42] sil2100, you could say if someone hasnt seen a notification by now they should manually check or reboot [12:42] or maybe just reboot if manual doesnt work [12:43] Yeah, I might send out a quick one about that somewhere [12:58] rvr, when you didn't get a notification, is there anything interesting in system-settings' logs? === xavigarcia_lunch is now known as xavigarcia [13:04] sil2100, did you trigger a new build. [13:04] ? [13:04] jibel: yes [13:05] sil2100, should it be on https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/ ? [13:06] hmmm [13:06] I have no idea what's happening [13:07] jibel: I didn't check the logs [13:07] Maybe it's blocked due to the wily images being built? [13:07] Looks like cdimage just ignored building the image [13:07] I need to check the logs [13:09] jibel, rvr: let me poke cdimage again, I don't see anything in the logs [13:09] kenvandine: could you publish UITK https://ci-train.ubuntu.com/job/ubuntu-landing-055-2-publish/10/ , one new build dep just added? [13:10] Mirv, sure [13:12] kenvandine: thanks! [13:13] Mirv, np [13:17] jibel: ok, looks like it's building this time [13:17] sil2100, good, thanks [13:46] fginther, josepht I've had some trouble getting the tarmac examples to work on my instance. Can someone set aside a little time to help me out today? [13:50] balloons: we should be able to make a bit of time for you. We have a cluster of meetings in the late morning and early afternoon (EDT) [13:51] boiko: ping [13:51] rvr: pong [13:52] boiko: I have found two problems in silo 11 so far [13:52] boiko: First one, timestamps [13:52] salem_: ^ [13:52] boiko: On the messaging-app main screen, old timestamp appears after changing the timezone and restarting the app [13:53] boiko: Second one, history-daemon is started on boot [13:53] rvr: the starting on boot thing is expected, forgot to update the testplan, now it generates some cached content on boot [13:53] rvr: sorry for that [13:53] boiko: Ok [13:54] rvr, hm, the timestamp issue is tricky. I will have a look. thanks. [13:55] rvr: ok, can you just put the testing on hold while we check the timestamp issue you found? [13:55] boiko: Yup [13:57] rvr: meanwhile I will update history-service's testplan [13:57] boiko: Thanks [14:01] sil2100, I cannot publish silo 16 to stable-phone-overlay, I'm not authorized for qtmultimedia-opensource-src [14:01] abeato: I think we'll either need a core-dev or Mirv ;) [14:01] Mirv: ^ [14:02] sil2100, yep, looks like that :) [14:04] alesage, when you get online, please ping me re- silo 10, thanks! [14:10] dbarth__, hey, I thought we decided I would land mardy's facebook removal. :) [14:11] abeato: sil2100: publishing [14:12] rvr, could you maybe put a block on [435] ubuntu/landing-024 - account-polld for now? Silo 21 has this change, as well as some other goodies. /cc dbarth__ [14:13] kenvandine: can you btw also perhaps top approve https://code.launchpad.net/~timo-jyrinki/ubuntu-seeds/ubuntu-touch.wily_add_qt5-image-formats-plugins/+merge/274882 (needs core dev) so that QA can check the silo? it's not actually going to land to wily archive as such, the silo has wily + vivid for the overlay. [14:13] jgdx: Do you want it to block or to remove it? [14:13] rvr, block until we hear from dbarth__? [14:13] jgdx: Ack [14:13] rvr, thanks :) [14:13] And done ;) [14:13] Mirv, done [14:14] kenvandine: thanks again [14:19] jgdx: yes, is there still a silo conflict? [14:20] dbarth__, silo 24 vs 21 [14:21] jgdx: ah ok [14:23] jgdx: silo 24 abandonned [14:23] dbarth__, thanks [14:26] Mirv, thanks! [14:32] rvr: just verified here, the timestamp thing is just a behavior change because history-daemon is being started on boot now [14:32] rvr: so for testing, instead of rebooting and then changing the timestamp, you can change the timestamp and then reboot [14:33] rvr: in any case, I reported #1508074 to improve this behavior in the long run [14:34] rvr: so, if those were the only things you found wrong in the silo, it is good to go [14:37] boiko: Nope, I stopped testing there [14:39] boiko: The problem can be considered a regression, since the current expectation is that no reboot is needed [14:39] boiko: So, either the problem is fixed or a dialog is presented to force a reboot === chihchun is now known as chihchun_afk [14:49] trainguards, why indicator-session and unity in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-042/+packages doesn't get the proper changelog lines or bugs [14:49] MPs are [14:50] https://code.launchpad.net/~unity-team/unity/trusty-sru-7.2.6/+merge/274599 and https://code.launchpad.net/~azzar1/indicator-session/lp-1460626-trusty/+merge/261087 [14:54] robru: Hi [14:54] robru: rhuddie needs QA powers in bileto [14:54] robru: How can add him to the team? [14:54] sil2100: ^ [14:58] rvr, sil2100 I signed it off on behalf of rhuddie [14:59] popey, ^ clock approved [14:59] * popey runs up to jibel and gives him a bit wet sloppy kiss [14:59] Thanks! [14:59] jibel: Ok [14:59] jibel, thanks [15:00] popey: it's rhuddie that should get the big sloppy kiss he did the work ;) [15:00] I'll let jibel pass it on [15:24] dbarth__, jgdx there are 2 account-polld silos 21 and 24, would it be possible to merge them so we don't do the verification twice? [15:25] jibel, silo 24 is abandoned and I asked for a block on the associated card. [15:25] jibel, it can probably be deleted by now [15:33] jgdx, even better :) thanks [15:54] trainguards: could i get someone to take the branch in https://code.launchpad.net/~dobey/whoopsie-preferences/no-get-ui/+merge/275056 and tweak the version to "0.19~15.04.1" or something, to upload to landing-026 silo? [15:55] for the vivid series [15:55] rvr: well, nowadays a reboot is already required, if you follow the testplan, you reboot and then change the locale [15:55] rvr: if you had opened messaging-app already and try to change the locale, closing messaging-app and reopening won't help [15:55] boiko: The locale, no the time zone [15:56] rvr: sorry, I meant the timezone [15:56] boiko: I tested this morning in OTA6, and didn't require a reboot [15:56] rvr: try on a stock image: open messaging-app, close it, change timezone and reopen it [15:56] Restarting messaging app worked [15:57] rvr: really? it shouldn't, but let me give it a try === boiko_ is now known as boiko [16:06] rvr: nevermind, you were right, history-daemon was getting the new timezone correctly (I thought it wouldn't, but it does) [16:06] rvr: we will fix this regression [16:08] boiko: Ok, I am moving the silo to failed [16:08] rvr: thanks [16:58] josepht, what time are you thinking this afternoon? [17:00] balloons: how does 2:30 work for you? fginther: you too [17:00] balloons, fginther: that's EDT, btw [17:01] josepht, works for me [17:01] jgdx: ping === alan_g is now known as alan_g|EOD [17:09] josepht, i might not be back on time.. Might need to be 1500.. But i'll try and ping if so [17:10] rvr, pong [17:11] rvr, could you give me the whole .log? [17:12] that wakelock value is a bit random, I should've left it blank or [17:12] (not random, but for the sake of that particular test, it doesn't matter) [17:12] balloons: ack. [17:13] fginther: how about 3:00? [17:13] josepht, that works [17:14] balloons, fginther: updated invite sent for 3:00 [17:14] cihelp: can you enable auto-merger for lp:ubuntu-sdk-ide for zbenjamin / bzoltan_ ? [17:22] Mirv: thanks [17:23] rvr, I've changed the test. We don't want to test wakelock in Test 3, but rather in a new test. I've added a TODO. [17:25] jgdx: I see [17:25] jgdx: But it's also wakeupReq [17:27] jgdx: https://pastebin.canonical.com/142204/ [17:34] rvr, yeah, that too. [17:37] rvr, what we changed is how informed push-client's “poller” is of the connectivity state. So the important thing is that FM, no wifi and good wifi works as expected (no poll, no poll, poll). [17:38] I wish we could have a test case for when NetworkManager says "you're connected to the Internet", but you carrier says "to Internet-insert coin" [17:38] lol [17:39] jgdx: Then it's good [17:39] sweet [17:41] jgdx: Silo approved [17:46] Trevinho: it's because you used "trusty" instead of "UNRELEASED" in your changelog [17:46] ouch [17:46] that was the one we had, I'll fix them [17:48] robru: oh, actually unity changelog has UNRELEASED... You meant the other way around? [17:51] Trevinho: no it needs to be UNRELEASED. I don't see the problem with the unity changelog but the other one is clearly wrong with "no change rebuild" [17:51] dobey: im not sure why your asking for that. Why can't you just put that mp in the silo and build it? [17:52] robru: https://code.launchpad.net/~unity-team/unity/trusty-sru-7.2.6/+merge/274599 has UNRELEASED, but still the changelog is missing some bug links [17:52] and I'd love to avoid to do one branch for each bug packported [17:52] err, fix backported :P [17:52] robru: because it's a native manually uploaded package in the archive and not managed by the train [17:53] robru: so the build job will just fail and complain about the version being wrong in the changelog [17:54] robru: anyway, i just made lp:~dobey/whoopsie-preferences/no-get-ui-15.04 which has the changes to debian/changelog necessary to build it in vivid as a backport, if you could just bzr bd -S that one and then upload it to landing-026 PPA, that'd be awesome [17:55] or well, I could fill the changelog manually... [17:57] Trevinho: I'm not sure what's wrong with your changelog. It should be that if you touch the changelog by hand it preserves everything so I'm not sure why the one in the silo diverse from your mp at all. You'll have to fill out whatever you think is missing by hand [17:57] ok, thanks [17:58] dobey: well why not onboard it for train usage now? It'll be easier than doing manual sources every time [18:00] robru: i am not the maintainer, so i don't want to step on their toes to do that, and turn myself into sisyphus perpetually pushing boulders up hills by trying to do it [18:01] dobey: OK one sec I just need coffee [18:01] robru: sure. thanks [18:09] dobey: ok it's uploaded, you can run the build job [18:10] robru: ok, thanks much [18:14] dobey: you're welcome [18:29] josepht, thanks. And in the end, I made it on time :p [18:29] if you'd rather go early, can do [18:30] balloons: we'll wait until 3:00 if that's okay. Our meetings went long [18:30] yep === greyback__ is now known as greyback === salem_ is now known as _salem === _salem is now known as salem_ [19:14] cihelp: https://jenkins.qa.ubuntu.com/job/cu2d-choo-choo-autolanding/310/console s-jenkins is in a bad way [19:28] hi trainguards! Are packages with debugging symbols created for packages landed in the overlay? Is there somewhere to find them? [19:28] alecu: I believe they are, yes. [19:28] alecu: what package? [19:29] robru: I'm looking for these two: libmediascanner-2.0-3-dbgsym mediascanner2.0-dbgsym [19:30] alecu: I see libmediascanner-2.0-4-dbgsym in there [19:30] robru, can you top-approve that MP again? The node that job ran on went bye-bye [19:30] alecu: oh libmediascanner-2.0-3-dbgsym is there for vivid. -4 is in wily [19:31] robru: ah, I just needed to click on "View package details".... [19:31] fginther: sorry I was in a rush to get that in in time for the cron job that pulls trunk into production, thanks for looking at it though [19:31] fginther: will let you know if the next branch still has issues [19:31] robru: so, the right way is to download those packages, and manually install them, right? there's no way to add the ppa, or something, right? [19:32] alecu: what are you trying to do exactly? the overlay PPA should be enabled by default in silos (and if not, the citrain script enables it) [19:32] alecu: I mean the overlay PPA should be enabled by default in phone images. [19:34] robru: right: I've got a clean phone, just installed with OTA-7, no silos. And I'm trying to install the debug symbols for a package I want to debug [19:35] robru: so I enable rw, do an apt-get update, and then try to install the -dbgsym packages, but they are not found. [19:35] alecu: ok, if you're not working on a silo then you'll want to make the root image readable, make sure overlay PPA is enabled, then you can install that package you want. [19:35] alecu: I'm not sure why it wouldn't be found... [19:36] alecu: I guess you'll have to download the deb manually, I don't know much about this dbgsym stuff [19:36] alecu: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+files/libmediascanner-2.0-3-dbgsym_0.107%2B15.04.20150922.1-0ubuntu1_armhf.ddeb [19:37] robru: no worries, I can do that manually. Thanks anyway for helping me find it! [19:37] alecu: you're welcome [20:33] robru: about the new landing feature, does it detect --overwrites? I mean, does it use the commit id or the commit number as reference? [20:46] Trevinho: it uses the commit id ;-) === salem_ is now known as _salem [21:46] alesage, still around? [21:49] oSoMoN, yes here [21:50] alesage, so the issue that’s affecting your testing of silo 10 (webbrowser-app) on desktop has been identified, it’s https://bugs.launchpad.net/oxide/+bug/1508054 [21:50] Launchpad bug 1508054 in webbrowser-app (Ubuntu) "[desktop] Crashes on startup with wily+overlay" [Critical,Confirmed] [21:50] oSoMoN, yep, seeing that [21:51] alesage, a fix is in the works, can I suggest we don’t block on this to validate the silo. if your testing is satisfactory on a touch device, that should be good enough I think [21:51] oSoMoN, IIRC the features I'd be testing were layout features destined for the desktop proper [21:52] alesage, they can also be tested on a nexus 7 in landscape orientation, if you have one handy [21:53] oSoMoN, am I unlucky in being affected by the crash bug? or would another QE maybe miss it? [21:53] alesage, no, I think the bug should affect everyone regardless, it’s puzzling that we haven’t hit it earlier