=== michihenning is now known as michi [02:10] === IMAGE 76 building (started: 20150124-02:10) === [02:15] === IMAGE RTM 210 building (started: 20150124-02:15) === [03:30] === IMAGE 76 DONE (finished: 20150124-03:30) === [03:30] === changelog: http://people.canonical.com/~ogra/touch-image-stats/76.changes === [03:45] === IMAGE RTM 210 DONE (finished: 20150124-03:45) === [03:45] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/210.changes === [09:43] Morning all [10:11] morning davmor2 [11:11] popey, +1 to publish clock-app [11:12] nik90, ^ [11:15] thanks jibel [11:17] have pinged dpm a mail to upload when he gets a chance. Might not be till sunday night / monday morning. [11:25] cihelp: mako-06, -10 ,-11 stucked [11:26] vila: did someone ask for it ? [11:26] err, wrong channel [11:33] psivaa_, hmm, seems the krillins cant do adb anymore in smoketesting ... [11:33] ogra_: let me take a look [11:34] psivaa_, we enabled the adb lockscreen checking ... plars thought it was all fine server side for this (needs a certain u-d-f version that seemed to be installed on the server) [11:35] could you reboot one of the krillins in recovery and check if there is a file called ".adb_onlock" in the /data dir [11:35] ogra_: u-d-f is the latest in the server [11:36] and yes i'll reboot krillin and check that [11:36] yeah, then --deveolper-mode should create this file [11:42] ogra_: that file is there [11:43] damn ... then it should let you adb shell ... [11:43] uh ... [11:44] /data is mounted under /android/data in the running system [11:44] ogra_: it just says error when adb shell is run [11:44] how do i get more verbose output? [11:44] it should say "error: closed" [11:44] right [11:45] ok, yeah, thats the lock check code [11:45] but adbd looks for /data/.adb_onlock [11:45] while i guess it needs to look for /android/data/.adb_onlock [11:45] * ogra_ tries that here [11:45] ogra_: do you want me to move it [11:45] yeah [11:46] let me try that [11:47] move it, reboot and you should be able to adb shell [11:47] there is no /android btw, hope it's OK for me to create? [11:49] ogra_: does not seem to fix [11:49] yeah, i'm able to log in right after lightdm started ... no unlocking needed [11:49] works here, are you sure the filename is correct ? [11:50] phablet@ubuntu-phablet:~$ ls -l /android/data/.adb_onlock [11:50] -rw-r--r-- 1 root root 0 Jan 24 12:46 /android/data/.adb_onlock [11:51] ogra_: i *created /android/data and moved the file from /data, then i did adb reboot. now the /android/ dir is gone [11:51] eek [11:52] in a normal boot ? [11:52] (in recovery there is indeed no /android dir) [11:52] no in recovery that was [11:52] no, in recovery that was. i mean [11:53] but without being in recovery i can not adb shell [11:55] oh [11:55] try the following in recovery then: [11:55] touch /data/android-data/.adb_onlock [11:56] then reboot again [11:56] trying.. [11:58] ogra_: i'm in with that [11:58] heh [11:58] :) [11:58] ok, adbd needs to check in /userdata for the file then [12:02] i guess a new image then :) [12:02] bfiller, boiko landing of silo 11 failed. Test 4 of the test plan of history service (Ensure that history-daemon is not running by default after rebooting phone) does not pass [12:03] bug 1414288 [12:03] bug 1414288 in android-tools (Ubuntu) "adbd falsely looks for /data/.adb_onlock to override the screen lock check" [Undecided,New] https://launchpad.net/bugs/1414288 [12:03] jibel, do we have anyone who can approve landing a fix for this ? ^^ [12:04] its a 4char change to get smoke testing back on track [12:04] ogra_, ping me when it is in a silo [12:04] ok [12:07] ogra_: do you have a FB account? [12:07] davmor2, nope [12:08] I'll ping cwayne1 [12:13] trainguards ^^ [12:13] :P [12:32] jibel: I'll be back in a few hours to check that [12:42] o/ [12:43] Practice took longer, but I'm on IRC now if any landings need tending ;) [12:43] sil2100, line 101 please [12:43] +1 ;) [12:44] Browser opening! [12:47] thx [12:50] yw! [12:52] charles: once you're around, would be awesome if https://code.launchpad.net/~charlesk/indicator-datetime/rtm-14.09-lp-1410874-alarm-sounds-vs-calendar-sounds/+merge/247229 could get approved === sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping sil2100 | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: devel-proposed images for mako #74 and krillin #82 can't be installed === sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping sil2100 | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: - [13:08] sil2100: everything is broken so far not a good start to the day :( [13:12] davmor2: want some fb testing or something? [13:12] davmor2: what's broken? [13:12] jibel, silo 015 is ready (line 101 has all instructions) [13:13] ogra_, ack. [13:13] popey: I got onto cwayne1 via email and pushed him all the info he asked for [13:13] Anything for me to worry about? Anything landed that broke the world? Since my e-mail says nothing [13:14] jibel: checking if that is supposed to be like that or the test plan needs to be updated [13:14] sil2100, the adn change for which you just assigned 101 [13:14] *adb [13:15] sil2100: silo 19, silo 0, silo 11, silo 7, silo 17 and the one I'm working on currently is partially fixed and partially broken in silo 8 [13:15] davmor2: ok [13:20] ogra_: so it looks like signon-apparmor-extension got added back into the seed even though the silo 19 that fixes the failure to add a u1 account failed so now scopes can't log into anything and I'm assuming that app installs will fail and this is why it should be a dep on package and not in the seed grrrrrrrrrr [13:22] jibel: hmn, for me history-service is not running after boot [13:22] jibel, boiko : with silo 11 [13:22] will reflash with latest build and try [13:22] back in a few hours [13:23] sil2100: ^ [13:23] phablet@ubuntu-phablet:~$ ps auwx | grep history [13:23] phablet 3684 0.0 0.0 4836 664 pts/42 S+ 08:21 0:00 grep --color=auto history [13:26] geh... [13:28] bfiller, I'm on 210 with silo 11, let me reboot one more time. [13:28] rtm/krillin [13:32] bfiller, immediately after boot, I unlocked SIMs and greeter [13:32] ⟫ adb shell pgrep -a history [13:32] 3474 /usr/bin/history-daemon [13:32] bfiller, how do I troubleshoot that? [13:34] bfiller, I'll reflash and try again [13:35] Lunch time [13:42] Good reminder, same here [14:19] ogra_, if you want us to test silo 15 can you build it? it is marked "Silo ready to build" [14:19] jibel, oops, yeah, indeed [14:20] and update the test plan with this case if it is not done already (I haven't checked yet) [14:20] i dont think there is any testplan at all for adbd [14:21] ogra_, do we need to back out the signon apparmor extension [14:21] that solves the test plan problem then [14:21] pmcgowan, dbarth bugged me daily for the last ten days to seed it ... no idea, i just made the change for him [14:23] dobey, can you check on silo 19 [14:23] * ogra_ can indeed quickly drop it again if needed ... as long as you are sure dropping it solves the prob [14:24] pmcgowan, i think you got his mail about it too ... [14:25] Subject: "Seed of signon-apparmor-extension to RTM" [14:29] ogra_, yeah he said it worked for him, just pinged him [14:34] pmcgowan: with the package removed from my long term use phone I have a usable system again, silo19 failed yesterday as I could login to U1 in order to install or buy and app [14:34] davmor2, dbarth will be here soon to take a look, god to know [14:34] could not login even [14:34] good [14:35] pmcgowan: dobey already started looking at it last night [14:35] let me forward you the mail [14:36] ok, seems we should have an MR for signon in that silo [14:36] pmcgowan: 2 incoming [14:38] pmcgowan: my confusion is to why signon wasn't just a dep of the package rather than added to the seed directly , thankfully cwayne1 was pretty responsive to the email I sent him today to figure out what the issue was [14:38] davmor2, ok lets see what db says [14:39] biab [14:39] davmor2, might be that the package is also on desktop and a dep would have pulled it in there which could be unwanted [14:40] ogra_: hmm true [14:41] ogra_: all I can say is thank god for the silo 000 or I doubt I would of noticed till Monday on sanity testing :) [14:41] jibel: did you want me to sanity test 210 and see what is broken by the package? [14:43] davmor2, i'd rather fix it, build a new image and sanity test that, since we know it's broken? [14:44] jibel: fair enough, the only issue is going to be that any silo we test that uses it is likely to be broken [15:23] ogra_, +1 for silo 15 [15:23] I added the tests to our test plan [15:23] thanks ! [15:28] Publishing [15:32] ogra_, jibel: thanks for the silo! [15:38] davmor2: signong-apparmor-extension isn't a dependency of u1-credentials, because it isn't a requirement for u1-credentials to be useful; rather, with the necessary fixes even, it seems to break u1-credentials, or at least, it breaks it for anything that is unconfined and needs to use online-accounts, from what i can see [15:39] dobey: which is possibly the issue with scopes I think most of the act in an unconfined manner right? [15:39] dbarth: ^ [15:40] davmor2: not sure which scopes you're talking about, but most are confined afaik [15:41] dobey: so for example with signon-apparmor-extension in place like on image 210 photos login for facebook and instagram fail even though the accounts exist [15:42] davmor2, dobey: i'll be there in a second on r210 [15:42] davmor2: i'm pretty sure fb/instagram are confined [15:43] dobey: hmmm could be [15:43] what escapes me is that 205 + extension + silo 19 work fine for me [15:44] dobey: do you have LoggingLevel=2 in ~/.config/signond.conf ? [15:44] i will need to change networks to get 210 fully unfortunately [15:45] otheriwse, i have verified the branches and fixes and all the ones attached to the bug (but the 2 u1 ones) are merged fine and in rtm afaics [15:46] i don't right now [15:47] dbarth: exactly! like i said, it was working fine last week when i landed the exact same change in vivid, but now it's broken there too :( [15:47] err [15:47] davmor2: even [15:48] dobey: no I think it was a good reply to dbarth :) [15:49] oh right [15:49] i should go back to sleep [15:49] and i'm not really "here" anyway, i just hopped on to check non-work things and saw my name hilighted in irc :P [15:50] dobey: sorry for that, but real quick, you have all the rtm branches already in silo, right? [15:50] dobey: ie, the announce errors and unconfined ones? [15:51] yes [15:51] silo 19 is both branches [15:51] ok === chihchun_afk is now known as chihchun === bfiller_ is now known as bfiller [16:55] jibel: unlocking the sims is what's causing history-daemon to start and that is normal. if you don't have sim lock on and reboot it will not be running [16:55] boiko: isn't that correct? [17:05] trainguards: anyone around who can help reconfigure ubuntu silo 7? I added a new package to it [17:05] sil2100 or cihelp ^^^ [17:06] bfiller: can do [17:06] rsalveti: great, thanks [17:07] bfiller: done [17:07] rsalveti: cheers [17:09] bfiller: dbarth: davmor2: what happened with signon-apparmor-extension then? [17:09] should we revert the seeds change? [17:09] rsalveti: davmor2: ok, so by removing the apparmor extension i can go 1 step further with pay_ui [17:09] davmor2: so i guess, the workaround for now is to unseed again the extension [17:09] davmor2: and check further whats wrong upstream in vivid where it was working previously [17:09] pmcgowan: ^^ ; i'll send a quick summary [17:10] right, but should we revert or wait? [17:10] rsalveti: don't know about that [17:10] dbarth: what do you think? [17:10] we can revert that and trigger a new image later today with the fixes that got in already [17:11] seems we should revert [17:11] what was the issue? not caught up [17:11] alright, let me prepare that [17:11] scopes and such are denied access [17:11] davmor2> [08:20:47] ogra_: so it looks like signon-apparmor-extension got added back into the seed even though the silo 19 that fixes the failure to add a u1 account failed so now scopes can't log into anything and I'm assuming that app installs will fail and this is why it should be a dep on package and not in the seed [17:12] bfiller: on it! [17:12] sil2100: no worries, rsalveti took care of it [17:12] sil2100: already reconfigured it [17:12] bfiller: ah, rsalveti was faster ;) [17:12] rsalveti, actual problem seems unrelated to U1 but maybe to the ACLs , [17:12] rsalveti: you won't revert other seed changes though right (with keyboards stuff added) [17:12] bfiller: you can't buy or install apps, you can't login to any accounts from scopes and the scopes don't show content for accounts you are signed in for other than that nothing [17:12] bfiller: nops, just signon-apparmor-extension [17:12] davmor2: minor issue :) [17:12] I would say +1 for the revert, since it will also open up more QA possibilities [17:12] bfiller, how does one use the emojis [17:13] alright, let me prepare the silo [17:13] pmcgowan: go to keyboard settings and enable it like other language layouts [17:13] bfiller: let me check (history-daemon) [17:13] pmcgowan: then it will show up in globe menu in keyboard [17:14] bfiller, should we turn that on by default? [17:14] or based on context? [17:14] pmcgowan: don't think so, iOS does not [17:14] I think it works like any other language [17:14] And for now that's good enough I suppose [17:15] nice [17:15] pmcgowan: no color yet, need support in qt 5.4 for that [17:15] ok [17:15] but better than nothing [17:15] bfiller, got about 4-6 in here so far [17:16] pmcgowan: silos? [17:16] bfiller, snow :) [17:16] pmcgowan: ah [17:16] pmcgowan: me too, about the same [17:16] about 6 silos too it seems :) [17:16] pmcgowan: had to drive to Dorchester this morning for Owen's hockey game, kind of nasty [17:17] I bet [17:17] Snowing here as well, moments like these make me sad for not having a garage [17:17] Will have to un-snow the car [17:18] biab [17:18] * sergiusens mentions it's 38 Celcius here today [17:18] *celsius [17:18] hmm... who's filling in for the scopes team? [17:19] pmcgowan: so for testing now I'm just going to remove that package it has already unblocked silo0 [17:19] * sil2100 needs someone to approve https://code.launchpad.net/~marcustomlinson/net-cpp/fix_ppc_timeout-rtm/+merge/247409 [17:21] brb, need to fetch my girl [17:42] sil2100: pmcgowan: problem with https://code.launchpad.net/~marcustomlinson/net-cpp/fix_ppc_timeout-rtm/+merge/247409 is that it seems only tvoss is able to top approve [17:42] because he's the maintainer and driver of the net-cpp project [17:42] which is wrong [17:43] sil2100: so only tvoss can currently approve that [17:53] pmcgowan: davmor2: publishing the revert [17:53] we should trigger a new image soon, just don't yet know if we're landing more stuff today [17:54] will wait a few hours and trigger a new image === barry` is now known as barry_ === barry_ is now known as barry [18:00] rsalveti, wait until we land silo 11 to trigger a new image, it's the last critical from the list of silos ready for QA. [18:00] jibel: sure [18:01] probably less than one hour [18:06] Back [18:07] rsalveti: geh, net-cpp needs some additional maintainers, seriously [18:07] yup [18:18] jibel: I was going to test the history-daemon thing, but after flasing rtm proposed I could not access the device via adb anymore, trying to flash again to see if it helps [18:18] boiko, unlock the device to use adb shell [18:19] jibel: oh, didn't know, thanks [18:19] boiko, it's a fix that landed yesterday [18:19] or security feature, give it the name you want [18:20] jibel, ok, installing the silo to test now [18:23] jibel: the history daemon is not running here after rebooting, anything special in your setup I need to be aware of? [18:26] bfiller: I don't think sim unlocking should bring the history-daemon up, but I will give it a try to try to reproduce what jibel is seeing [18:28] night all catch people tomorrow === chihchun is now known as chihchun_afk [18:35] davmor2: see you o/ [18:37] boiko: no other explanation I can think of [18:38] can someone top approve https://code.launchpad.net/~marcustomlinson/net-cpp/fix_ppc_timeout-rtm/+merge/247409 per the first comment [18:42] bfiller, maybe [18:42] pmcgowan: doesn't let me [18:43] bfiller, maybe I can whats the link [18:43] you just pasted it [18:44] so its just not enabled to approve [18:44] pmcgowan: where it says status there will be an option to mark it approved [18:44] right [18:44] pmcgowan: right, same for me [18:44] any landers here with the powers? [18:44] pmcgowan: bfiller the target branch for that is ~tvoss [18:44] pmcgowan: bfiller only tvoss can top approve [18:45] https://code.launchpad.net/~thomas-voss/net-cpp/rtm-14.09 [18:45] yep I see it [18:45] bfiller, silo 11 is OK-ish. searching for " returns nothing and % returns everything. the search string is not escaped properly. [18:47] bfiller, and the test plan of the messaging-app has not been updated [18:48] pmcgowan: I can override that and enforce landing that [18:48] pmcgowan: but I need to hear a definite override decision from someone higher-up ;) [18:49] pmcgowan: should I land it without a top-approval? [18:51] jibel: we can fix those and update the test plan, there should be some automated tests already but we can add manual ones as well [18:52] boiko: can you have a look at those issues? not sure if tiago around [18:52] bfiller: sure, I will fix those [18:52] sil2100, let me verify what his comment says [18:52] bfiller, right, there is one AP test but it is very basic and just search for a plain ascii string [18:52] pmcgowan: yeah, as I said earlier today, needs tvoss [18:52] because he's the owner of the project [18:53] the commit seems fine, so I'd just vote to override it [18:53] and get tvoss to fix that project and branch [18:53] pmcgowan: it passed QA so it seems ok, but still I always prefer to make sure that we land what the upstream developers want in their code - but this seems safeish [18:53] sil2100, it is the same diff as he said [18:53] it's also already in trunk, and tvoss approved that one [18:53] 4 lines [18:53] right I say go ahead [18:55] ACK [18:57] Landing [19:20] Crap [19:20] Yeah, this needs tvoss... [19:26] The train doesn't have the power to push to that branch, grrr [19:26] And I suppose webops are not available today [19:28] sil2100, seems the package landed but the merge failed? [19:30] pmcgowan: yeah, not much I can do with that, I'll have to just send an e-mail to tvoss about this [19:30] And free the silo in the meantime [19:30] No one in #webops to help me sadly [19:30] sil2100, yep ok [19:38] o/ [19:40] rsalveti, sil2100 anything else looking to land or ready for a build [19:41] pmcgowan: all waiting qa sign off [19:41] pmcgowan: it seems everything is waiting on QA, there's only boiko's new vivid silo [19:41] But that seems to be far from ubuntu-rtm yet [19:42] doesnt seem to be anything active right now, dav is off [19:42] I think 11 needs fixes [19:42] as does 17 [19:44] pmcgowan: afaik jibel is still testing 11 [19:48] rsalveti, boiko fixing some issues there [19:48] pmcgowan: should we trigger a new image then? [19:50] rsalveti, trying to raise boiko to see [19:51] rsalveti, did you see my comments on the battery bug with AP connected and not [19:51] pmcgowan: iirc you said the battery consumes faster when connected, right? [19:52] rsalveti, yes, at least the aborted suspends are much higher [19:52] right, that's expected with our wlan driver afaik [19:52] so maybe doesnt prove anything [19:52] but colin said 15% aborts was too high as I recall [19:53] and its much lower o mako [19:53] because any ping/request to the device ip is already enough to wake it up [19:53] right, that might be a difference/bug with our own driver [19:53] that's why testing with android is also so critical [19:53] ok [19:53] we might not necessarily be using the same options and so on [19:53] right [20:08] sil2100: I added a new component to vivid silo 17, can I just use the reconfigure link, or do you guys need to act on that? [20:08] boiko: a completely new component? [20:08] Or an MR to an already allocated project? [20:09] sil2100: yep, it had history-service, I added messaging-app [20:09] boiko: ok, I'll reconfigure it for you then [20:09] sil2100: thanks :) [20:09] Currently it's still restricting that ;) [20:10] sil2100: no problems, just wanted to check :) [20:12] Reconfigured :) [20:14] pmcgowan: rsalveti: jibel: fixes building on the silo already, I will now just update the testplan [20:15] boiko: in which silo? [20:15] Ah, in 11? [20:15] ACK [20:16] Not sure if jibel is still around today :) [20:16] He was already long long long [20:16] sil2100: oh ok, no problems [20:45] sil2100, boiko unless it's an emergency, I'll review it tomorrow. [20:47] pmcgowan: rsalveti: ^ [20:47] pmcgowan: rsalveti: in that case, I think you can trigger a new image [20:55] boiko: alright [21:02] rsalveti: image triggered? [21:02] :) [21:02] yup [21:02] should show up son [21:02] soon [21:02] Although come to think of it in a few hours we would have the auto-built one anyway [21:03] rsalveti: thanks [21:03] https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch/ [21:03] nops, cron is disabled on weekends [21:04] Oh [21:04] Ok, then good :) [21:04] Make sense [21:04] * sil2100 needs to AFK for some time [21:04] bbl [21:05] === IMAGE RTM 211 building (started: 20150124-21:05) === [21:20] very good [22:10] === IMAGE RTM 211 DONE (finished: 20150124-22:10) === [22:10] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/211.changes === [22:10] pmcgowan: ^ [22:31] Woot, that should make things easier. [22:34] Oh! [22:58] Not a fan of the new restrictions on adb connections. [22:58] It totally broke half of my flashing script. [23:00] Also, breaks the method normally used to install silos... which normally happens *before* the setup wizard. [23:05] ToyKeeper, adb reboot recovery; adb shell touch /data/.adb_onlock; adb reboot [23:06] (after that the check is disabled ) [23:06] ooh, thats handy, thanks ogra_ [23:07] if you flash with --developer-mode and --password u-d-f puts that file in place [23:07] I must have an old version of UDF. [23:18] well, we didnt SRU u-d-f so this function is only in the vivid versionn [23:52] Anything needing releasing? [23:54] *in need of