[02:09] <imgbot> [03:24] <imgbot> [03:24] <imgbot> [07:19] <abeato> trainguards, need a silo for line 91 (fix for bug #1388030)
[07:19] <abeato> Mirv, ^^
[07:26] <Mirv> abeato: ok
[07:26] <abeato> Mirv, thanks
[07:27] <mvo> hey trainguards - so the train is fully on halt even for vivid AFAICT. what should I do if I want to land a new click for vivid? go the old-fashioned route and manually merge/dput? or is there some other way (or should I simply wait :) ?
[07:28] <ribru> mvo: vivid landings are wide open. Train doesn't land clicks though.
[07:29] <ribru> Oh you mean click itself...
[07:29] <mvo> ribru: this is click itself, yeah :)
[07:29] <Mirv> mvo: the same as what ribru said, vivid is open, rtm is closed
[07:29] <mvo> ribru: hm, maybe I forgot to click on a box somewhere? its silo 30
[07:29] <ribru> mvo: it's fine, get a silo. Mirv can do it, midnight for me ;-)
[07:29] <mvo> ribru: rest well
[07:29] <Mirv> ribru: you should stop checking IRC on midnight/Sunday :)
[07:29] <mvo> and thanks
[07:29] <ribru> Thanks
[07:30] <ribru> Mirv: the curse of irc on my phone ;-)
[07:30] <mvo> ribru: haha
[07:30] <Mirv> ah, right, "too easy"
[07:30] <Mirv> mvo: so, silo 30 is ready to build, so you should just click build?
[07:32] <mvo> Mirv: oh well, I need a cup of tea I guess, I forgot that I need to click that and that it won't happen automatically
[07:32]  * mvo slaps himself
[07:32] <Mirv> mvo: I wish we had that sort of automation ;)
[07:33] <mvo> Mirv: I hope the airline will have it :) it seems like if everything is set to ready the system should just go ahead and build it
[07:42] <tvoss> good morning
[07:58] <tvoss> ogra_, ping
[08:04] <tvoss> o/
[08:19] <brendand> morning ogra_
[08:27] <popey> Good morning!
[08:28] <abeato> brendand, morning, I need QA for silo 8
[08:28] <seb128> hey popey
[08:29] <abeato> those were bugs from previous iteration
[08:30] <brendand> abeato, ok. it might be delayed a bit since we're qa-ing the release candidate
[08:30] <brendand> abeato, anyway nothing is landing right now
[08:30] <abeato> brendand, ok, no worries
[08:49] <sil2100> o/
[08:50] <sil2100> davmor2, ogra_, brendand: so from Selene's e-mail, do you guys think any of the issues pointed out could be potential blockers for our promotion?
[08:51] <sil2100> I also wonder if ToyKeeper was able to finish all tests required for promotion testing, or will a re-test be needed
[08:57] <Mirv> sil2100: o/
[09:07] <ogra_> sil2100, well, the crashes are quite a bit worryong (see the followups in the thread)
[09:07] <ogra_> tvoss, hey, you pung ?
[09:08] <sil2100> Woha, that's a lot of follow ups
[09:09] <ogra_> sil2100, beyond that (and massive battery usage when playing music which is new ... ) i would personall say it is fine ... but for the crashers it sounds like product team should say a word about  signoff
[09:09] <ogra_> +y
[09:10] <tvoss> ogra_, sil2100 Saviq and me are on the crashers
[09:10] <ogra_> (not sure we have a grip yet though)
[09:10] <sil2100> ogra_: I think now it's just us on the case, since the product team anyway took this image for their testing
[09:10] <ogra_> tvoss, right, the question is how deep your grip is yet ... should we hold back for a respin ?
[09:10] <brendand> ogra_, would be good if we could get rid of the crasher
[09:10] <tvoss> Saviq, what are your thoughts?
[09:10] <brendand> ogra_, but it's certainly not totally unstable
[09:11] <ogra_> brendand, yeah, but if it takes another day thats to long
[09:11] <Saviq> tvoss, sil2100, ogra_, I was thinking of a workaround, the whole crashiness seems to be still related to Audio {} in a notification / snap decision
[09:11] <ogra_> if we can fixx them in the next hours and re-spin so we can get a delta test just for that issue, i think we should re-spin ...
[09:12] <ogra_> but only then ...
[09:12] <Saviq> but I actually don't know of any consumers of that Audio { } component (just trying to confirm now)
[09:12] <Saviq> everyone is playing the sound by their own (telephony, alarms etc.)
[09:12] <ogra_> if there is a chance to delay beyond today, we shouldnt (but the issue should be clearly communicyted to all parties)
[09:13] <Saviq> so I'm thinking we could just drop the Audio { } to reduce the risk of crashes and give ourselves time to properly investigate
[09:13] <tvoss> Saviq, +1 from my side
[09:13] <ogra_> Saviq, well, the fact that battery drains like crazy on music playback also kind of points in that direction
[09:13] <tvoss> ogra_, ?
[09:13] <Saviq> ogra_, right, that is totally new to me
[09:14] <tvoss> ogra_, did we check the gstreamer/pulse landings?
[09:14] <ogra_> i get less than 4h from the phone on constant music playback ... that used to be a lot more
[09:14] <davmor2> Morning all
[09:15] <ogra_> it also feels like we kind of lost the advantages from power saving we had last weekend
[09:15] <davmor2> ogra_: don't watch youtube videos then
[09:15] <ogra_> davmor2, just flac playback ... not even excessive mp3 decoding involved
[09:16] <davmor2> ogra_: run top on playing music I think media-hub-server climbs quite high sometimes
[09:16] <tvoss> ogra_, while battery life certainly is something to investigate, we have no grip on it, yet
[09:16] <ogra_> tvoss, no, but that also points on media-hub direction
[09:16] <ogra_> s/on/in/
[09:16] <tvoss> ogra_, well, I would argue towards gstreamer or pulse
[09:17] <tvoss> ogra_, do you use a bluetooth headset?
[09:17] <ogra_> no
[09:17] <ogra_> wired headphone
[09:18] <seb128> Saviq, ubuntu-system-settings use Audio{} to preview ringtone/message sound
[09:18] <Saviq> seb128, sure, but that doesn't cause it to crash though
[09:19] <Saviq> seb128, I only mean to remove it from notificaions
[09:19] <Saviq> +t
[09:19] <Saviq> seb128, not from anywhere else
[09:19] <seb128> Saviq, sorry, I didn't follow the conversation, I was just replying to "<Saviq> but I actually don't know of any consumers of that Audio { } component (just trying to confirm now)"
[09:19] <Saviq> seb128, [...] in notifications
[09:19] <seb128> Saviq, got it, ignore me ;-)
[09:20] <Saviq> seb128, basically, no one's using the "sound-file" hint for notifications AFAICT
[09:20] <tvoss> ogra_, the audio role stuff might cause issues, too. That's the other big change we had landing to the infrastructure. As far as I know, it keeps multiple streams in pulse open
[09:23] <ogra_> tvoss, right ... and it must be somethin that landed after last weekend ... i surely had a lot better battery life over all right after the NM fixes landed
[09:23] <tvoss> ogra_, do we track battery life somewhere?
[09:24] <ogra_> not constantly ... cking_ does snaphot measurements at times i think
[09:26] <cking_> tvoss,   it's a task I'm passing over to QA, but if you need some re-testing, as ppisati
[09:26] <cking_> *ask*
[09:27] <cking_> ppisati has identical kit now set up to do some ad-hoc testing if required
[09:28] <ogra_> might be good to get some comparison testing between image 128 and 140 on krillin
[09:31] <Mirv> sil2100: when you're free from e-mail, we'd have a meeting :)
[09:32] <sil2100> Trying to connect ;)
[09:46] <davmor2> popey, ogra_, sil2100, brendand: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1378416
[09:46] <popey> thanks davmor2
[09:48] <ogra_> davmor2, i think that might be a duplicate of the other one
[09:48] <ogra_> or at least related
[09:51] <ogra_> brendand, davmor2, in your dashboard, if you had an incoming call, does it say From: x-ofono-unknown for past calls ?
[09:51] <ogra_> (it does for me)
[09:54] <popey> ogra_: i have seen that in the past, but not now. i see names and avatars
[09:55] <ogra_> it shows fine in the phone app ... just not in the dashboard
[09:56] <ogra_> and how can you see an avatar for a unknown number ? :)
[09:56] <ogra_> do we have some default ?
[10:01] <popey> oh, unknown.. sorry
[10:01] <popey> i dont have any unknown numbers call me ⍨
[10:07] <sergiusens> ogra_: yes it does say org-ofono-unkown
[10:25] <ogra_> sergiusens, bug 1388774 .... feel free to confirm
[10:25] <ogra_> :P
[10:35] <ogra_> mvo, oh, while i see the FTBFS above ... did you and cwayne talk about the failing click tests in smoketesting yet ?
[10:35] <thostr_> sil2100: can I get a silo for line 69?
[10:35] <mvo> ogra_: I looked at the failure output after resolving my vpn issues
[10:36] <sil2100> thostr_: looking!
[10:36] <mvo> ogra_: I find it a bit hard to read - where does the test come from? its not from click itself, is it?
[10:36] <ogra_> no idea ... i  thought it did ... cjwatson might be able to tell you
[10:37] <sil2100> thostr_: do you have 2 different trunks for rtm and vivid?
[10:37] <cjwatson> url to the test?
[10:37] <mvo> cjwatson, ogra_: http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/407/consoleFull
[10:38] <mvo> (this is what I got)
[10:38] <ogra_> cjwatson, the test that checks if all clicks from click_list are installed ... fairly simple one
[10:39] <ogra_> cjwatson, for krillin there are some removals and additions by the custom tarball ... the list needs to come from cwayne somehow and the test needs to read it
[10:39] <cjwatson> I'd need to see the source to the test, maybe it's only looking in /usr/share/click/preinstalled/
[10:39] <cjwatson> not a test I have heard of before
[10:39] <sil2100> thostr_: if not, then I can do a sync silo ;)
[10:40] <thostr_> it's two different ones...
[10:40] <thostr_> sil2100: but sync should still be possible
[10:41] <sil2100> thostr_: then whichever you prefer :) Just make sure that it doesn't conflict with the way those projects are handled by default
[10:41] <ogra_> cjwatson, mvo, psivaa_ should be able to point to the sourc eofr that one i think
[10:41] <thostr_> sil2100: however, to be on save side, let's not sync
[10:41] <ogra_> *source for
[10:42]  * psivaa_ is reading the backlog :)
[10:42] <cjwatson> ogra_,mvo: that stuff was all tested quite carefully by hand, so I think it's likely a test bug
[10:43] <ogra_> cjwatson, yes, as i said, it reads the wrong input list
[10:43] <ogra_> cwayne, needs to provide one for this ... and the test needs adjustment to find it
[10:44] <cjwatson> Right, so not something the click team needs to worry about
[10:45] <ogra_> yes, i just had hoped you had touched the test before :)
[10:46] <cjwatson> Nope :-)
[10:53] <sil2100> thostr_: ok, are there MPs ready?
[10:55]  * sil2100 wonders if branches can be re-used for 2 merges
[11:02] <thostr_> sil2100: yes
[11:02] <thostr_> sil2100: and it's different MPs
[11:07] <sil2100> thostr_: but using the same branches, right?
[11:08] <thostr_> yes
[11:09] <ogra_> tvoss, Saviq, any ETA for a possible fix ? else we should promote an image soon
[11:10] <ogra_> sil2100, ^^
[11:10] <tvoss> ogra_, gimme 30 minutes, building
[11:10] <ogra_> ok
[11:10] <ogra_> tvoss, dont stress it though, we can easily promote a new image later today with a proper fix
[11:11] <tvoss> ogra_, sure
[11:11] <ogra_> (after the first promotion i mean)
[11:30] <sil2100> thostr_: ok, assigning - a bit worried that it might cause some trouble to use the same branch in 2 merges if one gets merged in, but we can sort that out when it happens ;)
[11:57] <brendand> ogra_, seems rick wants the user metrics bug fixed :/
[11:57] <sil2100> brendand: which one?
[11:57] <sil2100> Before promotion?
[11:58] <ogra_> do we even have an idea whats wrong with that ?
[11:58] <sil2100> I wouldn't block todays promotion on that I think...
[11:59] <sil2100> But that's just IMO
[11:59] <ogra_> same here
[12:00] <ogra_> brendand, where did rick say that ?
[12:00] <ogra_> hah
[12:00] <ogra_> and there is the mail
[12:01] <ogra_> woah !!!
[12:02] <brendand> ogra_, i just sent a response, which i might regret shortly :/
[12:02]  * ogra_ just did a tail -f /var/log/syslog 
[12:02] <ogra_> this is *awful*
[12:02] <ogra_> it is spamming a log line like every second
[12:02] <tvoss> ogra_, yup, ust seeing that now
[12:03] <tvoss> ogra_, here we go for battery life ;)
[12:03] <ogra_> heh, yeah
[12:03] <ogra_> i wonder if thats the last device tarball
[12:03] <tvoss> ogra_, hmmm, what does hang_detect do?
[12:03] <ogra_> tvoss, i think it is a no-op for us
[12:03] <ogra_> rsalveti couls tell
[12:03] <ogra_> *could
[12:04] <ogra_> i dotn see any hang-detect though
[12:04] <ogra_> (on krillin)
[12:04] <ogra_> Nov  3 13:03:39 ubuntu-phablet kernel: [60977.307978][STP-PSM] [I]stp_psm_disable_by_tx_rx_density: rx cnt = 12 in the previous 3 sec
[12:04] <ogra_> i got one of these every second
[12:04] <ogra_> john-mcaleely, ^^^is that known ?
[12:04] <tvoss> onghttp://pastebin.ubuntu.com/8802139/
[12:05] <tvoss> ogra_, http://pastebin.ubuntu.com/8802139/
[12:05] <john-mcaleely> ogra_, um
[12:05] <ogra_> yeah, its an android daemon ... but i dont think we make any use of it
[12:06] <ogra_> it also doesnt seem to have consumed any CPU cycles for you
[12:06] <john-mcaleely> ogra_, doesn't look like one I know. Also doesn't seem likely for a regression from the changes
[12:06] <ogra_> john-mcaleely, no, rather an oversight than a regression
[12:06] <john-mcaleely> ogra_, yeah. We've never brutally cleaned the logging
[12:06] <ogra_> iirc that was the tarball that quietened all log writing
[12:07] <ogra_> we should definitely quieten this one too :)
[12:07] <ogra_> since that writes to disk
[12:07] <john-mcaleely> there's an outstanding change for the conn_soc driver. is that log likely to be from there?
[12:07] <ogra_> hmm, no idea :)
[12:07] <john-mcaleely> ogra_, raise a bug then, and we'll fix it
[12:08] <ogra_> seems to be the "STP power saving module"
[12:08] <ogra_> LOl
[12:08] <ogra_> more like a power wasting module now :)
[12:11] <ogra_> brendand, http://paste.ubuntu.com/8802213/ ... thats what i get in unity8 log when tapping the usermetrics entry in the greeter
[12:12]  * ogra_ wonders if there is any other way to get more usermetrics info 
[12:13] <sil2100> I wonder when this bug got introduced
[12:13] <sil2100> If it was visible before 139
[12:13] <ogra_> i wonder who but rick actually uses the usermetrics :P
[12:14] <brendand> sil2100, biggest culprit would probably be silo 10
[12:16] <tvoss> ogra_, so hang_detect comes from the ubuntu side :)
[12:16] <ogra_> tvoss, never :P
[12:16] <ogra_> its an android daemon
[12:16] <tvoss> ogra_, it is :)
[12:16] <ogra_> hmm
[12:18] <ogra_> the angled brackets make it even look like a kernel process
[12:18] <ogra_> where did you find the binary ?
[12:20] <ogra_> looking at the ps tree it clearly gets managed by kthreadd
[12:20] <ogra_> like binder or kswapd ... its a kernel process
[12:21] <tvoss> ogra_, ah yeah, true
[12:22] <ogra_> ps auxf helps ;)
[12:29] <tvoss> opening eyes, too ;)
[12:31] <ogra_> haha
[12:36] <ogra_> john-mcaleely, bug 1388810
[12:37] <ogra_> feel free to confirm if you can
[12:48] <ralsina> trainguard, can I change my rtm silo 5 into a vivid silo? I need to land there first anyway.
[12:48] <ralsina> that is row 49 in the spreadsheet
[12:48] <sil2100> ralsina: we'll have to free it up and re-assign to vivid (as it needs to build in a different distro)
[12:48] <sil2100> ralsina: would that be fine?
[12:49] <ralsina> sure!
[12:49] <ralsina> sil2100: and another vivid silo for row 50 please?
[12:51] <sil2100> ralsina: ok!
[12:51] <ralsina> awesome, thx
[13:18] <mlankhorst> fwiw I had some audio issues with the landing 001 ppa still, though a lot less often
[13:18] <mlankhorst> and might be a diff bug
[13:22] <tvoss> mlankhorst, ah, interesting. audio issues as in?
[13:23] <mlankhorst> things crash, I think it happened when plugging in something to the headphone connector, but not 100% sure
[13:29] <mlankhorst> I'm also investigating doing XMIR without hacking Xorg. Glamor should make the xorg hack obsolete in theory. :P
[13:32] <john-mcaleely> thanks ogra_
[13:33] <cwayne> jdstrand: ping
[13:35] <jdstrand> cwayne: hey
[13:36] <cwayne> jdstrand: heya, wondering if you were planning on landing a new apparmor-easyprof-ubuntu soon
[13:50] <jdstrand> cwayne: I wanted to check the bugs before I answered. there is one bug that is maybe an rtm bug: bug #1384286
[13:50] <jdstrand> thostr_: how important is that bug for rtm? ^
[13:50] <cwayne> jdstrand: that's already possible though, the tasks app/scope shares data now
[13:51] <jdstrand> cwayne: how is it doing that?
[13:51] <jdstrand> istr an apparmor denial for tasks in particular
[13:51] <cwayne> not sure, haven't checked the code, but it seems to work
[13:52] <ogra_> cwayne, https://bugs.launchpad.net/barajas/+bug/1388774 in case you didnt see that one yet
[13:52] <ogra_> (i didnt really know where to file it so it went there for now)
[13:53] <jdstrand> cwayne: this is tasks from the store?
[13:53] <cwayne> ogra_: that's odd, for me if its unknown it just shows the number
[13:53] <cwayne> jdstrand: nope, the preinstalled one
[13:54] <ogra_> cwayne, if i tap it i see all dates for the incoming calls in a list and have x-ofono-unknown at the top
[13:55] <cwayne> ogra_: which version of dashboard and calls scope?
[13:55] <ogra_> i have a still analog landline here, if i do call tests from it i get that entry
[13:55] <ogra_> cwayne, image 140
[13:55] <cwayne> ogra_: can you do a click list just so i can make sure the click versions are right
[13:56] <ogra_> gimme a number and i can give you a test call :)
[13:56] <ogra_> (note they were all rejected since i tried to repro the crash on reject on friday)
[14:13] <brendand> Wellark, finally getting around to silo 3 :)
[14:13] <thostr_> jdstrand: AFAIK there is not app/scope that share data as of today
[14:14] <jdstrand> thostr_: actually, cwayne pointed one out. the question is, do we want to support that for rtm?
[14:14]  * jdstrand is reviewing that app now
[14:14] <thostr_> jdstrand: is that the last item to make everythign work?
[14:14] <jdstrand> thostr_: no-- that is just my item
[14:15] <jdstrand> afaik
[14:15] <jdstrand> we need to decide on the directory
[14:15] <thostr_> cwayne: ^ what else is missing
[14:16] <jdstrand> I thought there was a scopes api component, iirc what michi said
[14:16] <cwayne> thostr_: not sure if anything else is missing, if we can access the same dirs we can figure out a way to share data
[14:16] <cwayne> although the tasks app/scope does share data today
[14:17] <jdstrand> cwayne: I need to confirm it works-- it might, but that was unintentional. I definitely remember seeing a denial
[14:17] <jdstrand> which makes me think it is not or it is using old data or some special read_path permission or something
[14:20] <mlankhorst> tvoss: does mir support input well enough for a standalone 'xmir' binary?
[14:20] <tvoss> mlankhorst, best to check with RAOF or anpok on that
[14:20] <mlankhorst> ok
[14:24] <jdstrand> cwayne:     "read_path": [
[14:24] <jdstrand>        "/home/phablet/.local/share/com.canonical.scopes.tasks/Databases/"
[14:24] <jdstrand>      ]
[14:24] <jdstrand> cwayne: so that is why it works
[14:24] <jdstrand> the denial I saw must've been before they implemented read_path in the security policy
[14:26] <cwayne> ah
[14:27] <brendand> tvoss, i got this crash in the wizard - https://errors.ubuntu.com/oops/88f4bdd6-6363-11e4-825a-fa163e4ccdf2
[14:27] <brendand> tvoss, does it look like one of the ones you're familiar with?
[14:28] <tvoss> brendand, yup, that's a known one
[14:28] <sil2100> brendand: how does the image look so far?
[14:29] <brendand> sil2100, the crashes are the main thing
[14:29] <ogra_> well, and rickspencer :)
[14:29] <ogra_> sil2100, (as he is wanting usermetrics fixed before promotion (see ML))
[14:32] <sil2100> I know, yeah...
[14:32] <ogra_> i guess we need to do some convincing here
[14:34] <brendand> ogra_, i didn't see him ask for it before promotion
[14:34] <brendand> ogra_, he said we can't ship with it, which is true
[14:34] <brendand> ogra_, but then we can't ship with these crashers still around
[14:34] <ogra_> ah, i interpreted that as "we cant ship a milestone"
[14:35] <abeato> sil2100, question, line 19 in the spreadsheet is for something that already landed, but we have to use another silo because of some problems we had, is it okay to just remove that row? would that break something?
[14:35]  * ogra_ asked him
 ogra_, well, first of all, I was expressing my opinion, not making a final decision ;)
 and second, yeah, I mean for final
[14:36] <ogra_> sil2100, ^^
[14:36] <ogra_> so we are good
[14:37] <sil2100> Good to know
[14:37] <sil2100> Anyway, we'll discuss that in ~1h
[14:40] <jdstrand> olli: hey, what is your opinion on bug #1384286 for rtm? it is a very small change with no chance of regression (due to build checks). I'd been holding off on it cause it didn't seem super important, but it seems borderline. if we don't do it now, we won't do it unless another critical bug in the policy is found
[14:40] <tvoss> sil2100, hey there
[14:40] <tvoss> sil2100, could we get qtubuntu-media into silo 12?
[14:40] <jdstrand> olli: it would require a custom tarball update
[14:42] <cwayne> jdstrand: is there a reason we can't just do the same read_path thing tasks does?
[14:42] <jdstrand> cwayne: people can do that as a workaround, but read_path requires manual review in the store
[14:43] <cwayne> ah ok
[14:43] <cwayne> jdstrand: my thinking is that it's not critical then, im fine with piggybacking it on another critical bug fix, but don't think we should roll an update just for that yet
[14:45] <brendand> Wellark, testing silo 3 and flight mode won't come on
[14:45] <brendand> Wellark, switch is one but no airplane icon and only one sim is offline
[14:45] <jdstrand> cwayne: it did come up in DC and the severity was not clear to me then, which is why I wanted thostr_ and olli's opinion
[14:45] <jdstrand> I don't care either way. I just need to pull the trigger on it if it is rtm :)
[14:46] <brendand> Wellark, see http://people.canonical.com/~brendan-donegan/flight-mode.png
[14:46] <jdstrand> I'll fix it in vivid probably today
[14:49] <brendand> thostr_, ^ - anyone able to help me look at that?
[14:49] <thostr_> jdstrand: I'll check with Olli
[14:51] <thostr_> brendand: Satoris will come back to you
[14:52] <jdstrand> thostr_: fyi, I updated the bug and asked michi to comment on the path. I'll also send a followup email
[14:52] <jdstrand> if nothing else, I'll have it fixed in vivid and the details will be settled
[14:55] <thostr_> jdstrand: ack
[15:00] <tvoss> brendand, got the crash file for me?
[15:02] <brendand> tvoss, this one - http://people.canonical.com/~brendan-donegan/_usr_bin_system-settings-wizard.32011.crash
[15:20] <satoris> brendand: I was told you have some problem with indicator-network.
[15:21] <brendand> satoris, yeah the ui seems to be stuck completely
[15:21] <satoris> As in can't even close the indicator or bring in the launcher?
[15:21] <brendand> satoris, no not like that
[15:22] <brendand> satoris, as in the indicator is incongrous with the real system state according to the ofono scripts
[15:26] <satoris> brendand: rtm, krillin and silo 3?
[15:26] <brendand> satoris, yes silo 3
[15:27] <satoris> Ok, reflashing to verify.
[15:28] <cwayne> davmor2: once theres a promotion, i've got a nice set of bugfixes in a custom tarball for ya :)
[15:29] <sil2100> cwayne: \o/
[15:29] <davmor2> cwayne: won't be till tomorrow earliest I think
[15:29] <cwayne> davmor2: i assumed as much :)
[15:29] <sil2100> cwayne: I hope those from the list?
[15:30] <satoris> brendand: is everything out of sync or only some parts (wifi, modem, etc)?
[15:30] <cwayne> sil2100: a few of them, yeah
[15:31] <brendand> satoris, everything. well i can't turn on wifi
[15:31] <brendand> satoris, it seems like the indicator is not sending any signals/calls
[15:32] <brendand> satoris, actually nmcli doesn't show the wireless hw at all...
[15:33] <satoris> brendand: that makes it a kernel or nm bug then. Indicator-network only presents what they report.
[15:44] <balloons> good morning fginther :-) Got a second to chat about testing the core app clicks as part of the job that builds them on s-jenkins?
[15:55] <fginther> balloons, can I ping you back in about 30 minutes?
[15:56] <balloons> fginther, sure thing, take your time. 12 or later your time works better for me
[16:03] <tvoss> sil2100, can I get qtubuntu-media added to silo 12?
[16:04] <sil2100> tvoss: ubuntu silo?
[16:04] <sil2100> It's a sync silo, right?
[16:04] <tvoss> sil2100, yup, the sync one to vivid for the stuff we landed in rtm
[16:05] <sil2100> tvoss: so, you would need to fetch qtubuntu-media from 14.09 there, right?
[16:05] <sil2100> I can do that in a moment
[16:05]  * sil2100 in a meeting
[16:07] <tvoss> sil2100, yup
[16:08] <ogra_> famous hour for meetins :)
[16:08] <ogra_> +g
[16:28] <bfiller> sil2100: can you reconfigure rtm 14 please? Added a new package
[16:32] <sil2100> bfiller: sure
[16:32] <sil2100> tvoss: a few moments more I need, as still in the meeting
[16:34] <tvoss> sil2100, sure
[16:35] <bfiller> sil2100: thanks
[16:41] <sil2100> brendand, davmor2: you guys finished the regression tests? Are you continuing with mako sanity tests?
[16:42] <davmor2> sil2100: in a call I will start it after
[16:42] <brendand> sil2100, exactly 1 regression test left :)
[16:45] <fginther> balloons, your request is probably something that just needs to go to our backlog and therefore more appropriate to discuss with ev or Ursinha who are managing that.
[16:46] <balloons> fginther, ahh, so I should have added a story at the meeting :-) If only my brain was clearer then. I checked to make sure stories existed for my other wants
[16:46] <fginther> balloons, no worries, I need to get used to it too
[16:53] <sil2100> brendand: \o/
[16:56] <sil2100> ogra_, brendand, davmor2: I might be late a few minutes, meeting overlapping
[17:12] <nik90> tvoss|food: hi, do you see my email about the qml position source fetching user location data every second despite calling the stop() function. I need to know if this is a known bug or not and I can accordingly judge if I should push the location feature for the clock app.
[17:12] <brendand> tvoss|food, i have ubuntu-location-service going crazy here again
[17:12] <nik90> tvoss|food: I just want to make sure that I don't introduce a feature that eats up the battery while using the clock app.
[17:25] <sil2100> Damn this laptop gets hot during hangouts, normally I don't have it on my lap so I don't feel it
[17:26] <ogra_> its getting winter as davmor2 said ...
[17:26] <ogra_> just sit on the balcony next time ;)
[17:26] <davmor2> ogra_: no the laptops are there for house heating
[17:27] <ogra_> ohh, right !
[17:27] <ogra_> just get some fireproof underwear then :)
[17:27] <davmor2> sil2100: look at top next time  you are using 210% cpu at times :)
[17:28] <davmor2> sil2100: by the way here is the doc you want to keep your eye on :) https://docs.google.com/a/canonical.com/spreadsheets/d/1Ar4x4tOf_c14QKCyKn3r4YQnJ3AZdnEXdjTOAhyXWXU/edit#gid=1467360386
[17:37] <john-mcaleely> sil2100, ogra_ so, is 140 being promoted?
[17:37] <ogra_> most likely ... we're still waiting for final results
[17:37] <john-mcaleely> ogra_, eta on that?
[17:37] <ogra_> john-mcaleely, note though that due to the crashers and issues we tra to do another promotion this week
[17:37] <ogra_> i think QA said 1-2h
[17:38] <john-mcaleely> ogra_, ok, I'll continue waiting
[17:40] <ribru> sil2100: did you see my branch for cu2d? I want to land that today. do you have a couple minutes to review?
[17:51] <sil2100> john-mcaleely: we're waiting for davmor2 to finish up mako sanity tests
[17:52] <sil2100> If that's ok, then we promote
[17:52] <sil2100> ribru: let me take a look at that
[17:52] <sil2100> Although soon I will have to drive back home
[17:54] <john-mcaleely> sil2100, great, thanks
[18:01] <tvoss|food> brendand, could you attach with gdb and get me a core dump?
[18:01] <tvoss|food> nik90, we will handle that case service side, go ahead with landing the feature
[18:01] <tvoss|food> nik90, also: nothing bad happens if the clock app is not in the foreground
[18:02] <nik90> tvoss|food: true, but I don't people to get the impression that the clock app is eating up their battery when its in the foreground
[18:02] <nik90> tvoss|food: but I trust you, so I will land it :)
[18:02] <tvoss|food> nik90, ack, cool
[18:02] <tvoss|food> nik90, looking forward to the feature
[18:03] <brendand> tvoss|food, it's gone now. next time
[18:03] <nik90> tvoss|food: it just shows the user location below the clock face, small feature
[18:04] <tvoss|food> nik90, sure, still
[18:05] <ogra_> nik90, is there any ETA on getting timer and stopwatch back ?
[18:06] <nik90> ogra_: tbh, I haven't seen any designs yet for it. And also it requires platform services that are currently missing like the ability to keep track of the timer when the clock app is in the background and few other use cases.
[18:06] <nik90> ogra_: so nope, I don't have an ETA on it. and tbh I am not exactly sure what I am going to be working on for this cycle either
[18:06] <ogra_> aww, thats sad ...
[18:06] <ogra_> imho thats a massive feature lack vs android
[18:06] <nik90> agreed
[18:07] <nik90> I will check in with popey and the designers to see what the plan is for that.
[18:13] <ribru> alexabreu: around? need some merges approved in order to publish https://ci-train.ubuntu.com/job/ubuntu-landing-008-2-publish/44/console
[18:13] <ogra_> ribru, ribs fixed ?
[18:14] <ribru> ogra_: better but not quite.... i got out of the house this weekend but didn't venture too far.
[18:15] <ribru> ogra_: mostly just sore, I think all the horrible pain is over
[18:15] <ogra_> cool
[18:15] <ribru> thanks
[18:15] <ogra_> :)
[18:19] <sil2100> ribru, slangasek: I'll have to drive out home in a moment, not sure if I'll make it on time home for the meeting though - not sure how much traffic there will be around
[18:19] <tvoss|food> sil2100, is silo 12 still on your list? :)
[18:20] <ribru> sil2100: ok well at least Ursinha-afk is back so hopefully we can chat with her ;-)
[18:20] <sil2100> tvoss|food: doing!
[18:20] <tvoss|food> sil2100, \o/
[18:20] <alexabreu> ribru, sure
[18:22] <alexabreu> ribru, all have been approved ... https://code.launchpad.net/~abreu-alexandre/webbrowser-app/fix-webapp-properties-ua-override/+merge/238991
[18:22] <ribru> alexabreu: thanks
[18:23] <ribru> alexabreu: why are they both listed as superseded?
[18:24] <sil2100> bbl!
[18:25] <alexabreu> ribru, 3 branches have been stacked together to ease up the landing ...
[18:26] <ribru> alexabreu: well I'm not really sure what you're trying to do in there. the MPs that are approved are not the MPs that are in the silo. so you should either unstack the MPs and de-supersede the MPs in order to publish as is, or you have to update the MP list in the silo to be the right MPs, then rebuild and retest then we can publish
[18:28] <davmor2> ogra_: why did you let sil2100 go now how can I tell him that the sanity testing on mako went okay
[18:29] <ogra_> davmor2, so you want a promotion ?
[18:29] <ogra_> i think he is fine with us promoting while he is gone :)
[18:29] <davmor2> jibel: ^ would you like to confirm?
[18:29] <ogra_> its not like he can do much
[18:30] <ogra_> (apart from cheering)
[18:30] <ribru> ogra_: oh if we have a promotable image does that mean I can finally publish these two silos that say "TOP BLOCKER"?
[18:30] <davmor2> ogra_: but you know how he likes to tell you to press the button
[18:30] <ogra_> ribru, *after* promotion (yeah, i'm german :P )
[18:30] <ribru> haha
[18:31] <ogra_> davmor2, yeah, i do ... but i guess he is fine this time :)
[18:33] <davmor2> ogra_: well press the button, there was one fail but it is the least of them and a reboot fixed it, music added to the device didn't show up in the scope for me but did in the music app, and it showed up after I rebooted so just a glitch,  the cpu on mako is pegging out at about 109%
[18:33] <alexabreu> ribru, mmmh not sure why those have been kept in the silo ... the branches are the same except that there have been a re-mr ...
[18:33] <ogra_> davmor2, ok, ... jibel any word ?
[18:34] <ribru> alexabreu: yeah, citrain doesn't magically know when you change mps! you have to put the new mp in the silo if you make a new mp
[18:35] <ogra_> and use the blinker ;)
[18:36] <alexabreu> ribru, mmmh, yes that's what I did! the stylesheet line is fine ...
[18:36] <davmor2> ogra_: just hit it, I think jibel might be on and offline currently, but the one issue I had he didn't, but he did see the 100%+ cpu issue
[18:36] <ribru> alexabreu: was it ever reconfigured?
[18:36] <ogra_> davmor2, ok, going for it then
[18:36] <alexabreu> ribru, I thought it was, ... maybe it wasn't
[18:36] <ogra_> running ...
[18:37] <ribru> alexabreu: last time silo 8 was reconfigured was oct 7th... unlikely
[18:37] <alexabreu> ribru, argh ... sorry it should have been recnfigured, and I thought it had ...
[18:37] <alexabreu> grr
[18:37] <alexabreu> ribru, could you reconfigure?
[18:37] <ribru> alexabreu: ok
[18:39] <ribru> alexabreu: ok reconfigured and building: https://ci-train.ubuntu.com/job/ubuntu-landing-008-1-build/108/console
[18:39] <alexabreu> ribru, thx
[18:39] <ribru> alexabreu: you're welcome
[18:55] <ribru> bfiller: rtm 5 for line 94
[18:55] <ribru> bfiller: lines 93 and 95 conflict with existing silos, can you merge those?
[18:56] <john-mcaleely> looks like a promoted image just landed...
[18:56] <ogra_> ssshhh
[18:56] <ogra_> (still rinning)
[18:56] <ogra_> *running
[18:57]  * ogra_ twiddles thumbs waiting for the emulator images
[18:59] <veebers> ogra_: Morning, hey I tried to install autopilot on a vivid image and it gave me an error about a file conflict with dbus-propert-service, I thought this was sorted?
[18:59] <john-mcaleely> krillin is here :-)
[18:59] <bfiller> ribru: looking
[19:00] <olli> oops
[19:00] <olli> where did sil2000 go
[19:00] <ogra_> olli, driving home
[19:00] <ogra_> ok, there we go
[19:01] <ogra_> [19:01] <olli> did it happen ?
[19:01] <ogra_> (this is krillin 140, mako 118, generic and generic_x86 112)
[19:01] <ogra_> olli, when i give that note with three = then it did usually ;)
[19:02] <olli> just double checking
[19:02] <olli> awesome!
[19:02] <ogra_> [19:02] <olli> thank you thank you thank you everyone
[19:02]  * ogra_ goes to have linner
[19:02] <ogra_> :)
[19:02] <olli> this definitely doesn't feel like a Monday
[19:04] <john-mcaleely> \o/
[19:04] <popey> ooh
[19:28] <bfiller> ribru: 93 I can combine with silo 6, but 95 can't really be combined with silo 15 as it's a different fix and would require different qa
[19:29] <ribru> bfiller: ok, please do the silo 6 thing, the reconfigure link should work for you, then you can rebuild. I'll assign line 95 then
[19:29] <ribru> thanks
[19:29] <bfiller> ribru: ack
[19:29] <ribru> bfiller: ok you got rtm 17.
[19:29]  * ribru -> lunch
[19:40] <ogra_> sil2100, promoted ...
 [19:40] <ogra_> ogra_> (this is krillin 140, mako 118, generic and generic_x86 112)
[19:41] <sil2100> ogra_: \o/ great news then!
[19:41] <bfiller> ribru: also need a silo for line 76 when you get a chance
[19:41] <ogra_> open the gates !
[19:41] <sil2100> btw. was there any decision regarding flo and manta?
[19:41] <ogra_> they didnt get any QA
[19:41] <sil2100> I know, just want to know if anyone thought about them as being our reference platforms
[19:42] <sil2100> Since it makes no sense to have reference platforms which we have no menpower to handle ;)
[19:42]  * ogra_ didnt 
[19:42] <sil2100> Anyway, ogra_, davmor2, brendand: thanks guys!
[19:42] <ogra_> tablet users should use vivid/utopic
[19:42] <sil2100> And, of course, big thanks to ToyKeeper !
[19:42] <ogra_> until we have a product that requires tablet support in rtm
[19:42] <ogra_> yeah
[19:42] <ogra_> thanks to all of QA for the hard work !!
[19:43] <sil2100> Ok, let me open up the gates then
[19:43] <sil2100> ribru, elopio, ToyKeeper, davmor2, brendand: remember to proceed carefuly anyway, prioritizing the fixes for the most wanted bugs (crashes, 100% CPU and infographics)
[19:43] <sil2100> We might want another promotion soon
[19:44] <ogra_> sil2100, i think there are other fixes for stuff from errors.u.c ... we should consider that too IMHO
[19:44] <ToyKeeper> sil2100: I think the plan is one promotion per week until release.
[19:44] <ogra_> (like mtp )
[19:44] <sil2100> Of course, I don't say we don't land anything else, but these are nice to have as we basically slightly whitelisted some annoyances
[19:45] <ogra_> right
[19:45] <sil2100> ToyKeeper: yeah, that's the management plan, but we actually wanted to promote another thing this week with just some fixes to the most annoying bugs
[19:46]  * sil2100 is happy and will in a moment write a happy landing e-mail
[20:20] <jhodapp> sil2100, ping
[20:22] <jhodapp> ribru, ping
[20:23] <ribru> bfiller: rtm 20
[20:24] <jhodapp> ribru, for an entry in the landing spreadsheet like line 21 where the landing silo was removed, but the rtm silo isn't there to sync from anymore either, is this line of any use? Or do I need a completely new entry to land that bug fix into vivid?
[20:24] <ribru> jhodapp: checking
[20:25] <ribru> jhodapp: is it the case that the landing landed in rtm?
[20:25] <jhodapp> ribru, it is, yes
[20:25] <jhodapp> ribru, during the DC sprint
[20:26] <ribru> jhodapp: ok in that case, just change column G to say 'sync:ubuntu-rtm,14.09 media-hub' and then we can reassign that to sync from the archive rather than a ppa
[20:26] <bfiller> ribru: thanks
[20:26] <ribru> bfiller: you're welcome
[20:26] <jhodapp> ribru, ah nice, I imagine that would need every package name of what to sync, right?
[20:26] <jhodapp> ribru, more than just media-hub
[20:26] <ribru> jhodapp: if that silo had been left assigned, and the rtm silo freed, citrain would automatically fall back on syncing from the archive in that case
[20:27] <ribru> jhodapp: ok, fill out the package list as needed
[20:27] <jhodapp> ribru, ok cool
[20:27] <ribru> jhodapp: just make sure it starts with 'sync:ubuntu-rtm,14.09 '
[20:27] <jhodapp> awesome, thanks
[20:27] <ribru> jhodapp: you're welcome. and ping me when done, I can assign
[20:27] <jhodapp> ribru, sounds good
[20:27] <ribru> sil2100: lol @ channel topic
[20:30] <jhodapp> ribru, ok it's ready
[20:33] <ribru> jhodapp: https://ci-train.ubuntu.com/job/prepare-silo/3046/console hmm there's a couple silos that conflict
[20:34] <jhodapp> ribru, hmm, I know about the qtubuntu-media one but let me check th qtvideo-node
[20:35] <jhodapp> ribru, oh that's Mirv's qt landing silo which he says to ignore
[20:35] <ribru> oh right, sorry I didn't check that
[20:35] <ribru> ok, will override
[20:35] <jhodapp> ribru, the other one is my silo so let's override
[20:35] <ribru> jhodapp: ok, vivid 9
[20:35] <jhodapp> ribru, thanks!
[20:36] <ribru> jhodapp: you're welcome
[20:36] <ribru> bfiller: please approve: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-006-2-publish/24/console
[20:47] <bfiller> ribru: fixed silo 6 MR, can be published again
[20:48] <ribru> bfiller: oh heh, isn't that the one you were rebuilding with the new mr? just saw 'you can publish' in the dashboard, is it too early to publish?
[20:51] <bfiller> ribru: right good point, this needs to go back through QA
[20:51] <ribru> bfiller: heh, good catch.
[20:51] <bfiller> ribru: retesting it now
[20:52] <ribru> bfiller: thanks
[20:52] <om26er_> whats up with the 'i' ?
[20:53] <ribru> lol
[20:56] <ribru> tedg: you got 14, 16, and 21
[20:57] <tedg> ribru, Awesome, thanks!
[20:57] <ribru> tedg: you're welcome!
[21:01] <tedg> ribru, One more please
[21:01] <ribru> tedg: greedy! ;-)
[21:01] <tedg> Cleaning house on MRs!
[21:02] <tedg> Turning charles into a professional reviewer :-)
[21:02] <ribru> tedg: sweet. vivid should be easy to land without qa
[21:02]  * tedg has no comment
[21:02] <charles> lol
[21:11] <jhodapp> ribru, forgot one package in the list, can your reconfigure vivid silo 9 please?
[21:11] <ribru> jhodapp: sure
[21:12] <ribru> jhodapp: good to go
[21:13] <jhodapp> thanks
[21:27] <ribru> WAT
[21:29] <ribru> well i'll be...
[21:29] <ribru> jhodapp: looking into that unhandled exception. i thought I fixed that issue already
[21:39] <ribru> jhodapp: https://launchpadlibrarian.net/189020256/buildlog_ubuntu-vivid-amd64.qtubuntu-media_0.7.1%2B14.10.20141031~rtm-0ubuntu1_FAILEDTOBUILD.txt.gz looks like you have a build failure to fix. missing package to sync maybe?
[21:55] <ribru> tedg: https://ci-train.ubuntu.com/job/ubuntu-landing-021-2-publish/12/console please approve your merge
[21:56] <tedg> ribru, On it, resubmitted MR :-/
[22:00] <tedg> ribru, All clear
[22:07] <brendand> ogra_, is there going to be a fresh image tomorrow morning to look at?
[22:27] <ribru> rsalveti: so line 100 comment says it's a sync but the configuration is not actually set up to sync anything.
[22:27] <Saviq> brendand, hey, I've packages built out of tvoss's https://code.launchpad.net/~thomas-voss/media-hub/disconnect-signal-translation-layer-on-destruction/+merge/240413
[22:27] <rsalveti> ribru: that's because I'm not yet sure if we want to do binary syncs still
[22:27] <rsalveti> or just src package sync (building for rtm)
[22:27] <Saviq> brendand, is there anyone around who could test to verify that fixes the unity8 crasher?
[22:28] <Saviq> I was unable to crash it for a while now
[22:28] <ribru> rsalveti: the default thing for citrain to do is a source package sync from rtm
[22:28] <rsalveti> ribru: right
[22:28] <brendand> Saviq, i can send a call for testing out to my team
[22:29] <brendand> Saviq, or do you want a quick answer?
[22:29] <Saviq> brendand, no, rather a verify
[22:29]  * Saviq uploads the packages
[22:29] <ribru> rsalveti: so your manual way is only necessary if you want to manually choose the version number, which I suppose is reasonable.
[22:29] <rsalveti> yeah, still thinking
[22:30] <rsalveti> let me get some food first
[22:30] <rsalveti> wait it land properly on vivid
[22:31] <Saviq> brendand, here are the packages http://people.canonical.com/~msawicz/unity8/media-hub/
[22:32] <Saviq> brendand, I've been using trigger-sds.sh from http://bazaar.launchpad.net/~unity-api-team/unity-notifications/trunk/files/head:/examples/
[22:32] <Saviq> brendand, that triggers multiple consecutive snap decisions
[22:32] <Saviq> brendand, I was rarely able to go past the first one
[22:32] <Saviq> brendand, with the packages I sent, not a single crash
[22:37] <veebers> ogra_: you have a moment?
[23:06] <tedg> ribru, Can I get a silo for line 99 please?
[23:07] <ribru> tedg: ok, vivid 3
[23:09] <tedg> ribru, great, thanks!
[23:09] <ribru> tedg: you're welcome!