[00:01] <robru> sergiusens, i can take care of that, gimme a minute.
[00:01] <robru> sergiusens, no need for daily_release, better to prep a null merge for trunk release.
[00:02] <sergiusens> ok, thanks
[00:05] <robru> sergiusens, ok, that's disabled. future merges should no longer auto-land on trunk.
[00:06] <robru> sergiusens, so if you want to make a release of that now, take trunk and push it to a new location, then propose merging back to itself (eg, a merge with no commits). that MP can be taken to citrain to trigger a release.
[00:08] <jdstrand> robru: question: in the MP Submission Checklist Template, it asks if people built the package in a sbuild/pbuilder chroot. won't jenkins build armhf packages when we do the 'Build' step? and then we can test those?
[00:08] <sergiusens> robru, ack, one sec
[00:08] <sergiusens> robru, this already happened to me :-)
[00:08] <sergiusens> well, not me, but I was there :-P
[00:09] <jdstrand> robru: (ie, with the TestPlan)
[00:11] <sergiusens> jdstrand, that's true; I find this sort of redundant; would be awesome if the build/test could be done with the siloed one
[00:11] <robru> jdstrand, yes, packages will be built for all relevant arches in the silos.
[00:11] <sergiusens> robru, btw; there's some sugar, you can do: bzr branch lp:thumbnailer lp:~sergiusens/thumbnailer/empty
[00:11] <robru> jdstrand, building in a pbuilder is still a good idea to predict problems before jenkins finds them.
[00:11] <robru> sergiusens, oh nice
[00:11] <jdstrand> for sure
[00:12] <jdstrand> that is still on our setup. but we don't have arch-specific code so figure building in one arch is fine for that pre-MP testing
[00:12] <sergiusens> robru, what do I do with silo 3? or should I piggyback on that one?
[00:12] <robru> jdstrand, sure. the template is pretty generic, tailor it to your projects needs
[00:13] <jdstrand> yep, thanks :)
[00:13] <jdstrand> I just wanted to make sure I understood the Build step
[00:13] <robru> sergiusens, silo 3 got published already so that's basically too late...
[00:14] <sergiusens> robru, I added row 30
[00:14] <robru> sergiusens, so thumbnailer is in -proposed now. after it hits release pocket, it needs to be merged & cleaned.
[00:14] <robru> sergiusens, column A should indicate which project it's for
[00:15] <robru> sergiusens, and it can't get a new silo until the old one is clean. so we have to wait a bit here.
[00:15] <sergiusens> robru, do I need this stub landing at all if it's already in proposed?
[00:15] <sergiusens> robru, I thought the description could be anything; I'll mention thumbnailer
[00:16] <sergiusens> fixe
[00:16] <sergiusens> d
[00:16] <robru> sergiusens, description really needs to contain the project name so we know what the hell the landing is for ;-)
[00:17] <robru> sergiusens, I'm not sure what you mean. silo 3 got published so whatever commits were there are in -proposed now. I thought you said there was a new MP that got landed by accident.
[00:17] <robru> sergiusens, was there a different MP than the one from the silo?
[00:19] <sergiusens> robru, the mp in silo got merged before the publish to ppa happened; so the push to the ppa may be bad and I'm not sure what will happen when I try to merge and release the silo
[00:19] <robru> sergiusens, yeah me neither ;-)
[00:19] <sergiusens> robru, project names can be taken from the MRs :-)
[00:19] <robru> sergiusens, let me poke around a bit.
[00:20] <sergiusens> sure, going to have a late dinner so don't be surpirsed if I don't reply for a bit
[00:20] <robru> sergiusens, http://162.213.34.102/job/landing-003-1-build/23/console here is the build log. it shows evidence of a merge having taken place (eg, when the silo build ran, the MP hadnt landed on trunk yet, so it merged into trunk itself).
[00:21] <robru> sergiusens, it looks ok to me actually. lp:thumbnailer and https://code.launchpad.net/~ps-jenkins/thumbnailer/trusty-proposed agree on what 'r65' is. so there should be no conflict to do a merge & clean.
[00:23] <popey> balloons: fginther how we doing?
[00:23] <popey> (not being impatient, just wondered)
[00:29] <balloons> popey: on ?
[00:30] <popey> balloons: the click apps in the store..
[00:30] <balloons> popey: I realized my idiocy and I'm getting a proper chroot going (finally)
[00:30] <balloons> the merges are progressing
[00:30] <popey> sweet
[00:30] <balloons> popey: I believe shorts is all that is left.
[00:32] <balloons> I guess I'll manually land it, not sure fginther is done with the conversion of the naming to shorts
[00:33] <balloons> popey: fginther so we do seem to have an issue. The eds package you backed out for clock to pass, causes calendar to fail; http://91.189.93.70:8080/job/generic-mediumtests-trusty/1391/testReport/junit/calendar_app.tests.test_weekview/TestWeekView/test_show_next_weeks_with_mouse_/
[00:34] <balloons> namely this bug I believe: https://bugs.launchpad.net/ubuntu/+source/qtorganizer5-eds/+bug/1274792
[00:42] <balloons> popey: we can't land calendar without someone to add back in the qt5organizer-eds package to the builder
[00:42] <balloons> ping cihelp
[00:42] <balloons> and when we add it back we need to have everything for clock landed, because we won't be able to land clock once it's back in :-)
[00:43] <popey> balloons: is there a known someone who can do that>?
[00:44] <robru> sergiusens, ok, I merged & cleaned silo 3 for you, just to see what would happen. it was successful, the only snag is that there's now an empty commit on trunk. harmless but ugly. won't happen again now that daily_release is disabled.
[00:46] <balloons> popey: at this hour, I'm not sure
[00:53] <balloons> popey: I think we have a plan, we just need to land clock first now
[00:53] <popey> roger roger
[01:29] <robru> i'm heading out for dinner, but i'll be back in 2-3 hours to do more landings if necessary. just ping and/or email me.
[01:31] <fginther> balloons, I'm back
[02:24] <fginther> balloons, ping
[02:46] <robru> annnnnnnnnd
[02:46]  * robru -> EOD
[02:51] <bregma> robru, not already!
[02:57] <balloons> fginther: howdy. So, clock landed, but calendar can't without switching back
[02:58] <balloons> popey: I think we have a plan, we just need to land clock first now appreciate you being around :)
[02:58] <fginther> balloons, has everything clock landed?
[02:58] <popey> balloons: sure
[02:58] <balloons> popey: fginther weird it like turned my message to mush
[02:58] <popey> I am about now if there's anything you want to do
[02:59] <balloons> fginther: I guess not.. nik90 had to sleep, but we landed the main piece
[02:59] <balloons> fginther: I think I'm going to worry about it more tomorrow.. we'll at some point need to get a calendar build in with the new icon for the store
[02:59] <fginther> balloons, I'm around, want to try now?
[03:00] <balloons> fginther: yea, if you want to redo the package and we'll merge calendar. then undo it again so we can mess with clock more tomorrow :-)
[03:00] <fginther> balloons, I'm ok with that
[03:01] <fginther> let me get it going
[03:07] <fginther> balloons, popey, calendar is rebuilding now
[03:09] <balloons> fginther: https://code.launchpad.net/~popey/ubuntu-calendar-app/new-icon/+merge/207035 right?
[03:09] <balloons> ahh indeed
[03:09] <balloons> awesome
[03:12] <fginther> balloons, looks like a test failed, perhaps its needs the old qtorganizer-eds which I don't have
[03:15] <balloons> let me look quickly
[03:17] <balloons> fginther: that looks the same as before. did you push the new qt5organizer-eds?
[03:18] <balloons> we don't need to debug forever, i guess. we won't be able to get the image changes in at this point
[03:18] <fginther> 0.1.1+14.04.20140213-0ubuntu1 is installed
[03:22] <balloons> fginther: that should be the one to work. ok, let's revert back to what works for clock and call it good
[03:23] <balloons> i'll file something against the package to get a proper fix for both clock and calendar
[03:23] <balloons> ty again.. enjoy your night :=)
[03:23] <fginther> balloons, k, all done, I'll be up for a little longer
[05:09] <robru> bregma, just checking in before bed... no pings or emails... goodnight ;-)
[07:36] <popey> bug 1280647 makes me sad
[07:36] <popey> and makes me wonder if it's filed against the right project.
[07:52] <didrocks> popey: yeah, I'm unsure tbh, can be that or the sdk itself
[07:52] <didrocks> popey: or even apparmor
[07:52] <didrocks> you should start with tedg and see how many projects you will jump into :)
[08:03] <popey> didrocks: apparmor sounds more plausible
[08:12] <popey> didrocks: bug 1281948 - can you (or anyone) repproduce that?
[08:14] <didrocks> sil2100: hey, do you have a flashed phone handy? ^
[08:14] <didrocks> (in the middle in playing with recovery)
[08:17] <popey> OMG the x86 emulator is stupid fast!
[08:17] <popey> this is going to make developing without a device (and QA) SO much better!
[08:46]  * sil2100 is still upgrading
[09:01] <thostr_> sil2100: could you publish silo 4
[09:01] <sil2100> thostr_: looking
[09:04] <asac> popey: it works? :)
[09:04] <asac> popey: x86 emu?
[09:05] <popey> it does
[09:05] <popey> its fast too
[09:05] <popey> like stupid fast
[09:05] <asac> popey: nice one :P
[09:05] <popey> yeah!
[09:05] <popey> good work all round
[09:10] <sil2100> popey: hmmm, I could not reproduce
[09:10] <sil2100> popey: is this bug reproducible every time?
[09:11] <popey> yes
[09:12] <sil2100> popey: I just did the test, first opened a page with 3G, then used the indicator to switch WiFi on and it still works - I had to wait like 5-10 seconds for it to 'catch up', but seems to work
[09:12] <popey> what did you do, tap a link?
[09:13] <popey> you didnt close the browser in between?
[09:13] <sil2100> Tap a link at first, but then I typed in a new address
[09:13] <sil2100> No
[09:13] <sil2100> I was on the browser all the time
[09:16] <tvoss> popey, where can I get the emulator?
[09:16] <tvoss> popey, the x86 one
[09:16] <popey> tvoss: https://plus.google.com/u/0/100264483712374857174/posts/1u7HSYjF2He
[09:16] <popey> sil2100: dont type a new address, just click a link
[09:17] <sil2100> popey: ok, then that didn't seem to work indeed
[09:18] <popey> \o/
[09:18] <popey> confirmificate pls
[09:20] <sil2100> popey: confirmed!
[09:22] <popey> ta
[09:31]  * popey wonders where everyone is, on the landing call...
[09:32] <ogra_> oh
[10:21] <thostr_> can i get a silo for line 19?
[10:25] <sil2100> o/
[10:26] <jdstrand> popey, didrocks: if its apparmor, please check 'grep DEN /var/log/syslog' and report a bug against apparmor-easyprof-ubuntu
[10:27] <sil2100> thostr_: done
[10:27] <thostr_> sil2100: thanks
[10:27] <thostr_> can I put two dependent projects in one silo?
[10:28] <thostr_> or do I need a silo for prerequisites first?
[10:28] <sil2100> thostr_: what do you mean by 'two dependent'?
[10:28] <thostr_> project B depends on new version of project A
[10:28] <sil2100> thostr_: you can put that in one silo
[10:29] <sil2100> thostr_: if the deps are set correctly, when building the depending project will dep-wait for the other one to build
[10:29] <sil2100> And then build itself
[10:31] <thostr_> sil2100: ok
[10:37] <asac> anyone has a script that unassigns and unsubscribes from all bugs?
[10:37] <asac> in launchpad?
[10:37] <asac> :)
[10:40] <timp> asac: the easiest way is to fix all of them ;p
[10:41] <sil2100> didrocks, asac: I'll jump out in around 30 minutes with my rat to the vet for the surgery - it should only take like 15 minutes, since we don't have to be around during the surgery
[10:42] <didrocks> sil2100: ok, tel me once you are back
[10:43] <asac> sil2100: good luck for your rat :P
[10:44] <sil2100> asac: thanks ;) We don't want to loose another one, she's like a family member already ;p
[10:46] <popey> jdstrand: \o/ done https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1267979
[10:47] <asac> sil2100: yeah. i know
[10:48]  * didrocks wonders if jdstrand doesn't have an apparmor hilight
[10:52] <thostr_> can I get a silo for line 33?
[10:54] <jdstrand> popey: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1267979/comments/6
[10:54] <jdstrand> didrocks: :)
[10:54] <popey> Doh!
[10:54] <popey> thanks jdstrand
[10:54] <jdstrand> np
[10:55] <didrocks> thostr_: done
[10:56] <didrocks> jdstrand: seems some guys are challenging your security policy, nice that it works :p
[10:56] <jdstrand> hehe
[10:57] <popey> Fight the system!
[11:17] <psivaa> didrocks: https://bugs.launchpad.net/notes-app/+bug/1271054 appears to be the cause for the notes app flakiness. oSoMoN was working on it. I've updated the bug with the latest information
[11:20] <didrocks> psivaa: excellent, thanks a lot!
[11:20] <psivaa> didrocks: yw
[11:53] <sil2100> didrocks: back now if anything
[11:53] <didrocks> ogra_: so, based on psivaa's feedback, and all other inputs, I think we should promote latest image, except for maguro. asac +1 on this. I'll formulate that in the landing email, but that would be awesome if you have a bug report for it
[11:53] <didrocks> sil2100: ah, great, let's chat quickly in 7 minutes?
[11:53] <didrocks> (on your questions)
[11:53] <didrocks> that would be easiest
[11:55] <sil2100> Sure
[12:00] <ogra_> didrocks, bug 1282051
[12:00] <ogra_> oh
[12:01]  * ogra_ fixes summary ... the lib that changed was unity7 
[12:01] <didrocks> yeah, it's in unity7. Otherwise, good! thanks :)
[12:02] <sil2100> ;)
[12:03] <psivaa> didrocks: with 192 the tests are still running btw
[12:04] <didrocks> psivaa: the changes are compiler stuff, so I guess it's safe to base on 191 test results, but thanks for the warning
[12:04] <psivaa> didrocks: ack :)
[12:06] <sil2100> didrocks: just tell me once you have a moment for that quick chat
[12:07] <sil2100> As I said, no urgency ;)
[12:08] <ogra_> didrocks, so do you want 189 or 190 ?
[12:08] <didrocks> ogra_: I guess we can 192 even, basing on the results from 191 (and 192 was dogfooded by popey)
[12:08] <ogra_> ok
[12:08] <didrocks> ogra_: all devices, but maguro, of course :)
[12:08] <ogra_> yep
[12:09] <didrocks> sil2100: 5 minutes
[12:09] <didrocks> thanks!
[12:12] <ogra_> [12:13] <didrocks> ogra_: thanks!
[12:14] <ogra_> sigh
[12:14] <ogra_> my mako just crashed hard during upgrade from 189 ro 192
[12:14] <ogra_> *to
[12:15] <ogra_> err, 188 to 192
[12:16] <didrocks> hum, due to new download manager you think? did you get a stacktrace?
[12:16] <didrocks> or it's during the recovery mode?
[12:16] <ogra_> no, it suspended the screen, i noticed there was no lock screen when i woke it up, i touched it and it was unresponsive
[12:17] <didrocks> so, during download?
[12:17] <ogra_> is suspended and resumed again and the screen didnt come back and adb was gone
[12:17] <ogra_> yes
[12:17] <didrocks> mandel: did you hear about that? ^
[12:17] <ogra_> i dont think its the fault of the download manager
[12:18] <mandel> didrocks, ogra_ uh, dammed
[12:18] <mandel> ogra_, did the files download? can you paste the logs?
[12:18] <ogra_> all .crash files i see are old
[12:18] <ogra_> feb 14th is the newest
[12:18] <mandel> O_o
[12:18] <mandel> ogra_, that is very very old
[12:19] <ogra_> mandel, there are no dl-manager crash files i dont think it is involved here
[12:19] <mandel> well, 5 days old in ubuntu touch is like years old
[12:19] <ogra_> the UI hung and there was no lockscreen
[12:19] <mandel> ogra_, "awesome"
[12:19]  * ogra_ would rather blame unity or mir
[12:21] <ogra_> hmpf ... i wish the unity8.log had timestamps
[12:22]  * ogra_ sees some "file:///usr/share/unity8/Dash/GenericScopeView.qml:290: TypeError: Cannot read property 'category' of null"
[12:22] <ogra_> but thats also in the new log from this boot
[12:22] <ogra_> seems to not have any ill sideeffects
[12:24] <ogra_> mandel, btw, despite the crash the files seem to have downloaded fine ... selecting update in system-settings immediately offers to reboot and install
[12:25] <mandel> ogra_, you just made my day better hehe
[12:25]  * ogra_ thought so :)
[12:27] <ogra_> popey, i have no online music in 192
[12:27] <popey> i do
[12:28] <popey> in the music scope under "popular onlin"
[12:28]  * ogra_ wonders if having two mediascanners running might cause that 
[12:28] <ogra_> right, i dont see that
[12:28] <ogra_> only the local test music i have installed is listed
[12:29] <popey> http://popey.com/~alan/phablet/device-2014-02-19-122902.png
[12:29] <ogra_> (i have the carousel, but nothing else in the music lens)
[12:35] <ogra_> bah, not even after reboot
[12:36] <ralsina> didrocks: in the rampup, owners sheet there is a row for click-update-manager which doesn't exist anymore, can I just remove it?
[12:37] <didrocks> ralsina: just write "DEAD" so that we can track and demote from daily release
[12:37] <ralsina> didrocks: ack
[12:37] <ralsina> didrocks: oh well, can't edit
[12:38] <didrocks> hum
[12:39] <didrocks> are you logged with your canonical account?
[12:39] <ralsina> yes
[12:39]  * didrocks remembers to add all canonicalers as editors
[12:39] <didrocks> let me check, one sec
[12:39] <didrocks> "People at Canonical who have the link can edit
[12:40] <didrocks> ralsina: you are on https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdC05a2ZQSmgwU2NFYnJQOE9qMDRYa3c#gid=1, right?
[12:40] <ralsina> Yes, that URL. I'll reload and try again.
[12:40] <didrocks> reload harder :p (otherwise, I'll just add you explicitely)
[12:41] <ogra_> rsalveti, make sure you have no G+ open under a private account anywhere in the same browser
[12:41] <ogra_> err ralsina
[12:41] <didrocks> ogra_: you keep pinging the poor Ricardo for nothing :p
[12:41] <ogra_> you can also play with the gid= value in the url
[12:41] <didrocks> gid is the tab
[12:42] <ogra_> didrocks, its late, he should get up :P
[12:42] <didrocks> ahah
[12:42] <ralsina> ogra_: ack, it's not even reloading now. Crap. I'll recheck in 2' :-)
[12:42] <didrocks> :)
[12:42] <ogra_> (the beachboy ...have you seen where he lives now ?)
[12:42] <didrocks> oh I missed that
[12:45] <didrocks> sil2100: oh, you were not there yesterday when I got the message from sergio. Please do not assign gallery-app or camera-app landing slots. He want to be able to land line #4
[12:57] <sil2100> didrocks: ok
[13:09] <boiko> didrocks: hey, I still can't find the calendar you mentioned yesterday, do you have a link to it?
[13:12] <didrocks> I wonder how we can get the calendar url from google
[13:12] <didrocks> let me look
[13:23] <ogra_> boiko, you should have the "Ubuntu Engineering" calendar available if you search for it in your canonical account
[13:24] <ogra_> (everyone working in UE has it afaik)
[13:24] <boiko> ogra_: found it now
[13:25] <didrocks> ogra_: had to give him the direct url
[13:25] <didrocks> not sure why it doesn't show up in search, not the first time I heard about that
[13:26] <boiko> didrocks: ogra_: it looks like that field is not a search field, it is just an e-mail address field
[13:27] <ogra_> i think there is a widget on the left side when you are in your own calendar that allows searching
[13:36] <timp> didrocks: seems like everybody has that issue, I cannot search for the ubuntu engineering calendar as well
[13:36] <didrocks>  yeah, as boiko told, it's not a search field apparently, adn the email address doesn't contain "ubuntu engineering"
[13:37] <timp> is there an e-mail address that I can search for?
[13:37] <timp> I have some sprint calendars listed. I don't remember how I got them, but not by searching for an e-mail address I think..
[13:39] <didrocks> timp: mped
[13:42] <sil2100> didrocks: hooo, I just tried the new way and it failed ;/
[13:42] <timp> didrocks: it works. thanks
[13:45] <didrocks> sil2100: oh oh?
[13:56] <didrocks> sil2100: and fixed
[13:57] <sil2100> \o/
[14:01]  * didrocks goes for a run
[14:01] <didrocks> sil2100: FYI ^
[15:23] <sil2100> didrocks, asac: do you think I will be needed on the meeting in 10 minutes?
[15:23] <didrocks> sil2100: yeah, I think you are
[15:24] <didrocks> otherwise, you won't be invited :)
[15:26] <sil2100> Uh oh! ;)
[15:27] <asac> sil2100: you dont need to be there if busy, unless you like listening to me :)
[15:27] <asac> but since you are a veteran its good that folks know you :)
[15:28] <sil2100> I'll be around, but probably coding some stuff in the background ;)
[15:29] <asac> will be one minute late or 2
[15:29] <asac> guess people will trickle in slowlyu anyway :)
[15:30] <robru> boiko, i put line 25 in silo 5. please build.
[15:30] <didrocks> robru: already up?
[15:30] <robru> didrocks, yeah we have that "USTZ welcome hangout" now...
[15:32] <didrocks> robru: FYI, I implemented that revision stuff
[15:32] <didrocks> and it's deployed in production
[15:32] <robru> didrocks, sweeeeeeeet thanks sooooooo much!
[15:32] <didrocks> yw ;)
[15:36] <dobey> fginther: did you get a chance to look at https://code.launchpad.net/~dobey/tarmac/list-approved/+merge/206808 ?
[15:39] <bregma> didrocks, I just added some additional MPs to my landing (line 23) and evidently I need a 'silo reconfiguraiton' -- is this something I can do or something the landing team does?
[15:40] <didrocks> bregma: we are thinking about being able to do it yourself if you add new MPs on the some components (so if you already have a lock)
[15:40] <didrocks> bregma: for now, we are doing this for you
[15:40] <didrocks> sil2100: do you have a minute? ^
[15:44] <boiko> robru: thanks!
[15:44] <robru> boiko, you're welcome
[15:45] <sil2100> didrocks: sure
[15:46] <sil2100> bregma: I'll reconfigure it now for you
[15:46] <bregma> sil2100, thanks
[15:48] <sil2100> bregma: it should be reconfigured, you can rebuild now :)
[15:52] <sil2100> Ouch, hangout problems?
[15:52] <sil2100> I lost the ho connection and can't seem to be able to reconnect
[15:53] <didrocks> ogra_: I would like to build nicely a new image, thoughts?
[15:53] <didrocks> as we got some changes from distro
[15:53] <ogra_> didrocks, my thought is ... why dont you just do it :)
[15:53] <sil2100> ;)
[15:54] <didrocks> ogra_: because I needed love and approbation :)
[15:54] <didrocks> (done)
[15:54] <didrocks> endorsement*
[15:54]  * ogra_ hugs didrocks 
[15:54] <ogra_> you rock !
[15:54]  * didrocks hugs ogra_
[15:54] <didrocks> ogra_: thanks for your +1 and hugs! :)
[15:55] <sil2100> ;D
[15:55] <ogra_> :)
[15:56]  * ogra_ would love if we could move the meeting today ... i would really like to see the insights.ubuntu.com thing 
[15:57] <ogra_> silly marketing people didnt take our meeting into account !
[15:58] <sil2100> How DARE they!
[15:58] <ogra_> yeah, so ignorant !
[16:07] <robru> ogra_, didrocks, sil2100: are we moving our meeting then?
[16:08] <sil2100> Not sure
[16:08] <sil2100> On 19 we drive to pick up our rat from the vet \o/
[16:09] <robru> brb, breakfast
[16:09] <didrocks> robru: hum, not really, why?
[16:09] <didrocks> ah
[16:10] <didrocks> plars: balloons: can you come early to the evening meeting?
[16:10]  * ogra_ would really like to be around that other meeting to answer IRC questions etc 
[16:10] <didrocks> like in 20 minutes?
[16:10] <didrocks> (because of the insights.ubuntu.com thing)
[16:10] <didrocks> cyphermox_: as well? ^
[16:10] <ogra_> (though i assume i'm less urgently needed than others in the evening one)
[16:11] <didrocks> ogra_: yeah, there are as well the landers that could show up
[16:11] <didrocks> though
[16:11] <didrocks> anyway, we can keep the meeting short, we just kicked an image
[16:11] <cyphermox_> probably yes
[16:11] <cyphermox_> currently in a meeting
[16:11] <ogra_> same here :)
[16:11] <didrocks> I guess rsalveti as well :p
[16:11] <cyphermox_> yes
[16:12] <cyphermox_> but we should be done soon enough I guess
[16:12]  * didrocks prepares evening email
[16:15] <balloons> didrocks: I'll try
[16:31] <didrocks> robru: balloons: cyphermox_: rsalveti: plars: ogra_: I'm in the hangout if you want
[16:32] <sil2100> Which one?
[16:32] <sil2100> :)
[16:32] <didrocks> sil2100:  :p
[16:32] <didrocks> sil2100: same like
[16:32] <didrocks> link*
[16:32] <didrocks> https://plus.google.com/hangouts/_/calendar/Y2Fub25pY2FsLmNvbV91cTRvNmQyMWJvNmJ0bm1mcW9xZWtsNTdnOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t.cg7k3h1nmqml7psc1nn68223i0
[16:33] <sil2100> Be there in a moment
[16:38] <rsalveti> got a conflict now =\
[16:40] <fginther> dobey, yes that looks good, thank youu
[16:40] <cgoldberg> ping didrocks, hi.. just added line 38 to spreadsheet and need a silo for landing.. can you help with that?
[16:40] <didrocks> cgoldberg: are you coming to the landing meeting?
[16:40] <didrocks> cgoldberg: as discussed yesterday :)
[16:43] <cgoldberg> didrocks, right.. will do
[16:44] <didrocks> cgoldberg: we started in advance due to insight.ubuntu.com, you can join if you want
[16:45] <cgoldberg> didrocks, brt... at a sprint
[16:59] <robru> boiko, i published silo 1 for you, please merge & clean once it hits distro.
[17:00] <robru> seb128, line 35 got silo 9, please build
[17:01] <robru> cgoldberg, just making sure you're aware of this merge conflict, please rebase your branch: http://162.213.34.102/job/landing-006-1-build/34/console
[17:01] <cgoldberg> robru, yup.. working on it now.. thanks
[17:02] <seb128> robru, thanks
[17:02] <robru> cgoldberg, seb128: you're welcome
[17:04] <didrocks> robru: can you assign line 36?
[17:04] <robru> sure
[17:04] <didrocks> thanks
[17:05] <robru> ralsina, line 36 got silo 10, please build.
[17:09] <ralsina> robru: building, thanks
[17:44] <dobey> fginther: thanks. that's in trunk now. i'll try to get the "merge a specific MP" issue fixed soon too, as soon as i can find a little time to do it.
[17:44] <elopio> ping fginther, can I get an account on this jenkins please? http://91.189.93.70:8080/
[17:45] <fginther> elopio, for what purpuse?
[17:46] <elopio> to rebuild the failed executions some times. Now, I depend on balloons for that.
[17:46] <fginther> elopio, thanks, that works
[17:54] <robru> boiko, i see there's a merge conflict for webbrowser-app in silo 5. doesn't look like osomon is around. are you working on that?
[17:55] <thostr_> could somebody reconfig silo 7?
[17:55] <robru> thostr_, sure
[17:57] <robru> thostr_, done, please build
[17:57] <thostr_> robru: thanks
[17:58] <thostr_> robru: damn, I fuc..ed up
[17:58] <thostr_> robru: I wanted silo 4 to be reconfigured
[17:58] <robru> thostr_, no worries. on it
[18:01] <bregma> evidently the new Mesa packages have landed and are causing Unity build failures, it seems there's a broken dependency in Mesa somewhere
[18:01] <thostr_> robru: configured?
[18:01] <robru> thostr_, yep
[18:01] <thostr_> robru: thanks
[18:09] <bzoltan1> didrocks: I have added a line to the CI sheet
[18:10] <robru> bzoltan1, it's marked 'no'
[18:10] <bzoltan1> robru: because it is not yet ready
[18:10] <robru> ok
[18:14] <plars> didrocks: sorry I couldn't make it, I mentioned earlier that I wouldn't be able to. I'm back now though if you need something
[18:14] <didrocks1> plars: please coordinate with robru, cyphermox, ballons, there is an image coming :)
[18:19] <plars> robru, cyphermox, balloons: looks like it's already here. Looks like a lot of hud stuff, anything in particular to watch out for?
[18:20] <mhr3> robru, can i get silo for 41?
[18:20] <robru> mhr3, sure
[18:22] <robru> mhr3, ok, you got silo 11, please build.
[18:23] <ralsina> robru: can I get a silo for row 37? It's MWC related
[18:23] <robru> ralsina, sure
[18:24] <boiko> robru: I asked oSoMon to take it a look, not sure he fixed it
[18:24] <mhr3> robru, thx
[18:25] <robru> boiko, do you think it'll be fixed soon? because i have another landing that's waiting on webbrowser-app...
[18:25] <robru> ralsina, ok, you got silo 12, please build.
[18:26] <ralsina> robru: ack, on it!
[18:27] <boiko> robru: it looks like oSoMon merged one branch into the other, so one one of the branches is now needed, should I just update the spreadsheet?
[18:27] <boiko> robru: or is there any other way for me to proceed?
[18:27] <robru> boiko, if that's the case then yes. i'll have to reconfig it.
[18:28] <boiko> robru: let me do that, sorry for the trouble
[18:28] <robru> boiko, no worries. just trying to help everything land smoothly
[18:30] <boiko> robru: so, I have updated the spreadsheet line 25
[18:34] <robru> ok
[18:35] <robru> boiko, ok, it's reconfigured, please rebuild
[18:35] <boiko> robru: nice! thanks!
[18:51] <robru> yep, that just figures
[18:51] <robru> jenkins goes down *SEVEN MINUTES* after didrocks signs off
[18:52] <boiko> :)
[18:56] <veebers> didrocks: ping, hey we're getting a "Service Temporarily Unavailable" http://162.213.34.102/job/landing-006-1-build/build?delay=0sec
[18:56] <didrocks1> veebers: please check with the US CITrain support :)
[18:57] <didrocks1> not sure, I have a weechat still libing somewhere
[18:57] <veebers> didrocks: ah right :-)
[18:57] <didrocks1> let me kill it :)
[18:57] <didrocks1> have a nice day!
[18:57]  * veebers reads topic
[18:57] <didrocks1> living*
[18:57] <veebers> robru, cyphermox, rsalveti: ping  we're getting a "Service Temporarily Unavailable" http://162.213.34.102/job/landing-006-1-build/build?delay=0sec
[18:58] <robru> what. WHAT?!
[18:58] <cyphermox> fginther: ^
[18:58] <robru> didrocks must know that we don't have the power to start jenkins?
[18:58] <cyphermox> robru: nor should we
[18:59] <cyphermox> which is why I pinged Our Dear Vanguard, fginther ;)
[18:59] <cyphermox> according to the topic anyway
[19:00] <fginther> cyphermox, I have no control over that service, does it run from didrocks account?
[19:00] <robru> cyphermox, yeah but that makes no sense. fginther has already stated that this isn't one of his jenkinses. this is totally didrocks' thing, he's the only one who can fix this, and he just brushed us off
[19:00] <cyphermox> I fginther I don't think so
[19:00] <cyphermox> if it is, then it should be moved to where a vanguard has access, for sure
[19:02] <cyphermox> just a second
[19:02] <robru> http://static.fjcdn.com/gifs/All_edd9de_2472970.gif
[19:02] <veebers> robru, cyphermox: what I understand is it's running on prodstack or something?
[19:02] <cyphermox> yes
[19:02] <cyphermox> veebers: /me is trying to get on the machine
[19:03] <veebers> cyphermox: awesome, cheers
[19:03] <veebers> robru: ^_^
[19:03] <robru> cyphermox, i don't have a clue about prodstack or how to access that.
[19:04] <cyphermox> well, I'm not expecting much luck either, just hoping didrocks did it the way a nice sysadmin would
[19:04] <fginther> veebers, robru, it's not running on prodstack yet, that's in progress.  AIUI, didrocks didn't want to move it yet due to potential disruption to the landing work in progress
[19:04] <robru> right, well... we'll just wait 13 hours for him to come back and fix that then.
[19:05] <cgoldberg> fantastic :/
[19:05] <veebers> fginther: ah right ok. Does that mean we're boned? Or is there hope that it can be fixed?
[19:05] <cyphermox> no
[19:05] <cyphermox> I fully expect IS to be able to help us here.
[19:05] <veebers> awesome, thanks for the hope :-)
[19:06] <fginther> sorry guys, I'm afraid there's nothing the ci team can do here
[19:07] <cyphermox> heh, you know what, I can just mup didrocks.
[19:07] <cyphermox> he has to pay for this ;)
[19:07] <fginther> (also, in a meeting, so sorry for not following closely)
[19:09] <cyphermox> fginther: robru: I sms'd didrocks.
[19:09] <cyphermox> I expect it's just one command for him to do to give us access.
[19:10] <robru> fginther, no worries, we know it's not your thing.
[19:11] <fginther> robru, thanks
[19:24] <thomi> robru: cyphermox: does the ci-train project have a launchpad presence? I know there's ci-process-itself (or whatever), but that seems like it's for the old ci stuff?
[19:24] <thomi> for example, is the ci-train code on lp somewhere?
[19:25] <thomi> or can we file bugs?
[19:26] <robru> thomi, the citrain code currently lives under lp:cupstream2distro, which is technically the old thing, but it has a 'citrain' subdir in it.
[19:26] <robru> thomi, so that's probably a good place to file bus.
[19:26] <robru> bugs
[19:26] <cyphermox> thomi: much of the code is the same as the old cu2d code
[19:26] <cyphermox> but I'm not sure of *all* the specifics of that jenkins instance.
[19:27] <cyphermox> so before breaking more thinks to fix one, I'd rather give didrocks, who's off hours at this point, to get back to us.
[19:27] <robru> cyphermox, ok. seems like a long shot.
[19:29] <cyphermox> I sms'd 20 minutes ago, I'd like to give him enough time to get back home or whatnot, then call and see what can be done
[19:29] <cyphermox> we're not going to die for 30 minutes to an hour or two of downtime of this
[19:29] <cyphermox> more than that, we might ;)
[19:30] <cyphermox> speaking of dying, has there ever been an SLA defined?
[19:30] <robru> cyphermox, ok, any other day i wouldn't be so paniced, but this is literally the last day before featurefreeze.
[19:30] <cyphermox> robru: last day before feature freeze is still quite late to be landing things that matter for FF
[19:31] <cyphermox> that said, I expect this to be resolved in under an hour
[19:31] <robru> cyphermox, ok, well I have a lunch thing right away, so I'm going to step out. can you coordinate with didrocks? i'll be back soon
[19:32] <cyphermox> yeah
[19:32] <robru> cyphermox, ok thanks
[19:33] <seb128> cyphermox, what's the issue?
[19:33] <seb128> jenkins down?
[19:33] <cyphermox> ah, seb
[19:33] <cyphermox> yeah
[19:33] <seb128> asac, who can help with jenkins being down out of didrocks' hourS?
[19:33] <cyphermox> trying to reach didrocks who's probably the only person with an ssh key on the machine
[19:34] <seb128> is he?
[19:34] <cyphermox> I don't know
[19:34] <seb128> that seems "suboptimal"
[19:34] <cyphermox> what I know for sure is I don't ;)
[19:34] <seb128> didrocks tend to have is phone off in evenings
[19:34] <cyphermox> I tried both phone numbers in the directory
[19:34] <cyphermox> but my phone just rings occupied
[19:35] <cyphermox> I'm in the office, so I don't know if it's because I can't make international calls or what
[19:35] <seb128> yeah, as said he tends to have his mobile off
[19:35] <cyphermox> yep
[19:35] <seb128> so I'm not surprised
[19:35] <cyphermox> well, maybe asac knows or has access
[19:35] <seb128> but honestly, we shouldn't rely on didrocks to be #is
[19:35] <seb128> right
[19:35] <cyphermox> seb128: indeed
[19:35] <seb128> asac, hey?
[19:36] <seb128> jasoncwarner, can you help?
[19:36] <cyphermox> seb128: I pinged in #is too, don't worry. But as I suspected they don't just routinely keep access to prodstack machines, though they could move the external IP to another jenkins we could bring up
[19:36] <seb128> cyphermox, right, it's just crazy that we don't have backup points for those infras
[19:37] <seb128> we can't rely on one member to be online 24/7
[19:42] <cyphermox> no, we can't
[19:42] <cyphermox> it may well have been thought of before, but I don't know who else has access
[19:43] <seb128> well, it's a good reminder that we need to scale resources
[19:43] <seb128> though it's unfortunate that happens the day before ff
[19:43] <cyphermox> heh
[19:43] <cyphermox> fires always happen when they ought not to
[19:44] <seb128> what team is on charge of that jenkins?
[19:46] <asac> seb128: hi
[19:46] <seb128> asac, hey
[19:46] <asac> seb128: check with vanguard in /topic :)
[19:46] <seb128> asac, jenkins is down, who can help?
[19:46] <asac> fginther: ^^
[19:46] <seb128> asac, <fginther> sorry guys, I'm afraid there's nothing the ci team can do here
[19:46] <asac> fginther: think they talk about the CI train jenkins
[19:46] <seb128> asac, that's what vanguard says
[19:46] <asac> fginther: is that true? my understanding was that didrocks did a charm that you guys deployed
[19:47] <seb128> asac, <fginther> veebers, robru, it's not running on prodstack yet, that's in progress.  AIUI, didrocks didn't want to move it yet due to potential disruption to the landing work in progress
[19:47] <seb128> to be complete
[19:48] <cyphermox> well, that does look to be in prodstack
[19:48] <asac> seb128: which jenkins are you missing?
[19:49] <seb128> asac, the CI train one
[19:49] <asac> seb128: do you have an ip?
[19:49] <seb128> asac, http://162.213.34.102
[19:49] <cyphermox> http://162.213.34.102
[19:49] <asac> thats public?
[19:49] <cyphermox> yes
[19:49] <seb128> yes
[19:49] <seb128> that's the CI train one
[19:49] <fginther> asac, As far as I know, that's running on didrocks own canonistack account
[19:49] <asac> ok
[19:49] <asac> seb128: can you mup didrocks :)
[19:49] <asac> he loves you enough
[19:49] <cyphermox> fginther: is there a charm then?
[19:49] <cyphermox> asac: I already did
[19:49] <asac> ok
[19:49] <seb128> asac, cyphermox did, he's off/having his phone turned off
[19:50] <asac> ok
[19:50] <cyphermox> I can try home phone
[19:50] <asac> err why do you know his phone is off?
[19:50] <fginther> cyphermox, there is a charm for standing up jenkins, yes
[19:50] <asac> texting doesnt tell you that i figure
[19:50] <seb128> asac, it rings busy and I know didrocks tend to have his mobile off in evenings
[19:50] <asac> cyphermox: when did you send the mup?
[19:50] <cyphermox> fginther: then we should consider if it's time to use it and build a new one, if the rocks don't answer
[19:50] <seb128> asac, so assumption but it's likely right
[19:51] <cyphermox> asac: 14h09
[19:51] <asac> cyphermox: how long ago is that ... or UTC plz
[19:51] <asac> :)
[19:51] <seb128> asac, we really rely on didrocks 24/7? the guy is stressed enough, that can't be right...
[19:51] <cyphermox> 40 minutes ago, sorry
[19:52] <asac> seb128: well, thats true, but in this case it was himself setting things up so its just him :)
[19:52] <cyphermox> doesn't seem to work at all for the phone calls, for me at least
[19:52] <asac> seb128: so while i feel bad, i think its fair
[19:52] <cyphermox> fginther: care to share the charm?
[19:52] <asac> ev: around?
[19:52] <fginther> one moment
[19:53] <asac> who is affected by this outage?
[19:53] <seb128> cyphermox, asac, I tried private email in case, let's see
[19:54] <cyphermox> fginther: I'll try to bring up my own, see if it looks like it would work properly. for now I think it will have to remain in canonistack if that's where it currently is, on  account of trying to not disrupt the process too much
[19:54] <fginther> cyphermox, https://code.launchpad.net/~ci-engineering-private/ci-train/trunk
[19:55] <cyphermox> not allowed here
[19:55]  * fginther grumbles
[19:55] <asac> cyphermox: right. check out what this is. however, i believe there are probably credentials etc.
[19:55] <asac> that are not in that thingy
[19:55] <asac> cyphermox: have you tried sshing into that machine?
[19:55] <seb128> asac, everyone, CI is down basically (and ff is tomorrow)
[19:55] <seb128> asac, it's going to be an important issue for unity7, they are trying to land their hidpi work before ff (and other stuff next)
[19:55] <seb128> asac, no CI train without that jenkins
[19:55] <seb128> e.g no build, no publish, no merge
[19:55] <asac> cyphermox: maybe he added ssh keys?
[19:55] <cyphermox> asac: doesn't seem to be the case, first thing I tried
[19:55] <asac> ok, lets wait 10 minutes and then call him
[19:55] <asac> on landline
[19:56] <cyphermox> I already did that earlier :)
[19:56] <asac> in parallel cyphermox checks out the charm
[19:56] <fginther> cyphermox, I'll send you something
[19:56] <asac> cyphermox: landline?
[19:56] <cyphermox> yes
[19:56] <asac> ok then only way out is to try fight the fire on our own :/
[19:56] <cyphermox> both lines, via my own landline in the office and also using google voice, just because I thought my landline wasn't able to do international
[19:56] <asac> maybe he is at a concert or something
[19:56] <asac> or cinema etc.
[19:56] <asac> :)
[19:56] <asac> so ...
[19:57] <asac> we sould retry in half hours or so
[19:57] <asac> ouch
[19:57] <cyphermox> yes, I'll check out the charm in the meantime
[19:57] <seb128> asac, btw I'm not sure you get to play the card of "but in this case it was himself setting things up so its just him" there, he probably did it/didn't migrate because the enforced constrains didn't let him do so
[19:57] <fginther> cyphermox, email sent
[19:57] <cyphermox> fginther: ack
[19:58] <asac> seb128: well, he could have set up ssh. the ssh access is the main reason we kept it in canoni atm
[19:58] <asac> seb128: but surely he is not to blame
[19:58] <asac> but we aren't either :)
[19:58] <seb128> did anyone asked to get access?
[19:58] <asac> he is a manager :)
[19:58] <seb128> no he's not
[19:58] <asac> for this effort
[19:59] <seb128> well, you give his the duties without the benefits
[19:59] <seb128> that's not fair
[19:59] <seb128> he's not a maganers
[19:59] <asac> err
[20:00] <cyphermox> seb128: access to this never came up before
[20:00] <asac> so lets focus on this problem
[20:00] <asac> i can explain more about hat
[20:00] <asac> but not today :)
[20:00] <cyphermox> alright, I have all the data I"m going to try to bring another jenkins online
[20:02] <cyphermox> oh!
[20:02] <cyphermox> d'oh
[20:11] <fginther> sergiusens, we're seeing a problem with the core apps using cmake are not including the icon
[20:11] <asac> jfunk: yes here. we are ringing didrocks and at same time
[20:12] <asac> jfunk: try to bring up a shadow instance on our own
[20:12] <asac> cyphermox: so still looks good?
[20:12] <fginther> sergiusens, any ideas on where to look?
[20:21] <sergiusens> fginther, balloons which project?
[20:21] <sergiusens> all?
[20:21] <sergiusens> so I can branch
[20:22] <sergiusens> but the root cause is either -> icon path, icon name in either -> CMakeLists.txt manifest.in or desktop file Icon= entry
[20:23] <sergiusens> fginther, balloons or missing an install entry
[20:23] <fginther> sergiusens, currently seeing it with clock and weather app
[20:23] <sergiusens> fginther, let me get those
[20:23] <fginther> sergiusens, probably best to debug with clock
[20:24] <asac> cyphermox: anyone sent an update to ML?
[20:24] <asac> cyphermox: otherwise i can do that.
[20:25] <sergiusens> balloons, did you update the icons in the branch btw?
[20:29] <sergiusens> fginther, solved
[20:30] <fginther> sergiusens, \o/
[20:32] <fginther> sergiusens, what's the story?
[20:33] <sergiusens> fginther, icon has no install rule
[20:38] <sergiusens> fginther, https://code.launchpad.net/~sergiusens/ubuntu-clock-app/icon/+merge/207295
[20:39] <sergiusens> fginther, did you add click build and testing during MRs?
[20:41] <fginther> sergiusens, no click build there yet, but it needs to be added. I've been updating the jobs here so far: http://s-jenkins.ubuntu-ci:8080/view/click/
[20:41] <fginther> sergiusens, which I know isn't the final solution
[20:41] <sergiusens> fginther, if you get me a trusty box, we can do reminders easily
[20:41] <sergiusens> trusty x86
[20:41] <fginther> sergiusens, https://jenkins.qa.ubuntu.com/job/reminders-app-click/
[20:42] <fginther> sergiusens, is more needed?
[20:42] <veebers> cyphermox: Hate to bother you, any update re: release train?
[20:42] <cyphermox> fighting canonistack...
[20:42] <veebers> cyphermox: ack, thanks
[20:42] <cyphermox> worst case, we'll make sure it's fine to do uploads for whatever tomorrow
[20:42] <fginther> sergiusens, here's a better link: http://s-jenkins.ubuntu-ci:8080/view/click/job/reminders-app-click/
[20:42] <cyphermox> or you know, account for the lost time
[20:42] <asac> fginther: sure that this outage mnight not be related to the ci-train.ubuntu.com bringup?
[20:42] <sergiusens> fginther, I would like to build it in a click chroot though
[20:43] <asac> fginther: do you know what tickets etc. are there?
[20:43] <sergiusens> fginther, look at https://code.launchpad.net/~sergiusens/phablet-tools/buddy-x/+merge/206587
[20:44] <fginther> asac, There are no jobs on https://ci-train.ubuntu.com/. It appears that IS has set things up, but still need to have the jobs defined.
[20:48] <asac> fginther: thats not what i mean
[20:48] <asac> fginther: maybe they reassigned some IP etc.
[20:49] <asac> fginther: do you have the ticketss we filed for this?
[20:49] <fginther> asac, ahh, that ticket, going through it now
[20:49] <asac> thx
[20:49] <asac> just to be sure
[20:49] <asac> that its not them having pulled the plug out of this or something
[21:01] <fginther> asac, just verified with is/webops that they haven't done anything with the prodstack citrain in the last few hours. This appears to the service or canonistack itself going down
[21:06] <fginther> sergiusens, the MP for the icon fix failed to build deb packages, any ideas?
[21:07] <sergiusens> fginther, already pushed fix
[21:07] <fginther> sergiusens, awesome
[21:07] <sergiusens> fginther, if we get rid of debs for these, we wouldn't need all this cmake ;-)
[21:08] <fginther> sergiusens, can we install click packages on a trusty desktop?
[21:08] <sergiusens> fginther, yes
[21:09] <fginther> sergiusens, then yes, this deb stuff is a boat anchor
[21:11] <sergiusens> would love to see that!
[21:12] <sergiusens> fginther, can you tell the bot to run again btw?
[21:13] <asac> cyphermox: how is your lead going?
[21:13] <fginther> sergiusens, looks like it's running ow
[21:16] <mhr3> robru, hm, landing pipeline broken?
[21:17] <robru> mhr3, yep, whole thing imploded seconds after your last message to me
[21:17] <mhr3> lovely
[21:17] <robru> mhr3, i blame you. ;-)
[21:17] <mhr3> ehm... thanks? :P
[21:18] <robru> mhr3, j/k. jenkins vanished before I could even click publish like you asked. sorry. we have Top. Minds. on this, but it might take until tomorrow morning to resolve.
[21:18] <asac> cyphermox: so yeah, lets see if we can bring this baby up; otherwise try to land most critical cases manually
[21:18] <asac> cyphermox: like upload to silo for them :)
[21:18] <cyphermox> working on it.
[21:18] <asac> after testing: upload to archive
[21:19] <cyphermox> I had never used canonistack before though so now I have an instance up, just can't ssh to it
[21:19] <mhr3> robru, looks like didier went over his isp limit :P
[21:19] <asac> cyphermox: check with #cts
[21:19] <cyphermox> what?
[21:20] <asac> cyphermox: thought you need help with canonistack
[21:20] <asac> thought cts was the right house for that
[21:24] <fginther> cyphermox, are you following this? https://wiki.canonical.com/InformationInfrastructure/IS/CanonicalOpenstack?action=show&redirect=CanoniStack
[21:24] <fginther> cyphermox, and did you deploy with juju?
[21:24] <cyphermox> yes
[21:25] <asac> thomi_: you guys impacted by this?
[21:25] <fginther> cyphermox, juju probably used your ~/.ssh/id_rsa files, if you are having ssh troubles remove this line (IdentityFile ~/.canonistack/${NOVA_USERNAME}_${OS_REGION_NAME}.key) from your .ssh config
[21:26] <asac> veebers: ^^ ?
[21:26] <fginther> sergiusens, jenkins passed
[21:27] <cyphermox> fginther: I tried all the keys, but I'll check and try again
[21:27] <cyphermox> my ssh config is quite complex
[21:28] <veebers> asac: yes we are. We were trying to release an Autopilot when we came across it
[21:29] <asac> veebers: do you have your stuff in the silo?
[21:29] <asac> and need publishing?
[21:29] <veebers> asac: yes
[21:29] <veebers> asac: not tested
[21:29] <asac> veebers: ok. so you can test right now
[21:29] <veebers> asac: ah I see, no, not built into the silo
[21:29] <veebers> I thought you meant a silo allocated
[21:29] <asac> veebers: you have the set of MPs?
[21:29] <veebers> asac: aye, it is in the spreadsheet details, one moment
[21:30] <veebers> asac: landing-006 tab
[21:31] <sergiusens> fginther, btw, tell me when we can move reminders to that MR I sent your way; this would allow fat packages shortly
[21:31] <didrocks> asac: robru: cyphermox: got the message from seb128. I restarted jenkins on the machine
[21:31] <asac> didrocks: the hero :)
[21:31] <cyphermox> cool
[21:31] <cyphermox> didrocks: care to share access? :)
[21:31] <robru> didrocks, and give some people access before you sign off!
[21:31] <asac> didrocks: can you give ssh access to cypher or so and tell him how to do that and then go off :)?
[21:32] <didrocks> cyphermox: robru: asac: as can't on canonistack policy
[21:32] <didrocks> I*
[21:32] <cyphermox> how so?
[21:32] <didrocks> you need to connect with sshutle
[21:32] <didrocks> sshuttle*
[21:32] <didrocks> which is per nova id
[21:32] <asac> didrocks: thats a policy?
[21:32] <cyphermox> you should be able to ssh-import-id
[21:32] <didrocks> apparently, from what I was told
[21:32] <asac> didrocks: you cant put someone in .ssh/authorized_keys?
[21:33] <asac> didrocks: then make a special key and send it to cypher and a few trusted
[21:33] <asac> didrocks: encrypted with gpg
[21:33] <didrocks> asac: yeah, sounds better
[21:33] <cyphermox> didrocks: let's visit the canonistack setup tomorrow, there's something here I don't have quite right
[21:33] <didrocks> anyway, we are going to move to prodstack
[21:33] <didrocks> then no-one will have ssh access
[21:33] <asac> didrocks: guess thats evil, but shrug :)
[21:33] <didrocks> which worries me a little
[21:33] <asac> didrocks: at least we can ask 24/7 for restarts :)
[21:33] <cyphermox> didrocks: no, if IS can do stuff on it it's simple
[21:33] <asac> didrocks: so system just needs to be robust that restarts recovers
[21:34] <asac> e.g. 1000 restarts to test
[21:34] <didrocks> cyphermox: robru: for the stuff that was running, you may need to rerun then btw
[21:34] <robru> didrocks, ok thx
[21:34] <didrocks> if it was just "building", (and no preparing packages), you can run the job with "watch only"
[21:35] <didrocks> to avoid repreparing anything
[21:35] <robru> mhr3, ok i published your silo 11 now
[21:36] <veebers> yay didrocks \o/ thanks for sorting that out
[21:36] <didrocks> no worry
[21:40] <fginther> sergiusens, regarding fat packages and ci, we would end up building armhf, amd64 and i386 packages for each MP?
[21:40] <sergiusens> fginther, yeah, but cross compiled in the same build with the click chroot
[21:41] <sergiusens> fginther, and armhf and i386 for now
[21:41] <mhr3> robru, yey! :)
[21:43] <asac> cyphermox: robru: so are we set?
[21:44] <asac> is jenkins up?
[21:44] <cyphermox> pretty much yeah
[21:44] <robru> asac, it's up for now.
[21:44] <robru> asac, no idea what caused the outage or if it might happen again
[21:44] <robru> asac, and still no way to restore it without didrocks
[21:44] <cyphermox> I have access.
[21:44] <robru> oh ok
[21:44] <robru> i don't ;-)
[21:44] <cyphermox> and I think I just fixed my canonistack setup
[21:45] <cyphermox> or maybe not
[21:45] <cyphermox> juju is the problem.
[21:46] <didrocks> asac: just note I only have access to the jenkins backend
[21:46] <didrocks> I don't have access to the apache frontend
[21:46] <didrocks> which is in another host
[21:48] <asac> didrocks: what?
[21:48] <asac> didrocks: is that a problem now?
[21:48] <asac> didrocks: who owns that stuff?
[21:48] <asac> ev?
[21:49] <didrocks> I guess that my ssh key wasn't added to the machine
[21:49] <asac> didrocks: can you confirm that the apache frontend is not the problem here?
[21:49] <didrocks> asac: no, jenkins was down
[21:49] <asac> didrocks: so every instance has a master key... whoever crreates the instance has that
[21:49] <asac> didrocks: so you can confirm that the apache server is fine? :)
[21:49] <didrocks> yeah
[21:49] <didrocks> it's working
[21:49] <didrocks> as told 15 minutes ago
[21:49] <asac> cool. i am pretty sure it wont explode today :)
[21:49] <didrocks> well
[21:50] <didrocks> nothing exploded in 4 weeks
[21:50] <asac> still would like to know who owns that service
[21:50] <didrocks> so I hope we'll have moved to prodstack before it explodes again
[21:50] <asac> didrocks: right, but the level of flakiness of jenkins is way higher than a pure apache proxy
[21:50] <didrocks> yeah, and it happened once in 4 weeks though (because we don't have $random plugins)
[21:50] <asac> ev: do you know who has access to apache?
[21:50] <didrocks> asac: I probably have a master key for it, I just don't know enough of canonistack to use it
[21:51] <asac> ev: we seem to have fixed the outage, but found that noone knows who can log in there
[21:51] <ev> what apache instance are we talking about?
[21:51] <asac> ev: the citrain one
[21:51] <ev> in canonistack?
[21:51] <asac> yeah
[21:51] <ev> didrocks: didn't you do the most recently deployment for that? You should have ssh access.
[21:52] <didrocks> ev: I can't ssh to it, but maybe I didn't source the right nova file
[21:52] <didrocks> ah, I'm on lcy02
[21:52] <didrocks> so the old rotted instance
[21:53] <asac> all good?
[21:53] <asac> cyphermox: can we do a test build or something
[21:53] <asac> to see that everything is operational?
[21:53] <didrocks> asac: it's already the case
[21:53] <didrocks> dude…
[21:53] <cyphermox> looks good in jenkins yeah
[21:53]  * didrocks sigh
[21:53] <didrocks> when I say it's good, it's good :/
[21:53] <cyphermox> didrocks: run away nao
[21:54] <didrocks> cyphermox: no, because you need to have access to the jenkins apache NOW it seems
[21:54] <didrocks> as it fall down once in 4 weeks, it seems that's it's more urgent than being in bed…
[21:55] <didrocks> ev: ok, found it
[21:55] <ev> yay
[21:57] <didrocks> getting jenkins up: 1 min. Fixing NOW a wrong firedrill to give access to an apache proxy in case it refall in the next day: 20 minutes
[21:57] <didrocks> anyway, asac: cyphermox has all access now
[22:00] <didrocks> anyway, bye
[22:12] <dpm> balloons, or fginther, could you help me figuring out why this MR is not passing, despite succeeding on the tests? https://code.launchpad.net/~dpm/ubuntu-weather-app/fixes-1282081/+merge/207190
[22:13] <fginther> dpm, there was a test failure, it didn't get added to the MP, but I can fix that : http://91.189.93.70:8080/job/generic-mediumtests-trusty-weather-app/29/
[22:14] <dpm> thanks fginther
[22:14] <balloons> dpm, http://91.189.93.70:8080/job/generic-mediumtests-trusty-weather-app/29/..
[22:14] <balloons> ohh I see fginther is a faster keyboardist :-)
[22:21] <robru> boiko, ping about webbrowser-app in silo 5. it looks like it's built. have you done any testing yet?
[22:22] <boiko> robru: hey, nope, I went offline for a few minutes, and just discovered jenkins is back up, will do the testing now
[22:22] <robru> boiko, great, thanks. would like to publish that soon, but don't cut any corners with the testing ;-)
[22:22] <boiko> robru: I won't, don't worry
[22:26] <robru> boiko, oh, and i put dialer-app in silo 13 for you, please build ;-)
[22:28] <boiko> robru: were it you who merge & cleaned the build that was in silo 1? if so, thanks
[22:28] <robru> boiko, yes I think so. you were away and I had a sense of urgency for whatever reason.
[22:28] <boiko> :)
[22:29] <robru> boiko, by which I mean "you're welcome!"
[22:29] <robru> ;-)
[22:31] <boiko> robru: thanks, btw, your active notifications when silos are allocated are really welcome, less polling on the spreadsheet
[22:32] <robru> boiko, absolutely, push notifications always beat pull ;-)
[22:32] <boiko> yeah
[22:32] <robru> boiko, also I'm terrified that i'm going to step on the work that other landers are doing so I like to be as noisy as possible so people know I'm working ;-)
[22:32] <boiko> hehe, makes sense
[22:55] <robru> kgunn, i put unity-mir into silo 11, please build
[23:07] <boiko> robru: testing on the browser MR done, it is good to go
[23:07] <robru> boiko, thanks
[23:07] <boiko> robru: the spreadsheet says it is still building though
[23:07] <robru> boiko, that's just a hiccup from the outage earlier
[23:08] <boiko> robru: ok, all good then
[23:08]  * boiko calls it a day
[23:08] <boiko> see you!
[23:08] <robru> boiko, goodnight!
[23:08] <kgunn> robru: thanks!
[23:08] <boiko> robru: good night!
[23:09] <robru> kgunn, you're welcome
[23:11] <balloons> fginther: why is https://jenkins.qa.ubuntu.com/job/clock-app-click/142/ building as _all?
[23:12] <balloons> I understand it's pure qml, but.. I guess it's fine
[23:14] <fginther> balloons, I can't answer that, i assume it has something to do with debian/control
[23:14] <fginther> its architecture is "all"
[23:15] <balloons> fginther: yes.. I confirmed with dpm it's fine.. just checking :-) last time I built a click as all, they questioned me :-) But it had a plugin so, not pure qml
[23:16] <dpm> yep, clock is pure qml, no arch-specific code, thus _all