[00:06] <retoaded> balloons, I may or may not be able to help you
[00:06] <retoaded> depending upon the nature of your query
[00:07] <retoaded> and timezones don't suck as long as you are in the right one
[00:09] <balloons> retoaded: :-) I appreciate the offer. I'm concerned about what's happening with the clock app runs
[00:10] <retoaded> balloons, ahhhh, not really my area but I can take a peek (as long as it's note code related).
[00:14] <balloons> retoaded: yea, I think this might be something to ask tomorrow
[00:15] <retoaded> balloons, ack
[00:15] <balloons> retoaded: if you can confirm the runners look fine, I think that's enough.
[00:15] <retoaded> balloons, where are the runners located?
[00:16] <balloons> retoaded: http://91.189.93.70:8080/computer/
[00:16] <balloons> they look fine and run for the other core apps.. sadly it's not a quick fix I thought it was anymore
[00:16] <balloons> retoaded: oO http://91.189.93.70:8080/job/mediumtests-trusty-slave-reboot/
[00:17] <balloons> thatt's cool, so you have a reboot job :-0
[00:17] <retoaded> balloons, ok, I don't think I have much access to that one. I need to fix that one of these days
[00:17] <balloons> or perhaps it's not what i think it is.. regardless. ty
[00:17] <balloons> no worries. ttyl
[00:18] <retoaded> ack
[08:01] <thostr_> good morning
[08:01] <thostr_> could anybody publish silo 3?
[08:42] <sil2100> thostr_: hi
[08:42] <thostr_> sil2100: hi, in hangout right now...
[08:42] <sil2100> thostr_: so, regarding indicator-network - robru confused everything up ;/
[08:43] <sil2100> thostr_: there was no indicator-network landing because there were no changes to release
[08:43] <sil2100> thostr_: so I'm not sure what he was trying to rebuild and release ;/
[08:43] <thostr_> sil2100: mhhh, ok. so what needs to be done now?
[08:43] <sil2100> Nothing, I published everything that was needed yesterday
[08:43] <sil2100> Not sure what robru wanted to accomplish?
[08:46] <didrocks> and robru used overrides as well :/
[08:46] <didrocks> so, everything is screwed, we don't have the metadata that we use (the branch is still in trusty-proposed, but well…)
[08:47] <sil2100> Ok, now this is confusing - so in the end what did he do? Did he just re-build the silo, or tried to re-publish it?
[08:48] <didrocks> not sure what he tried to do…
[08:48] <didrocks> sil2100: just look at job history
[08:50] <didrocks> he tried to republish
[08:50] <sil2100> I see 'ignore missing' he set
[08:50] <didrocks> yeah
[08:50] <didrocks> not sure what he tried to do at all…
[08:51] <didrocks> thostr_: the packages were migrating, did anything happen/did you ask him to do anything?
[08:51] <didrocks> http://162.213.34.102/job/landing-005-2-publish/18/console was pretty clear that it was already published :/
[08:52] <didrocks> at least, the publication published nothing
[08:52] <thostr_> didrocks: yes, but there was still a strange error message in the ci sheet
[08:52] <thostr_> didrocks: now, I'm really lost there
[08:52] <didrocks> http://162.213.34.102/job/landing-005-3-merge-clean/11/console
[08:52] <didrocks> thostr_: that was your error ^
[08:53] <didrocks> thostr_: which is legit, it's telling you indicator-network was not built at all, and you set it in the configuration
[08:53] <didrocks> thostr_: if you look at the build job, it told you why it didn't build it:
[08:53] <thostr_> waht I got yesterday was something like v
[08:53] <thostr_> "jettisoned without merging"
[08:54] <didrocks> 2014-02-17 18:02:46,091 INFO [08:54] <didrocks> …
[08:54] <didrocks> 2014-02-17 18:03:08,820 INFO No new useful revision published compared to dest, no need to upload this component
[08:54] <didrocks> thostr_: that was someone putting that in the comment
[08:54] <thostr_> ah
[08:54] <didrocks> thostr_: not in the status field AFAIK
[08:54] <didrocks> so you proposed indicator-network, which introduce no change
[08:54] <sil2100> I guess robru forgot or didn't know about this corner-case
[08:54] <didrocks> sil2100: and didn't try to understand :/
[08:54] <thostr_> so, should I now just rebuild and before remove the network=iindicator MP?
[08:55] <didrocks> thostr_: no, there is some way to ignore that
[08:55] <didrocks> so, what you should have done
[08:55] <didrocks> is
[08:55] <sil2100> Yeah... since why did he publish the second time when he could have already noticed that the silo doesn't have indicator-network for the second time
[08:55] <didrocks> telling "ok, I know some projects are missing, that's on purpose"
[08:55] <didrocks> IGNORE_MISSINGPROJECTS
[08:55] <didrocks> Ignore if some projects that are going to be merged back were not published. No merge will then be processed for those
[08:55] <didrocks> thostr_: this is the flag for that case ^
[08:56] <thostr_> that's when building the project
[08:56] <thostr_> but what do I do now?
[08:56] <didrocks> thostr_: that was when merging
[08:56] <didrocks> now, robru removed the whole state
[08:56] <didrocks> the only way is to free the silo
[08:56] <didrocks> set landed manually
[08:56] <didrocks> and bzr pull lp:~ps-jenkins/<component>/trusty-proposed && bzr push <trunk>
[08:57] <didrocks> for every component that were released
[08:57] <thostr_> am I supposed to do that now?
[08:57] <didrocks> thostr_: yeah
[08:58] <didrocks> well "now" == when you have time to reconciliate the trunk
[08:58] <didrocks> we are going to free the silo for you meanwhile
[08:58]  * didrocks runs merge and clean with ONLY_FREE_SILO
[08:58] <didrocks> and set "Landed" to the spreadsheet
[08:58] <didrocks> sil2100: does this make sense to you? ^
[08:59] <sil2100> didrocks: ok, right... since normal merge and clean would miss one revision?
[08:59] <sil2100> I mean, release
[09:00] <sil2100> Ok, right
[09:00] <sil2100> didrocks: let's do it
[09:00] <didrocks> sil2100: well, he destroyed the whole bzr branches
[09:00] <sil2100> didrocks: should I do the pulling and pushing?
[09:01] <didrocks> sil2100: you can, please keep thostr_ in touch
[09:01] <didrocks> sil2100: look at your publish job
[09:01] <didrocks> you have the url to the branches
[09:02] <sil2100> didrocks: ACK
[09:02] <sil2100> thostr_: I'll do some bzr push magic on your projects now
[09:02] <thostr_> sil2100: great, thanks!!!
[09:03] <didrocks> thostr_: all the confusion (and people using overrides without knowing…) was due to indicator-network added to the list without having anything to flush. Can you check this doesn't reproduce please?
[09:03] <didrocks> this is the second time from your team btw
[09:03] <didrocks> the system tries to only rebuild if it's needed (which is available through an option as well)
[09:29] <sil2100> didrocks: I'll be in the meeting in like 1-2 minutes
[09:32] <didrocks> ogra_: around?
[09:32] <sil2100> ogra_: meetonng
[09:32] <ogra_> oops
[09:36] <didrocks> thostr_: we have a unity-scope-loader crash (not reliably though): http://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-daily/54/artifact/clientlogs/camera_app/_usr_bin_unity-scope-loader.32011.crash/*view*/
[09:37] <didrocks> do you mind having a look at that as we landed a new version?
[09:37] <ogra_> thostr_, the list of changes is at http://people.canonical.com/~ogra/touch-image-stats/20140217.1.changes
[09:42] <thostr_> ogra_: looking
[09:54] <thostr_> didrocks: the crash report is useless... we haven't changed that code in ages, all recent scopes changes are only applying to new scopes framework
[09:55] <thostr_> and the new scopes don't utilize that unity-scope-loader any more
[09:55] <didrocks> thostr_: ok, so let it die in limbos
[09:56] <thostr_> didrocks: yes
[10:02] <ogra_> thostr_, if it is not used, what keeps it in the image then ?
[10:02] <ogra_> (it is not seeded)
[10:02] <thostr_> ogra_: it's still used today
[10:02] <ogra_> ah, k
[10:02] <thostr_> but will go away when we switch to new scopes (probably next week)
[10:02] <ogra_> right, understood
[10:32] <sil2100> ;)
[10:36] <ogra_> didrocks, maguro doesnt look good
[10:36] <ogra_> unity hangs hard for me, some click apps seem not installable
[10:38] <sil2100> WTH
[10:38] <sil2100> hm
[10:38]  * ogra_ reboots 
[10:48] <didrocks> reboots always fix everything :)
[10:50] <ogra_> yeah, doesnt seem to hang anymore
[10:50] <didrocks> ogra_: see, fixed!
[10:50] <didrocks> ship it :)
[10:50]  * didrocks wonders where the icon theme is set…
[10:50] <ogra_> woah
[10:50] <ogra_> the camera on maguro always flickered ...
[10:51] <ogra_> but now it is like a strobe
[10:51] <ogra_> completely unusable
[10:52] <didrocks> asac: maybe we should let people using maguro on the previous image and move on and promote the new one. What was the deprecation plan for this? ^
[10:52] <ogra_> nah, we shouldnt do that
[10:52] <ogra_> are we in a hurry ?
[10:52] <didrocks> you prefer to ship it with a broken camera?
[10:52] <ogra_> else i would propose to wait for QA to get up
[10:52] <asac> question is if anyone will look at the camera issue
[10:52]  * asac doubts it
[10:53] <asac> i dont htink we should promote more "broken" stuff
[10:53] <didrocks> based on the feedback we had with the other issues, I doubt we'll have support
[10:53] <asac> to maguro
[10:53] <asac> rather turn that channel off
[10:53] <didrocks> asac: +1
[10:53] <asac> but would prefer to do that when moving mover
[10:53] <asac> over'
[10:53] <ogra_> asac, that will happen anyway as soon as we switch
[10:53] <asac> lets see where we stand today wrt 4.4 switch
[10:53] <ogra_> which is due this week
[10:53] <didrocks> asac: well, so we can't promote anymore image until we switch with 4.4?
[10:53] <asac> ogra_: right, but do we accept that we dont promote until 4.4?
[10:53] <asac> thats not clear to me yet
[10:54] <didrocks> asac: can you clarify that out with the management?
[10:54] <asac> didrocks: lets wait for the south americans to come on
[10:54] <ogra_> asac, well, i only did phone/sms smoketests the last days ... i dont even know if we didnt promote with a broken cam already
[10:54] <asac> didrocks: management will not take that decision from me :)
[10:54] <asac> ogra_: plz check
[10:54] <asac> ogra_: dont complain about non-regressions :)
[10:55] <asac> that causes confusions
[10:55] <asac> hehe
[10:55] <ogra_> then i cant do any other work
[10:55] <sil2100> So, no promotion today :'( ?
[10:55] <asac> anyone else tested maguro?
[10:55] <asac> dogfooded?
[10:55] <didrocks> asac: nobody else has a maguro around
[10:55] <ogra_> sil2100, i would prefer to get some input from QA
[10:55] <asac> davmor2: :)
[10:55] <didrocks> asac: he's in the US timezone this week
[10:55] <ogra_> which doesnt mean no promotion :)
[10:55] <asac> do you know if old maguro images had camera broken
[10:55] <ogra_> asac, right, once oakland gets up
[10:56] <asac> which is like ... 10h from now :)
[10:56] <ogra_> 5 i think
[10:56] <ogra_> well ... in ~5 they should be available
[10:56] <asac> didrocks: what issues do plague us currently on maguro?
[10:56] <asac> do you know?
[10:56] <ogra_> i dont see why we are in a hurry with promoting
[10:56] <didrocks> asac: the only one I know, apart from tests being broken is what ogra_ told, the camera
[10:57] <ogra_> asac, i had a hard hang when testing ... but that didnt come back afetr a reboot
[10:57] <asac> psivaa: any idea why the demo dashboard shows "syncing" http://ci.ubuntu.com/smokeng/trusty/touch_custom_demo/mako/31:20140218:20140115.1/6657/
[10:57] <psivaa> asac: looking
[10:57] <ogra_> asac, and the camera is definitely bad ... but its over a week ago i tried it the last time
[10:57] <asac> ogra_: so you feel the camera was super stable a week ago?
[10:57] <ogra_> no
[10:57] <asac> or was it always buggy on maguro?
[10:58] <ogra_> it was always flickering
[10:58] <asac> and surely you sometimes ended up in a bogus state from time to time, right?
[10:58] <ogra_> but in a state that you could still use it and actually see the pic
[10:58] <ogra_> today it is like a strobe ... you cant really see the pci (it takes photos still though)
[10:58] <ogra_> *pic
[10:58] <asac> hmm
[10:59] <asac> that phenomenon i had 3 month ago
[10:59] <asac> when i was using maguro
[10:59] <ogra_> i havent had hard hangs in quite a while, but yes, indeed i had some over the last year
[10:59] <asac> sounds like its not a regression
[10:59] <asac> ogra_: cant you downgrade and just use camera all over the house for 10 minutes?
[10:59] <asac> :)
[10:59] <asac> you could show me pics of your livingroom, cats, etc. :)
[10:59] <asac> lol
[10:59] <ogra_> well, it regressed as in it flickers so badly that it makes the app unusable
[10:59] <asac> ogra_: that could be MIR induced
[10:59] <ogra_> wheres it flickered before but you could still use it
[11:00] <asac> ogra_: ok, try comparing to last promotion
[11:00] <ogra_> *whereas
[11:00] <asac> thats all that matters :)
[11:00] <asac> guess no need to hurry as we are unlikely to take steps to address/fix this issue. just support decision what to do with maguro going foward
[11:00]  * ogra_ puts the bootspeed work aside and installs a new image
[11:01] <asac> yeah sorry :)
[11:01] <ogra_> no worries
[11:08] <psivaa> asac: this appears to be a bug in the dashboard sync script. the results are in 'syncing' state right from the custom_demo builds.
[11:09] <asac> psivaa: kk. please file ticket or whatever to have someone look i guess
[11:10] <asac> as long as results are correct
[11:10] <asac> then its not that important
[11:10] <asac> but still buggy :)
[11:10] <psivaa> asac: yea, filing a bug for it.
[11:10] <psivaa> probably the reason why it's showing 0% on the KPI page
[11:13] <asac> right
[11:13] <asac> thats how i found it :)
[11:13] <asac> wondered whats going on
[11:13] <asac> but then saw "synching"
[11:14] <asac> is mirv on vac?
[11:15]  * asac thinks so
[11:18] <sil2100> asac: yes, he'll be back next week
[11:19] <sil2100> didrocks: can I assign a silo for unity8 now anyway? I guess it won't affect maguro's camera-app I think? ;)
[11:20] <didrocks> sil2100: sure
[11:36] <ogra_> asac, didrocks, so on 188 there is the same fast flicker when i cover the lens or do fast movement, but it isnt there if i hold the camera still and focus on something ... in the latest proposed image it was there all the time
[11:37] <ogra_> oh, and it seems to be completely gone when i lock/unlock the screen with the camera running in 188
[11:39]  * ogra_ upgrades to proposed again to make sure
[11:42] <didrocks> let's see :)
[11:43] <sil2100> geh
[12:06] <thostr_> could anybody reconfigure silo3?
[12:07] <sil2100> o/
[12:09] <sil2100> thostr_: done
[12:16] <didrocks> ok, going for a run, see you later guys
[12:17] <ogra_> asac, didrocks, so the flickering is worse on the new image, but the trick with lock/unlock (that i hadnt discovered before) makes it a bit better at least
[12:25] <didrocks> ogra_: can you ask that in your meeting with rsalveti?
[12:25] <ogra_> sure
[12:25] <didrocks> to know if he has time to have a look
[12:25] <didrocks> that will help to decide I guess
[12:26] <ogra_> he knows about the flickering in general
[12:26] <ogra_> its an issue on the android side
[12:26] <didrocks> ogra_: just to confirm, it's possible to promote images per device, right?
[12:26] <ogra_> yes, ugly but possible
[12:26] <didrocks> why ugly, you have to put an hack for that?
[12:26] <didrocks> (IIRC, you have a for … in loop)
[12:27] <ogra_> no, it is just ugly to have one device released with known bugs that got fixed in other images on other devices
[12:27] <ogra_> we usually dont do that
[12:27] <ogra_> technically it isnt ugly ...
[12:27] <ogra_> but it breaks an established philosophy
[12:28] <ogra_> but given that the device will fully vanish from the channel by end of the week and not be installable at all anymore then i'm not even sure we should bother
[12:29] <didrocks> yeah, that's why I think it's acceptable (due to the vanishing)
[12:29] <ogra_> (with holding it back)
[12:29] <didrocks> but let's see what rsalveti is able to tell (I'm sure he's more focused on mwc and 4.4)
[12:29] <ogra_> right
[12:30] <ogra_> and we shouldnt distract him to much ... to get that done
[12:30] <didrocks> right
[12:30] <didrocks> but let's get a confirmation first
[12:31] <ogra_> popey, on your flo, could you check the last three lines of ~/.bashrc ?
[12:32] <popey> export GRID_UNIT_PX=20
[12:32] <ogra_> i wonder if something went wrong with the patch that forces landscape ... and thus you get wrong default values for the resolution
[12:32] <popey> export QTWEBKIT_DPR=2.5
[12:32] <popey> export NATIVE_ORIENTATION=portrait
[12:32] <popey> oh nope
[12:32] <popey> thats manta
[12:32]  * popey untangles usb cables
[12:32] <ogra_> hmm, the first one should be 21 i think
[12:32]  * ogra_ chacks the code
[12:32] <popey> fi
[12:32] <popey> export GRID_UNIT_PX=21
[12:32] <popey> export QTWEBKIT_DPR=2.5
[12:32] <popey> ^^ thats flo ogra_
[12:33] <ogra_> ah, then it is right
[12:33] <ogra_> you shouldnt get these giant icons with a value of 21 though
[12:34] <ogra_> hmm, but you should have NATIVE_ORIENTATION=landscape in there too with the latest image
[12:34] <popey> i fudged that into /etc/environment iirc
[12:34] <ogra_> ah
[12:34] <popey> yes, i did
[12:35] <popey> i need to apt-get update this one for latest demo unity
[12:35] <ogra_> it is in /etc/ubuntu-touch-session.d/flo.conf now
[12:35] <popey> groovy
[12:35] <popey> nexus 4 still dead ☹
[12:36] <ogra_> btw, i think we need to re-runn all the AP tests to make sure landscape doesnt break anything
[12:36] <ogra_> popey, try detaching the battery cable
[12:39] <ogra_> asac, ^^^
[12:40] <ogra_> (we should be re-testing in protrait on flo)
[12:40] <ogra_> err
[12:40] <ogra_> landscape
[12:42] <popey> ogra_: what? take it apart?
[12:42] <ogra_> popey, yes
[12:42] <ogra_> not that hard
[12:42] <popey> k
[12:43] <ogra_> there is only one cable ... underneath a metal brace you have to unmount first
[12:43] <ogra_> and all howtos i read suggested to leave the brace off when re-assembling it since it can cause unwanted grounding somewhere
[12:43] <ogra_> i havent had any issues with mine since
[12:56] <popey> ogra_: back off, unplugged, replugged battery, back still off, plugged in usb, flashing red light \o/
[12:56] <popey> (that's good right?)
[12:56] <ogra_> yay
[12:56] <ogra_> yep, it is
[12:56] <popey> thanks
[12:56] <ogra_> leave it charging
[12:56] <popey> k
[12:57] <ogra_> it should come out of that state on its own
[12:57] <ogra_> if it doesnt, 5min button press should help
[13:33] <asac> ogra_: yeah, however, we have never done that before, so would be good for now to check whats up with the APs
[13:34] <ogra_> right
[13:35] <ogra_> gah
[13:35] <ogra_> so why did my flo come up in portrait now
[13:35] <ogra_> root@ubuntu-phablet:/# tail -3 /home/phablet/.bashrc
[13:35] <ogra_> export GRID_UNIT_PX=21
[13:35] <ogra_> export QTWEBKIT_DPR=2.5
[13:35] <ogra_> export NATIVE_ORIENTATION=landscape
[13:36] <ogra_> hmpf
[13:37] <asac> ogra_: maybe root session needs that env?
[13:37] <ogra_> or we need something from the PPA
[13:37] <ogra_> i just used the daily tarball
[13:37] <ogra_> under the assumption it would work though
[13:40] <asac> ogra_: most likely you need ppa then. yes
[13:40] <asac> hmm
[13:40] <asac> though people said just the env hack was needed in ppa
[13:40] <asac> *shrug*
[13:44] <ogra_> in PPA ... thats the point :)
[13:45]  * ogra_ cares for the images we will push to endusers ... there are enough people looking at the others :) 
[13:50] <pmcgowan> ogra_, seems those vars should be set system wide in /etc/environment or somewhere
[13:51] <ogra_> they are exported by the session manager on session startup
[13:51] <ogra_> the bashrc entries are just for AP
[13:52] <pmcgowan> ogra_, I see
[13:53] <ogra_> its just the easy place to check which values they have after a fresh install
[13:53] <sil2100> didrocks: I'm shocked that the spreadsheet still works ok! Maybe your yesterday's optimization helped?
[14:05] <didrocks> sil2100: not sure, maybe that 5 writing in different cells in a short period of time confuses them
[14:05] <didrocks> sil2100: as it seems to start when we have multiple silos
[14:12] <didrocks> ogra_: while I was running, I was thinking about this: can you open a bug with the camera issue and workaround? If we go on and we promote without maguro, we can still reference and open for contribution
[14:13] <ogra_> i would really like to promote all or not promote all instead of doing poecemeal
[14:13] <ogra_> *piecemeal
[14:18] <mardy> didrocks: hi! In Online Accounts, we have a few merge proposals which have been merged into trunk, but have not landed yet. This week we started with the CI-train; so, do I add these packages to the Landing Asks document or...?
[14:20] <alan_g> cjohnston: Hi, could we enable running the tests as part of https://jenkins.qa.ubuntu.com/job/mir-clang-trusty-amd64-build/ please?
[14:21] <didrocks> mardy: you will be bootstrapped today, so we can flush trunk with an empty MP
[14:21] <sil2100> mardy: hi!
[14:21] <cjohnston> alan_g: please file a bug against ubuntu-ci-services-itself
[14:21] <sil2100> mardy: right, as didrocks said ^
[14:21] <didrocks> ogra_: that doesn't prevent to open a bug whatever decision we take, right? :)
[14:21] <mardy> didrocks, sil2100: thanks, I will!
[14:21] <alan_g> cjohnston: ack
[14:21] <didrocks> mardy: yw ;)
[14:21] <ogra_> didrocks, indeed
[14:22] <mardy> sil2100: BTW, any news about raw 240 in the Landing Asks? (u-s-s-o-a)
[14:24] <sil2100> mardy: we have dropped cu2d already and used it only for specific cases (mostly desktop-only ones), so we'll have to release this with citrain ;)
[14:26] <mardy> sil2100: Ah, OK, will do
[14:59] <mardy> sil2100: does this look OK? https://code.launchpad.net/~mardy/signon/packaging/+merge/206952
[15:00] <mardy> sil2100: I mean, the way that the MP is presented, not the code
[15:02]  * sil2100 looks
[15:04] <sil2100> mardy: hm, I'm not sure if we need to include this info in the project trunks - usually we only provide a wiki page for both the merge policy and test cases ;)
[15:06] <sil2100> mardy: I guess nothing bad would happen if we did though!
[15:07] <mardy> sil2100: I'm following tedg's idea of including that in trunk, and then generate the wiki page automatically
[15:07] <mardy> sil2100: well, half-automatically :-)
[15:08] <tedg> sil2100, The big advantage is that the tests can be reviewed the same time as the feature.
[15:08]  * didrocks likes this idea
[15:08] <sil2100> Indeed
[15:08] <tedg> Not that I'd talk about features so close to feature freeze ;-)
[15:09] <didrocks> mardy: or rather than generating in the wiki page, you can say: "please refer to <file> in trunk"
[15:09] <didrocks> on that wiki page
[15:09] <mardy> kenvandine: are you going to be the "lander" for OA?
[15:09] <tedg> didrocks, The tool does both, it points out how to get it in the wiki page, and then includes it below.
[15:09] <didrocks> ok :)
[15:09] <kenvandine> mardy, i doubt it
[15:10] <tedg> didrocks, I figured I had to do that to keep certain pro-wiki groups happy :-)
[15:10] <didrocks> mardy: upstream is the lander, for all your team, I guess it's dbarth
[15:10] <didrocks> tedg: interesting… ok :)
[15:12] <mardy> kenvandine: OK; and what about the code reviews? I can ask alex-abreu, if you prefer
[15:12] <dbarth> kenvandine, didrocks: hi
[15:13] <alex-abreu> dbarth, an say: "please refer to <file> in trunk"
 on that wiki page
[15:13] <alex-abreu> oops
[15:13] <dbarth> in the case of mardy's landing
[15:13] <alex-abreu> dbarth, https://code.launchpad.net/~abreu-alexandre/qtcreator-plugin-ubuntu/add-inspector-option-to-html5-run/+merge/206955
[15:13] <dbarth> we have a dependency noted in the ci pipeline to land signon-ui in the archive first
[15:13] <dbarth> kind of stuck between 2 worlds
[15:13] <dbarth> alex-abreu: sweet
[15:14] <didrocks> dbarth: why stuck between 2 worlds, you will land signon-ui as well, right?
[15:14] <alex-abreu> mardy, which review?
[15:14] <didrocks> for me, that's part of the whole "webapps team" responsability, right?
[15:17] <kenvandine> that should go in the same silo right?
[15:17] <didrocks> yeah, it's a possibility
[15:18] <mardy> alex-abreu: for instance, https://code.launchpad.net/~mardy/signon/packaging/+merge/206952
[15:18] <mardy> alex-abreu: but the question is also about all the future MP which I'll create :-)
[15:19] <didrocks> sil2100: I think with the bootcamp, I won't be able to do the evening meeting + email, can you cover me?
[15:19] <mardy> kenvandine: what is a silo? I've been hearing this word many times, but I'm not sure what that means in the CI-train context
[15:20] <sil2100> didrocks: ok, sure ;) Will try that - just to make sure, we didn't promote any image today due to the maguro issues, right?
[15:20] <didrocks> sil2100: well, I guess ogra_ will have more info from rsalveti. No promotion yet. You can mention though the crash that we ignore and the work on barry's crash
[15:21] <kenvandine> mardy, the ci train gives you a landing silo, which includes a PPA where all the components of the landing get published
[15:21] <kenvandine> for review and testing
[15:21] <alex-abreu> mardy, I could help w/ the reviews if you want
[15:21] <sil2100> didrocks: right, Barry still didn't answer, seems not to be around
[15:21] <sil2100> Not sure what JFDI means
[15:21] <sil2100> ;)
[15:21] <mardy> alex-abreu: thanks; I guess that means that you should join the ~online-accounts team
[15:22] <didrocks> heh :)
[15:22] <didrocks> kenvandine: I got feedback from a lot of native speaker even who didn't know what a silo represents in fact
[15:22] <didrocks> if I knew, I would have just called it cylon :p
[15:22] <alex-abreu> mardy, will you be my manager?
[15:22] <mardy> kenvandine: if that means that a failure in one of the packages means that the whole bunch is rejected, I'd rather have OA in a different silo, as OA and webapps have very few contact points
[15:22] <kenvandine> yeah... silo is a good term for it though
[15:23] <didrocks> kenvandine: of course it's a good one… because it exists in French! :)
[15:23] <kenvandine> mardy, no... the silo should contain all the components that need to change for the landing
[15:24] <mardy> kenvandine: OK, then it doesn't seem to be harmful to be in the same one :-)
[15:24] <didrocks> mardy: silo != stack. stacks were stucked together forever
[15:24] <didrocks> mardy: silo is dynamic, it's per landing
[15:24] <kenvandine> mardy, it's just for the one landing
[15:24] <didrocks> so, you can say
[15:24] <didrocks> "I'm going to land a new Mir"
[15:24] <didrocks> then, you get a silo with mir + unity-mir + platform-api + unity-system-compositor + xorg
[15:24] <didrocks> for instance
[15:24] <didrocks> (real use case)
[15:25] <didrocks> then, you want to introduce a new sensor capability
[15:25] <ogra_> rsalveti, with todays -proposed image the maguro camera turned into a strobe, the flickering got a lot worse, there are discussions if we should block promotion on it or not
[15:25] <didrocks> so, you will get a silo with platform-api + qtubuntu-sensors
[15:25] <didrocks> and so on
[15:25] <didrocks> like, there is an incoming breakage in the theme, we'll bundle system-settings + unity8 + ubuntu-themes
[15:25] <didrocks> for that landing
[15:26] <mardy> didrocks: I see... so the silo could contain also packages not maintained by my team (for instance, if I want to land new versions of OA and friends-app at the same time)?
[15:26] <didrocks> mardy: yeah, as long as you are a lander and nobody else is trying to land friends-app as well, you get a lock to this landing
[15:26] <mardy> didrocks: cool
[15:27] <didrocks> mardy: so, I mentionned components, but the silo is made of MPs actually
[15:27] <didrocks> (which defines the impacted components of course)
[15:28] <mardy> didrocks: when do you decide to which silo a MP goes to? Does it need to be specified at the same time when the MP is created, or can it be done later (and how)?
[15:28] <didrocks> mardy: it's later, and that's exactly what the bootcamp is about
[15:28] <didrocks> to explain how to do that and so on
[15:28] <mardy> didrocks: ah, that Drive document
[15:29] <didrocks> yep :)
[15:29] <didrocks> then, we (the landing team) we assign a silo
[15:29] <didrocks> and then, you can work there
[15:29] <didrocks> knowing that assign == getting a lock on those components
[15:29] <didrocks> (and we assign depending on the image health as well)
[15:38] <cyphermox_> didrocks: I'd assign 18
[15:39] <didrocks> cyphermox_: sounds good!
[15:40] <didrocks> cyphermox_: btw, no spreadsheet issue yet
[15:42] <rsalveti> ogra_: the camera was always bad
[15:42] <rsalveti> ogra_: might just be worse with nested
[15:43] <ogra_> rsalveti, it got worse
[15:43] <ogra_> it got worse over the last 4 images
[15:43] <rsalveti> what changed for it to be worse?
[15:43] <ogra_> its a strobe
[15:43] <ogra_> flickers much more and faster
[15:43] <rsalveti> the camera-app did change, but we also got unity/mir changes as well
[15:43] <ogra_> i can calm it when locking/unlocking
[15:43] <ogra_> right
[15:44] <rsalveti> ogra_: can we try to disable nested easily to see?
[15:44] <ogra_> the question was can we promote with that or not
[15:44] <ogra_> (given maguro is hopefully gone by end of the week)
[15:45] <ogra_> rsalveti, image 188 is usable ... the flicker is there but not as bad as on 190
[15:45] <ogra_> it flickered like on 188 even before nested, i dont think it changed much there
[15:45] <rsalveti> ogra_: landscape mode is still a ppa only thing
[15:45] <ogra_> yeah, i noticed
[15:46] <rsalveti> ogra_: what changed between 188 and 190?
[15:46] <rsalveti> let me charge mine
[15:46] <ogra_> new unity mostly
[15:46] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20140217.1.changes
[15:47]  * ogra_ thinks http://people.canonical.com/~ogra/touch-image-stats/20140218.changes is irrelevant ... 
[15:50] <rsalveti> ogra_: libunity?
[15:51] <ogra_> yeah, probably
[15:51] <ogra_> rsalveti, the question is do we want to put any effort in ...
[15:51] <ogra_> just collecting opinions
[15:51] <rsalveti> well, it was kind of useful before
[15:51] <rsalveti> if it is indeed broken now, I believe we should still try to put some effort to get it fixed
[15:51] <ogra_> it always flickered and was hard to focus with the flicker
[15:52] <rsalveti> if it's flickering way more than before, it probably also means it's rendering way more
[15:52] <ogra_> most likely, yes
[15:53]  * rsalveti flashing 190
[15:55] <cyphermox_> didrocks: I got an error saying landing-008 was lready assigned, but it looks like things worked anyway
[15:56] <didrocks> cyphermox_: hum, where did you get that error, on the spreadsheet?
[15:56] <cyphermox_> yup
[15:57] <sil2100> hm
[15:57] <sil2100> cyphermox_: what did you want to assign to 008?
[15:57] <sil2100> gsettings-ubuntu-touch-schemas ?
[15:58] <cyphermox_> sil2100: yeah, line 18
[15:58] <cyphermox_> it
[15:58] <cyphermox_> it's done
[15:58] <didrocks> sil2100: cyphermox_: seb128: please don't run it
[15:58] <didrocks> I'll use it as an example
[15:58] <didrocks> for the bootcamp :p
[15:58] <cyphermox_> yup yup
[15:58] <sil2100> cyphermox_: indeed, I see it in the backend as well
[15:58] <sil2100> didrocks: ok ;)
[15:59] <didrocks> thanks
[16:01] <seb128> didrocks, you got lucky, I was about to run it, thanks
[16:01] <didrocks> thanks for being the example provider :p
[16:02] <seb128> yw ;-)
[16:06] <Laney> seb128: weren't you going to wait for the consumer half to be ready to land it all together?
[16:08] <seb128> Laney, it's blocking testing for others (or they would have to do local builds/set up a ppa)
[16:08] <seb128> Laney, so I decided to just go ahead to help those guys land
[16:08] <ogra_> didrocks, so davmor2 confirmed the camera app is worse for him than with the last promoted image ... lets wait for rsalveti's comments once he is done flashing
[16:08] <seb128> even if we change it, there are no client yet, wouldn't be the end of the workld
[16:09] <didrocks> ogra_: sure
[16:09] <didrocks> sil2100: ^
[16:09] <Laney> seems like something which fits the silo idea properly
[16:09] <sil2100> ogra_, didrocks: ACK
[16:12] <sil2100> robru: same to you - wait with publishing/building stuff
[16:13] <seb128> Laney, if the other side is ready to land yes
[16:13] <seb128> Laney, but unity-control-center is not under daily landing, so it's less convenient
[16:16] <alex-abreu> mardy, btw, assign me the MRs you want me to check ... otherwise I tend to forget
[16:22] <rsalveti> ogra_: yeah, it's really bad
[16:22] <rsalveti> it seems unity8 is rendering quite a lot more than before
[16:23] <ogra_> right
[16:23] <ogra_> obviously just in the latest iteration though
[16:23] <ogra_> which landed in 189
[16:30] <rsalveti> we can try to revert libunity and see
[16:31] <rsalveti> but it might not be that easy to find the culprit here
[16:36] <thomi_> hey fginther, I see you're working on the AP-docs-upload job?
[16:36] <fginther> thomi_, yes
[16:37] <fginther> thomi_, it's been a pain if you can't tell
[16:37] <rsalveti> ogra_: the complicated thing is that any parallel unity8/mir rendering will cause the screen to flash
[16:37] <thomi_> fginther: OK, just wanted to make sure you were aware of the failures (I'm getting emails, but that's OK)
[16:37] <rsalveti> ogra_: just bring down the indicator and you'll see
[16:37] <fginther> thomi_, oh, sorry about that. I'll let you know when I think I have it working again. Please ignore those until then
[16:38] <thomi_> fginther: no worries!
[16:38] <ogra_> rsalveti, didnt bring my maguro to the camp :/
[16:38] <ogra_> rsalveti, willy try once i'm back downstairs
[16:38] <rsalveti> ogra_: so something caused unity8/mir to render a bit more frames than usual
[16:38] <ogra_> right
[16:38] <rsalveti> ogra_: and that might be very hard to debug, so I don't think we should be blocked
[16:38] <ogra_> which i assume makes it appear snappier
[16:38] <sil2100> hmm
[16:39] <ogra_> right
[16:39] <rsalveti> ogra_: not necessarily, it shouldn't be doing any extra rendering besides the camera-app
[16:39] <rsalveti> ogra_: as it's in full screen mode
[16:39] <rsalveti> maybe something Saviq can help as well
[16:39] <ogra_> yeah
[16:41] <rsalveti> ogra_: video playback should be as bad as camera now
[16:41] <rsalveti> let me put a video to see
[16:41] <ogra_> ah, i didnt test that
[16:41] <ogra_> we literally only did very vague smoketesting the last few rounds
[16:41] <balloons> ping doanac
[16:41] <rsalveti> jezz, maguro is really slow with mir
[16:41] <doanac> balloons: hey
[16:42] <ogra_> like making call/sms and install a click packge and start it
[16:43] <balloons> doanac: so I have some things for you to look at. The clock app is acting funny in the jenkins builder, and I was spending some time last evening trying to figure out what was up. Essentially all the tests fail because the app fails to launch
[16:43] <rsalveti> ogra_: video playback gets easily stuck with mir
[16:44] <Saviq> ogra_, rsalveti, we should not be rendering more, what's the issue?
[16:44] <balloons> doanac: so I assumed it's clock's fault and tested trunk. That recorded the same error. So then I tried an earlier version before some changes from weeks ago I thought might be causing the delay. That also failed the same way
[16:44] <ogra_> Saviq, maguro has lots of new issues with that
[16:44] <rsalveti> Saviq: camera-app with latest image on maguro is flashing like crazy
[16:44] <balloons> here's an example of a run: http://91.189.93.70:8080/job/generic-mediumtests-trusty/1348/console
[16:44] <rsalveti> Saviq: so was wondering if that flashing was because unity8 was still rendering in background
[16:45] <balloons> doanac: it *seems* as if something underlying changed that broke things for clock
[16:46] <doanac> balloons: okay. i'll take a look
[16:48] <Saviq> rsalveti, not that I know of
[16:52] <balloons> doanac: so essentially, I'm not sure the easiest way for you to rollback some of the dependencies for clock and re-running the app until we discover what changed that broke it.
[16:54] <doanac> balloons: yeah. i'll have to poke around for a bit to have any ideas. i've opened a task for the team and am digging into it now though.
[17:17] <sil2100> ogra_, rsalveti: so, any news on a promotion? Or still questioned? ;)
[17:34] <sil2100> Ok, I need to drive home now
[17:35] <ogra_> sil2100, the bootcamp is running long, sorry
[17:35] <ogra_> lets keep promotion for tomorrow morning
[17:35] <sil2100> ogra_: sure ;)
[17:35] <sil2100> Good luck guys!
[17:42] <dobey> fginther: ping
[17:58] <sergiusens> didrocks, can we block landings for gallery and camera?
[18:00] <robru> didrocks, i can't assign silos... popup just comes up blank
[18:00] <didrocks> sergiusens: you want to land one?
[18:01] <didrocks> that's why you want to not land it
[18:01] <didrocks> (/me needs to run out)
[18:01] <sergiusens> didrocks, I have that mega landing; but I don't want people to skew the autopilot tests in the meantime
[18:01] <didrocks> robru: maybe another google outrage?
[18:01] <didrocks> sergiusens: ok, easy, we won't assign silos for those
[18:01] <didrocks> robru: cyphermox_: please don't assign silo for gallery and camera
[18:01] <sergiusens> didrocks, great, bfiller's landing is waiting from one MR from unity8 guys to be reviewed
[18:02] <sergiusens> thanks
[18:04] <didrocks> excellent, thanks sergiusens :)
[18:04] <didrocks> sergiusens: let me write it down to remember tomorrow morning
[18:04] <didrocks> (done)
[18:05] <robru> didrocks, cyphermox_: if you guys click 'assign to silo' what happens? do you get the popup? i get the popup but it's blank. doesn't even have the link to the prepare job
[18:05] <didrocks> robru: yeah, the script is taking more than 5s to run
[18:06] <didrocks> robru: I would say another google outrage, you should assign it manually
[18:06] <didrocks> with the 2 columns
[18:06] <robru> didrocks, oh, it seems to work in chromium but not firefox :/
[18:06] <didrocks> interesting…
[18:06] <didrocks> nothing changed, so I would say slower backend
[18:07] <robru> didrocks, there is a noticable delay before it pops up in chromium, but firefox it just never shows up
[18:07] <didrocks> ok, I think you just hit the 5s barriers
[18:07] <didrocks> and google has an issue on the apps scripts backend
[18:07]  * didrocks goes now
[18:07] <didrocks> robru: see you tomorrow!
[18:07] <robru> didrocks, bye
[18:13] <fginther> doanac, pong
[18:13] <doanac> fginther: hey
[18:35] <fginther> doanac, sorry, misfire
[18:35] <fginther> dobey, pong
[18:36] <dobey> fginther: hi. is https://code.launchpad.net/~dobey/tarmac/list-approved/+merge/206808 what you wanted for the "list approved merges" feature?
[18:37] <fginther> dobey, I'll take a look and get back to you
[18:37] <fginther> thanks
[18:37] <dobey> ok, thanks
[18:43] <balloons> doanac: any luck?
[18:45] <doanac> balloons: no real progress. just confirmed it seems to be okay on saucy
[18:50] <om26er_> doanac, hey! can you please enable CI for this new source https://launchpad.net/sync-monitor for renato
[18:53] <doanac> om26er_: added to our TODO's.
[19:09] <robru> bregma, you ready for me to SLAM unity7 into the archive?
[19:10] <robru> bregma, here we goooo ;-)
[19:10] <robru> bregma, oh, packaging changes....
[19:10] <robru> that was less dramatic than i'd hoped...
[19:13] <bregma> right, there's change in the default plugins in compiz, I suppose that's a sort of packagingchange
[19:13] <bregma> some day we'll have a landing that's quick and easy
[19:16] <robru> bregma, no worries, got the packaging ack already... and i mostly trust you ;-)
[19:18] <robru> bregma, done! so you got your big-boy pants today right? you can merge & clean when you see these hit distro?
[19:18] <bregma> robru, I can
[19:18] <bregma> when it pleases me to do so
[19:21] <robru> bregma, i think you'll find it's more pleasing the sooner you do it. because the less time you wait on that, the less chance that your next set of feature branches will have merge conflicts against trunk...
[19:22] <bregma> robru, believe me, they're already working on fixing those as we speak
[19:43] <balloons> doanac: any further news? This is holding up landing things for mwc.. :-)
[19:43] <doanac> balloons: i'm trying to get with fginther for help.
[19:57] <balloons> fginther: doanac is there a reason why the jenkins output is so weird as well. Leo was mentioning that the community apps might be missing some of the files that are collected for the internally developed apps
[19:58] <doanac> balloons: what do you mean by weird exactly?
[19:58] <fginther> balloons, yes, they are quite different test environments
[20:00] <balloons> doanac: I mean "weird" as in this case, the test output is a blank xml file, and there are 2 videos.. but in reality everything failed.. the output is just a bit weird. And leo mentioned looking at the crash files, which I don't see on the output, so :-)
[20:02] <fginther> balloons, so the two jenkins environments have completely different test runners, so adding crash files to one, does not translate to the other sadly... Still, this is something that can be added
[20:02] <balloons> fginther: ahh.. I can add a formal bug for that then.. it's not a priority atm, but would be useful for when we see things like this
[20:03] <fginther> balloons, agreed. It would be nice if the two were equivalent from the developers perspective.
[21:23] <balloons> doanac: fginther ping.. any progress?
[21:23] <fginther> balloons, no luck yet, as far as I can tell, the app is hanging
[21:23] <fginther> so no crash dumps
[21:24] <fginther> I also can't figure out what has changed between the last working test run and now
[21:25] <balloons> fginther: doanac reported it ran fine on saucy, not sure how (perhaps a saucy testrunner or ?). I don't think you can easily rollback packages without affecting everything.. could you rollback packages on a one-off builder ?
[21:25] <asac> robru: cyphermox_: what kind of landings are currently ongoing?
[21:25] <balloons> fginther: first canindates are the new ui toolkit and eds
[21:25] <asac> robru: cyphermox_: do you have scopes somewhere in flight?
[21:26] <robru> asac, yes, unity-scope-click should be nearly done
[21:26] <robru> asac, it just hit proposed, will be merged & cleaned soon
[21:27] <robru> asac, other than that, i did a friends-app and an html5-theme and those are both done (silos already cleaned)
[21:27] <asac> alecu: is that your?
[21:27] <asac> robru: ok be extra careful. we try to cut a good demo image tonight/tomorrow moring :)
[21:27] <asac> so dont bust us :)
[21:27] <asac> lol
[21:27] <asac> thx!
[21:27] <robru> asac, no worries
[21:28] <asac> lets if the scopes get good from testing
[21:28] <asac> or otherwise help updating silos in case they need another fix
[21:28] <asac> thx
[21:28] <robru> asac, sure i'm around, just ping me if anything needs help moving along
[21:30] <alecu> ralsina: do you know what is the problem that thostr found on our ppa?
[21:30] <fginther> balloons, I've got it running on trusty (same packages that jenkins builds)
[21:30] <ralsina> robru, asac: we have a bug, if we get a fix I'll rebuild, retest and then we'll see
[21:30] <ralsina> alecu: download fails
[21:30] <ralsina> alecu: at least it fails for him
[21:30] <ralsina> alecu: could be credentials
[21:30] <fginther> balloons, I'll take a closer look at the eds and uitk dependencies
[21:30] <ralsina> alecu: so I am testing
[21:31] <asac> ralsina: so you have a bug in silo 003?
[21:31] <asac> robru: ^^
[21:31] <asac> so guess dont publish that
[21:31] <asac> if the damage isnt done yet
[21:31] <ralsina> asac: that's what thostr said I am checking
[21:31] <robru> asac, wayyyy to late for that! i published silo 3 an hour ago at thostr's request
[21:31] <asac> robru: ok
[21:32] <ralsina> if he asked for it I guess I misunderstood thostr
[21:32] <asac> ralsina: so please deliver the real fix :)
[21:32] <balloons> fginther: ty I appreciate it. We need the set of merges for clock for mwc
[21:32] <ralsina> asac: ack
[21:32] <asac> robru: guess ralsina might need a new silo then after htis is done
[21:32] <balloons> let me know if I can help
[21:32] <asac> to get his fix in
[21:32] <ralsina> right
[21:32] <asac> ralsina: your problem doesnt regress the APs, rght?
[21:32] <ralsina> asac: should not
[21:32] <robru> boiko, landing 27 got silo 1, please build.
[21:32] <ralsina> asac: no AP for this stuff yet
[21:33] <asac> ralsina: right, but it shouldnt regrtess APs either
[21:33] <asac> like unit8
[21:34] <robru> seb128, around? i know it's late for you but gave silo 5 for landing 24
[21:34] <seb128> robru, thanks
[21:35] <boiko> robru: nice! thanks!
[21:35] <robru> ;-)
[21:36] <asac> thanks robru and ralsina. you guys will make it :)
[21:36] <asac> i am sure
[21:36] <boiko> robru: will only be able to test that tomorrow though
[21:36] <robru> boiko, no worries, it's ready for you
[21:36] <robru> ralsina, so just ping me when you get that MP done
[21:38] <fginther> balloons, you should think about a contingency plan if this doesn't get fixed
[21:40] <ralsina> robru: ack, thanks
[21:50] <fginther> balloons, hmmm, I installed qtorganizer5-eds on my local system and now clock-app fails to start. Logs also indicate a new version occurred after the last successful ubuntu-clock-ci test
[21:51] <fginther> balloons, will try removing this from the jenkins environment as a next step
[21:53] <ralsina> asac, robru: the problem seems to be that thostr had no credentials and we are not handling that case. However that should not matter for the demo, so we are not landing more stuff today.
[21:54] <robru> ralsina, so everything's fine and you don't need me?
[21:54] <ralsina> robru: yes
[21:54] <robru> ralsina, great. i'm still around if anything else comes up.
[21:55] <ralsina> robru: awesome
[21:55] <asac> ralsina: what?
[21:55] <asac> so all is fine?
[21:55] <asac> false alert?
[21:55] <asac> nice :)
[21:55] <asac> i like thoswde dragons that fly away
[22:00] <balloons> fginther: excellent, yes, it was on the suspect list, but I couldn't get clock to fail after upgrading/downgrading it last night..
[22:08] <ralsina> asac: well, it's broken but in a way that can be worked around for a demo ;-)
[22:21] <asac> ralsina: ok. can you update the spread with workaround?
[22:21] <asac> thx
[22:21] <asac> and change status
[22:23] <ralsina> asac: sorry, new in this, you mean the landing-003 sheet?
[22:27] <asac> ralsina: /msged you
[22:55] <jdstrand> hey, I'm looking at https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdC05a2ZQSmgwU2NFYnJQOE9qMDRYa3c&usp=drive_web#gid=1 and I need to add a component
[22:56] <jdstrand> I see all these ### Stack ...cfg ### lines, and I don't know what they are
[22:56] <robru> jdstrand, so those are taken from the old cu2d system
[22:56] <jdstrand> so I don't know how to just add something
[22:56] <jdstrand> ok
[22:56] <robru> lp:cupstream2distro-config /stacks/head/*
[22:57] <robru> jdstrand, should be no trouble to just add whatever. those are just there to aid the transition from cu2d.
[22:57] <jdstrand> I don't know what that is. I assume I can ignore it?
[22:57] <robru> cu2d is officially dead today
[22:57] <robru> yes
[22:57] <jdstrand> I see
[22:57] <robru> jdstrand, basically cu2d is the broken old thing that citrain replaces.
[22:58] <jdstrand> I see
[22:58] <sergiusens> robru, hey, can I get a train for 28?
[22:59] <robru> sure
[22:59] <sergiusens> thanks
[22:59] <jdstrand> robru: I think I don't know how to add lines to the spreadsheet
[23:00] <robru> jdstrand, permission problem?
[23:00] <robru> sergiusens, ok, you got 3. need me to click build or can you do it?
[23:00] <jdstrand> robru: can you help? there is this green outline and I'm afraid if I add stuff to the bottom, it won't be added correctly
[23:00] <sergiusens> robru, already doing it :-)
[23:01] <robru> jdstrand, what do you mean 'added correctly'? that spreadsheet is just for manual reference... i'm not aware of anything that examines that programmatically...
[23:01] <sergiusens> thanks
[23:01] <jdstrand> robru: no, I can edit, I am just not sure where to put them
[23:01] <robru> sergiusens, yw
[23:01] <robru> jdstrand, just try to keep things logically related.
[23:02] <jdstrand> robru: sure, but I did 'Add 20 more rows to the bottom' and the rows didn't look right
[23:02] <jdstrand> robru: like, column 'C' didn't have the little gray triangle
[23:03] <robru> jdstrand, probably just pull the corner down to fill in the cells? i don't see your rows.
[23:03] <jdstrand> robru: and they were all outside of the green border under row 279
[23:03] <robru> jdstrand, what are you adding?
[23:03] <jdstrand> robru: I removed them to start over :)
[23:03] <jdstrand> I want to add apparmor, click-apparmor and apparmor-easyprof-ubuntu
[23:04] <robru> jdstrand, are those desktop, phone, or both?
[23:04] <jdstrand> apparmor is both (and server), the other two are phone
[23:05] <robru> jdstrand, do they have any dependencies/ rdepends that are already in the list?
[23:06] <jdstrand> I haven't set all that up for click-apparmor and apparmor-easyprof-ubuntu
[23:06] <fginther> balloons, so far so good, clock tests are now running after removing qtorganizer5-eds
[23:06] <jdstrand> I was trying to get apparmor in there cause I have a landing I'd like to coordinate before FF
[23:06] <jdstrand> they other two I will work on after
[23:06] <jdstrand> but, upstart-app-launch depends on apparmor
[23:07] <jdstrand> so does usermetrics
[23:07] <robru> jdstrand, right, ok. i think we're overthinking this. give me a sec to check something
[23:09] <jdstrand> fyi, if this helps: https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
[23:09] <robru> jdstrand, this is a unique scenario for me; i'm used to disabling apps from cu2d to enable them in citrain. not sure how I would go about enabling something that was never in cu2d...
[23:09] <jdstrand> I see. yeah, I just went through training today and I'm trying to get everything lined up so I can request a landing
[23:10] <jdstrand> so it is all new to me
[23:10] <robru> I wonder if cyphermox_ knows more about this...
[23:10] <robru> jdstrand, ok, so the first thing I'd want to know is if the launchpad project names match the source package names? eg, lp:apparmor contains apparmor source package, etc?
[23:11] <balloons> fginther: woot, ty for rolling that back
[23:11] <cyphermox_> what is it?
[23:11] <fginther> balloons, in this case, it was just a remove
[23:12] <robru> cyphermox_, so jdstrand wants to add some projects to citrain, but they were never in cu2d. how do we handle that? do we have to add them to cu2d with all the "blah: False" lines?
[23:12] <fginther> balloons, clock-app doesn't have a dependency on qtorganizer5-eds, but it was causing problems
[23:12] <balloons> fginther: I *think* calendar was having issues as well
[23:12] <robru> cyphermox_, or can citrain just handle projects that are not referenced under cu2d-config?
[23:12] <cyphermox_> robru: AFAIK you don't need any configuration for citrain
[23:12] <balloons> fginther: ok, well let's land the branches, and sort out why after :-0
[23:12] <cyphermox_> but then you might run into some permission issues
[23:12] <fginther> balloons, ack, I'm working on the rssreader changes als
[23:12] <fginther> also
[23:13] <robru> jdstrand, ok, well in that case then I think we're set...
[23:13] <balloons> fginther: :-)
[23:14] <robru> jdstrand, do you have some MPs right now that are ready to go? i've got time to get you started if you want
[23:14] <robru> jdstrand, at this point I'd recommend just going forward with the landing, and then if it explodes for any reason, responding to those issues as they arise.
[23:14] <jdstrand> robru: well, no, it is complicated with apparmor
[23:15] <jdstrand> this is a new upstream version so everything is already merged in trunk
[23:15] <jdstrand> so for this landing, I was going to do the test plan, and then I have to talk to the apparmor guys about how to do MPs
[23:15] <jdstrand> (I only just got trained today)
[23:15] <robru> jdstrand, that's easy, all you have to do is push trunk to some secondary location, then propose the merge back to trunk (eg, propose a merge with no commits). then citrain can take that "null merge" and make a release out of it
[23:16] <jdstrand> it may be weird cause Canonical doesn't employ all the comitters. anyway, that isn't for right now
[23:16] <jdstrand> I see
[23:16] <robru> jdstrand, well I have a community contributor on friends-app and citrain has been working well for me merging his MPs.
[23:17] <jdstrand> that's fine-- we just need to figure it out (apparmor is multi-distribution, etc). We have the mojority, but there are a number of stakeholders. it might be weird for us to require them to do Ubuntu touch testing to get their MP in, for example
[23:17] <ralsina> robru: ping, I need to land something, it turns out
[23:17] <robru> ralsina, sure thing. got an MP?
[23:18] <ralsina> robru: row 29 in the Self service sheet, https://code.launchpad.net/~diegosarmentero/unity-scope-click/not-progress-actions/+merge/206981
[23:18] <ralsina> robru: it's tiny and harmless
[23:19] <robru> ralsina, ok, you're in silo 6. can you build or do you need me to?
[23:19] <jdstrand> robru: but the short answer to your question is I'm not ready for anywone to review anything right this second, but thanks
[23:19] <jdstrand> I will bring it up in the next meeting
[23:19] <robru> jdstrand, ok no worries. I'm here for at least 3 more hours in case anything changes.
[23:19] <robru> jdstrand, also generally, US west coast, happy to help with landings whenever.
[23:20] <ralsina> robru: I think I can!
[23:20] <jdstrand> robru: thanks!
[23:20] <ralsina> robru: I get no build btton tho
[23:20] <robru> jdstrand, you're welcome.
[23:20] <robru> ralsina, really? weird. i'll just do it then.
[23:20] <jdstrand> robru: you can answer one question-- what is column 'F'-- I'd like to add a note
[23:21] <robru> jdstrand, column F is a free-flow comment/note column
[23:21] <jdstrand> cool
[23:21] <robru> ralsina, ok, building here: http://162.213.34.102/job/landing-006-1-build/31/console
[23:22] <robru> ralsina, merge conflict ;-) please rebase your branch on trunk.
[23:22] <ralsina> ugh
[23:22] <robru> ralsina, ping me once you push the commit and then I can rebuild.
[23:22] <fginther> balloons, the clock tests are working now, the icon change has merged.
[23:22] <ralsina> robru: that dev is EOD, I'll have to do a new branch
[23:23] <robru> ralsina, oh, in that case I'll have to reconfig the silo, just ping me with the new MP address.
[23:28] <ralsina> robru, i gotta run. mmcc wil give you the mp
[23:29] <robru> ralsina, no worries
[23:30] <popey> balloons: fginther lets talk here rather than pming ☻
[23:31] <mmcc> ping robru : ralsina asked me to notify you of this branch being ready for silo landing-006. https://code.launchpad.net/~mikemc/unity-scope-click/remove-dummy-progress-actions/+merge/207066
[23:31] <robru> mmcc, perfect thanks
[23:32] <mmcc> robru: it's a redone branch due to conflicts, was previously reviewed as this MP: https://code.launchpad.net/~diegosarmentero/unity-scope-click/not-progress-actions/+merge/206981
[23:32] <robru> mmcc, ralsina : http://162.213.34.102/job/landing-006-1-build/32/console here's the build progress if you wanna keep an eye on that
[23:33] <mmcc> robru, great, thanks!
[23:33] <robru> mmcc, so when that's done, enable the PPA on your test device, make sure the bug is actually fixed, then I'll publish it. ping me once you're confident it's good
[23:34] <mmcc> robru - ack, will do.
[23:41] <elopio> ping cihelp, can I get an account on this jenkins please? http://91.189.93.70:8080/
[23:43] <sergiusens> robru, might want to disable automerger for lp:thumbnailer
[23:43] <sergiusens> rsalveti, ^^
[23:43] <rsalveti> indeed
[23:43] <rsalveti> just noticed it was already merged
[23:44] <retoaded> elopio, you'll probably need to talk to fginther about the account.
[23:44] <sergiusens> which means we now probably need to trigger a daily release
[23:54] <elopio> fginther, are you around?