[06:09] <bzoltan> Mirv: ogra_: I have a patch for the phablet-test-run script to make it behave better when running silly applications who do not drop deprecated APIs
[06:10] <bzoltan> I need it to land with the silo20 UITK -> https://code.launchpad.net/~bzoltan/phablet-tools/suppress_deprecated_notes/+merge/259468
[06:20] <bzoltan> brendand_: robru ^
[06:21] <robru> bzoltan: you should be able to add that to the spreadsheet and reconfigure and rebuild on your own. Do you need help?
[06:23] <Mirv> bzoltan: since phablet-tools I think doesn't have a real owner, you should be fine to land it as part of your silo
[06:26] <robru> oh it's a new package, sorry, duh
[06:28] <thostr_> robru: would you have the link to QA review board for me quickly?
[06:29] <Mirv> thostr_: https://trello.com/b/AE3swczu/silo-testing-for-questions-ping-eu-jibel-us-jfunk-nz-thomi-or-ubuntu-qa-on-ubuntu-ci-eng
[06:29] <thostr_> Mirv: thanks a lot
[06:39] <robru> thostr_: also it's permanently in the channel topic.
[07:13] <bzoltan> Mirv: robru: should I self approve that MR or would you take a look and say OK?
[07:14] <bzoltan> And I guess I am not able to reconf the silo since it is a new project
[07:14] <robru> bzoltan: looks fine. I'm just on my phone so i can't approve for real, go ahead
[07:15] <robru> Mirv: you around to reconf? I'm afk
[07:28] <Mirv> robru: yes, you are :)
[07:29] <Mirv> bzoltan: reconfing. maybe self top approve as I don't think the project has an owner.
[07:30]  * thostr_ wonders why ubuntu-silo38 is successfully QA tested but not marked as such in ci spreadsheet...
[07:31] <Mirv> thostr_: ask the person who handled the QA. it might be a mistake or then something not communicated.
[07:32] <thostr_> Mirv: will do
[07:33] <bzoltan> Mirv:  thanks
[08:29] <Wellark> trainguards: how do I enable the vivid overlay on my development machine?
[08:32] <Wellark> Mirv: ?
[08:33] <sil2100> Wellark: you can add the silo PPA on your system, not sure if the higher pin-priority would get in your way
[08:33] <Wellark> sil2100: I need the whole overlay
[08:34] <Wellark> not just a sile
[08:34] <Wellark> silo
[08:34] <Wellark> and I have no idea where the overlay ppa actually lives
[08:34] <sil2100> s/silo/overlay
[08:34] <sil2100> Ah
[08:34] <sil2100> Ok
[08:34] <sil2100> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay
[08:34] <sil2100> When adding manually, probably best if you set its pin-priority to 1001, as this is what priority it has on the devices
[08:41] <jodh> Anybody about that can give me perms to update the CI train spreadsheet, or do I need to wait for the US?
[08:41] <sil2100> Hey!
[08:42] <sil2100> I can give you the power
[08:43] <sil2100> jodh: I only got your landing request e-mail today in the morning, so I couldn't help with landing your change yet :)
[08:43] <sil2100> Anyway, let me add you to the right teams
[08:43] <popey> cihelp I'm getting build timeouts on jenkins, can someone please help? http://91.189.93.70:8080/job/ubuntu-calendar-app-vivid-amd64-autolanding/73/consoleFull
[08:44] <jodh> sil2100: thanks!
[08:45] <Wellark> sil2100: I've never set a priority on a ppa
[08:45] <Wellark> sil2100: do you have a link or something describing how it's done?
[08:46] <Wellark> but anyway, it should not matter, as I'm running stock vivid and anything in the ppa has never version numbers
[08:46] <Wellark> sil2100: thanks! :)
[08:46] <sil2100> Wellark: yeah, normally it shouldn't matter, it's an edge-case when it actually should ;)
[08:46] <sil2100> Wellark: but in case you need instructions: https://help.ubuntu.com/community/PinningHowto
[08:46] <Wellark> sil2100: <3
[08:47] <sil2100> Uh oh! You're welcome ;)
[08:47] <Wellark> sil2100: relax, I don't know your IP
[08:47] <Wellark> yet ;)
[08:47] <sil2100> Phew
[08:47] <sil2100> ;)
[08:48] <jodh> sil2100: I can now update the doc, but getting a couple of errors every few secs: "There was a problem while" and "The action you're trying to perform is causing a fatal error and cannot be performed."
[08:48] <sil2100> Oh no
[08:48] <sil2100> Oh crap
[08:48] <sil2100> jodh: ok, the spreadsheet is in a broken state again ;/
[08:48] <Wellark> will we get a new new new spreadsheet? :D
[08:49] <Wellark> sil2100: could we start using version numbers on them
[08:49] <jodh> sil2100: gulp, sorry if I borked it :)
[08:49] <Wellark> as the current is called "new"
[08:49] <Wellark> and the old one was called "new"
[08:49] <Wellark> and it got confusing :)
[08:49] <sil2100> Wellark: hah! Yeah, soon we'll have to ;/ But let's wait a bit, maybe it'll settle by itself
[08:49] <Wellark> oh you sweet summer child..
[08:49] <sil2100> jodh: no worries, I see it's broken since the morning...
[08:50] <Wellark> but I found your optinism inspriring
[08:52] <Mirv> the newest spreadsheet ever
[08:54]  * sil2100 wants robru to be done with the replacement soon
[08:54] <abeato> trainguards, you can remove line 24 of the spreadsheet and clean silo 27, we are not going to land that
[08:55] <sil2100> jodh: you can *try* adding your landing request, but there are chances it'll disappear ;) You wanted to land using a merge-request, or a source upload?
[08:56] <Mirv> abeato: thanks
[08:57] <abeato> np
[08:59] <Mirv> well, cleaning the silo but since spreadsheet gives fatal errors not removing the line yet (maybe)
[09:00] <abeato> Mirv, yes, I have noticed that :-(
[09:00] <abeato> Mirv, mind assigning silo to line 86 too?
[09:03] <jodh> sil2100: hmm, the upstart fix we need to land is now in wily, but I'm not seeing an appropriate branch to cherry pick the fix into for the vivid overlay (can't even find the rtm one?)
[09:05] <sil2100> jodh: I guess we'll just sync it over
[09:05] <sil2100> jodh: let me prepare everything for that
[09:06] <jodh> sil2100: thanks again
[09:06] <Mirv> abeato: only fatal errors unfortunately :(
[09:07] <abeato> ouch...
[09:08] <Mirv> abeato: trying manually atm
[09:08] <Mirv> abeato: manually typing ok, silo 016
[09:08] <abeato> Mirv, awesome, thanks
[09:09] <Mirv> won't be in the spreadsheet since I can't insert even the request id there
[09:09] <Mirv> but is on the dashboard
[09:09] <abeato> Mirv, so which is finally the procedure for landing in both wily and vivid?
[09:09] <abeato> Mirv, ok
[09:09] <abeato> Mirv, is doing a sync to wily fine?
[09:10] <sil2100> SYnc to wily should be fine
[09:10] <abeato> sil2100, ok, thanks
[09:12] <Mirv> abeato: fine for now, dual landing feature will be available later
[09:12] <abeato> ok
[09:42] <ogra_> hmm
[09:45] <ogra_> abeato, ^^^
[09:46] <abeato> ogra_, great, thx
[10:24] <pstolowski> 794989
[10:54] <popey> cihelp: anyone around?
[10:55] <jodh> sil2100: can I see the upstart build logs? I'm guessing this is kernel bug 1429756 (which required manual intervention to migrate the package out of -proposed for wily).
[10:55] <sil2100> jodh: sure, let me give you the link to the silo PPA
[10:55] <sil2100> jodh: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-021
[11:03] <jodh> sil2100: I've never seen that failure before. seems to be ppc only. Can you retry the build for that arch to rule out cosmic rays? :-D
[11:07] <sil2100> jodh: on it ;)
[11:08] <sil2100> jodh: rebuilding
[11:08] <alecu> Hi trainguards! May I ask for a wily silo for line 84 in the spreadsheet?
[11:09] <Mirv> alecu: you may, and I can try to battle with the spreadsheet :)
[11:09] <sil2100> :)
[11:09] <cjwatson> We can try that upstart build on a different builder if it fails again on sagari, just in case it's somehow builder-specific.
[11:10] <alecu> Mirv: oh, it's line 83. Was 84 last night.
[11:12]  * sil2100 still weeps in terror seeing google error notices in his mailbox
[11:19] <sil2100> whoops, I think the spreadsheet might have reverted itself
[11:20] <sil2100> Yep, it's reverted alright
[11:20] <sil2100> jodh: so, it seems your landing got wipped of the spreadsheet
[11:20] <sil2100> We'll have to re-input it...
[11:22] <Mirv> yep, last modified by sil2100 8 hours ago... right
[11:22] <Mirv> alecu: ^ 022
[11:22] <sil2100> ;/
[11:22] <alecu> thanks!
[11:25] <alecu> Mirv: the dashboard does not seem to match the spreadsheet rows...
[11:25] <alecu> Mirv: well, the MPs match, but the description and state does not
[11:25] <alecu> "Packages built. Testing pass. QA signed off. You can publish" <- seems wrong
[11:26] <alecu> and "Make sure recorded videos continue to play (fixes bug 1451816) (spreadsheet row 55). Tested with image 208" too
[11:26] <alecu> and that msg from queuebot does not seem right either
[11:27] <alecu> should I go ahead and build anyway?
[11:29] <alecu> ah, just caught up with sil2100's email that the spreadsheet is broken.
[11:30] <sil2100> alecu: yeah, and the topic also says it all ;)
[11:30] <sil2100> And it reverted again?!
[11:31]  * sil2100 gives up on restoring entries
[11:38] <alecu> ok, even though the dashboard is wrong, jenkins seems to be building the right thing
[11:43] <abeato> sil2100, my lxc-android-config landing has disappeared from the spreadsheet :-(
[11:43] <sil2100> Yeah, f*cking spreadsheet
[11:44] <abeato> yes...
[11:44] <abeato> sil2100, should I try to re-create it?
[11:45] <sil2100> abeato: yeah, if you could...
[11:45] <sil2100> We'll try to re-hook it to the train
[11:45] <abeato> sil2100, ok' I'll try
[11:45] <sil2100> But knowing our luck it'll revert again in some time
[11:46] <abeato> pff...
[11:46] <sil2100> We have backups though, so nothing is lost completely
[11:46] <sil2100> But still, it's crazy to re-enter stuff all the time
[11:53] <abeato> sil2100, I have re-created lines 86 and 88
[11:53] <abeato> sil2100, the silo I have is 16
[11:54] <jodh> sil2100: I've re-added as row 87, but getting a stream of errors so who knows if it's actually there or not :-(
[11:54] <abeato> yep, same for me
[11:54] <davmor2> sil2100: is image 10 broken on krillin vivid
[11:55] <abeato> davmor2, no, it is working for me
[11:55] <davmor2> then it has screwed p the download again bum
[12:02] <sil2100> abeato, jodh: I need to start preparing lunch, afterwards I'll try getting your stuff hooked up again
[12:08] <Ursinha> popey: I'll have a look
[12:12] <popey> Ursinha: thanks.
[12:24] <bzoltan> Mirv:  I am not sure if the CI sheet is good or broken again... but the silo20 is tested and ready to release.
[12:24] <bzoltan> Mirv:  for example my instance of the sheet does not contain the phablet-tools mr, but the PPA does have it.
[12:44] <Mirv> bzoltan: it's pretty much broken yes..
[12:45] <Mirv> bzoltan: thanks for pinging
[12:50] <Mirv> thostr_: it looks to me the 038 issue is just the spreadsheet being broken, so I can publish it
[12:51] <Mirv> there's nothing unclear really in trello
[12:52] <bfiller> Mirv: can you create a silo for line 85 please?
[13:05] <sil2100> Back
[13:05] <sil2100> Grrr
[13:08] <bregma> sil2100, how do I get one of my team members enabled to do ci-train landings?
[13:08] <sil2100> bregma: you make sure to pass knowledge to him, send him the link to the docs and poke me ;)
[13:08] <sil2100> Who is it you need added?
[13:13] <bregma> sil2100, ChrisTownsend
[13:13] <Mirv> bfiller: sure
[13:14] <sil2100> bregma: adding
[13:14]  * sil2100 tried getting back a few entries to the spreadsheet
[13:14] <bzoltan> Mirv:  thank you
[13:15] <Mirv> bzoltan: you're welcome
[13:15] <sil2100> bregma: done
[13:15] <bregma> sil2100, thanks
[13:20] <alecu> cihelp: ping! Hi, we are setting up a new project with kyrofa: https://launchpad.net/unity-scope-snappy and would like to have jenkins know about it, and do the builds for autolandings and MPs.
[13:21] <Mirv> bfiller: ^ silo 030
[13:22] <thostr_> Mirv: thanks
[13:22] <bfiller> Mirv: thanks
[13:23] <bfiller> boiko, salem_ : silo 30 has mission control fix
[13:23] <boiko> bfiller: ah nice, I requested that yesterday, but didn't get a silo until the end of the day
[13:23] <salem_> bfiller, thank you.
[13:24] <boiko> kenvandine: would you mind uploading the source package with this change to silo 30: https://code.launchpad.net/~tiagosh/ubuntu/wily/telepathy-mission-control-5/allow-getprop-execution/+merge/259174
[13:25] <kenvandine> boiko, sure
[13:25] <boiko> kenvandine: thanks :)
[13:26] <popey> Ursinha: any luck?
[13:32] <kenvandine> boiko, uploaded
[13:32] <boiko> kenvandine: thanks!
[13:32] <kenvandine> np
[13:35] <Ursinha> popey: one moment
[13:41] <Ursinha> popey: yesterday we had another report of these jobs being slow, we're investigating what is going on there
[13:42] <Ursinha> maybe jenkins slave is in trouble
[13:48] <ev> alecu: hi. Can you send a mail to ci-engineering-private@lists.launchpad.net about this with "autolanding" in the subject? Please provide detail on this kyrofa project, what resources or websites it requires access to (including internal ones), and anything else that might require some investigation or coordination with IS.
[13:49] <ev> alecu: if you want something to refer back to, this is all covered in the "new CI/Autolanding requests" mail I sent at the end of April
[13:49] <alecu> ev: sure! but the project is unity-scope-snappy. kyrofa is our new starter!
[13:49] <kyrofa> ev, hi!
[13:49] <alecu> :-)
[13:49] <alecu> ev: thanks for the pointers.
[13:49] <kyrofa> ev, the kyrofa project is amazing, by the way
[13:50] <ev> lol, whoops
[13:50]  * ev makes another coffee
[13:59] <alan_g> sil2100: camako said you wanted to know when mir-0,13,0 reached overlay to sync to wily; It's there.
[13:59]  * kenvandine hopes the spreadsheet isn't dieing... 
[13:59] <kenvandine> i'm getting fatal errors again
[13:59] <ogra_> you like it ?
[13:59] <sil2100> alan_g: ok, let me prepare a sync silo then
[13:59] <sil2100> kenvandine: yep, see e-mail and topic ;)
[13:59] <Wellark> hey, do we have a series added to Ubuntu in LP for vivid+overlay?
[13:59] <Wellark> I can't nominate stuff for the overlay to vivid proper
[13:59] <Wellark> as that's not where they are going to land
[13:59] <sil2100> jodh: so, upstart still seems to fail on powerpc from what I see...
[13:59] <Wellark> trainguards: plz, see above
[14:00] <sil2100> Wellark: sadly, there's no series for that, it's vivid basically... but if you want to track it in bugs, please open up an Ubuntu-RTM task
[14:00] <sil2100> We have a script that will close those
[14:10] <alan_g> cihelp: just seen two failures that look like reboot problems on mako. Could someone have a look? - https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/
[14:10] <Wellark> sil2100: thanks!
[14:10] <Ursinha> alan_g: images and channels are broken/acting weird now, there is investigation going on
[14:10] <alan_g> Ursinha: ok, thanks
[14:10] <Wellark> sil2100: do you remember the project name of "Ubuntu-RTM"?
[14:26] <Wellark> sil2100: ah, got it. it was Ubuntu RTM distribution. not project
[14:26] <Wellark> whee
[14:26] <cjwatson> sil2100,jodh: really?  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-021/+build/7443824 worked
[14:32] <Mirv> sil2100: before I forget it again, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-system-settings-online-accounts would need to be resolved. I tried to rerun it last week so it doesn't seem random. it's preventing a bunch of vivid-overlay from entering wily proper
[14:36] <sil2100> Uh oh!
[14:36] <sil2100> cjwatson: oh, ok, the dashboard lied to me then
[14:36] <sil2100> cjwatson: thanks for clearing that out :)
[14:37] <sil2100> jodh: ignore me ;p
[14:37] <sil2100> Mirv: hm, ok, thanks for pointing this out
[14:41] <jodh> sil2100: cjwatson: thanks.
[14:41] <jodh> sil2100: so, I now need to reflash with channel=ubuntu-touch/ubuntu-rtm/14.09-proposed, then 'citrain device-upgrade 021' right?
[14:42] <Ursinha> sil2100: hi :) what is ubuntu-touch/rc-proposed/ubuntu? stable... vivid?
[14:42] <Ursinha> veebers: ^
[14:43] <ogra_> Ursinha, vivid community channel
[14:44] <Ursinha> veebers: there you go :)
[14:44] <ogra_> (read: vivid but without the specific customm tarball and HERE stuff etc)
[14:46] <veebers> Ursinha, ogra_ ack cheers.
[14:46] <veebers> Ursinha: Who would know what goes into the smokedash? I'm not seeing the imageversion that was used in the gatekeeper in the dash
[14:47] <Ursinha> veebers: I think plars sent an email explaining why is that, if I haven't misread that
[14:48] <veebers> Ursinha: oh right, I'll go read my emails
[14:49] <sil2100> Ursinha: yep, vivid+overlay ;) There was an e-mail on phablet@ with the list
[14:49] <sil2100> https://wiki.ubuntu.com/Touch/Channels
[14:49] <Ursinha> sil2100: I failed to parse that :/
[14:51] <veebers> Ursinha, sil2100: Me too. Thanks for getting that clarified Ursinha
[14:52] <Ursinha> veebers: you're welcome :)
[14:54] <sil2100> Uh, but every channel mentiones from which place it builds right now, even in bold and italic ;)
[14:55] <ogra_> thats the problem
[14:55] <ogra_> missing <blink>
[14:55] <sil2100> Ooooh!
[14:55] <sil2100> :)
[14:58] <mzanetti> sil2100, ping
[14:58] <sil2100> mzanetti: pong
[14:58] <mzanetti> sil2100, so... I've finished testing silo 3 and it's now waiting for QA signoff
[14:58] <mzanetti> sil2100, when QA acks it, can we land it in both, wily and vivid?
[14:59] <sil2100> mzanetti: we would need to assign a new silo, sync silo, for vivid
[14:59] <sil2100> mzanetti: ah, the silo is for wily?
[14:59] <sil2100> Let's create a sync silo for vivid now, as QA only signs-off vivid silos right now
[15:01] <mzanetti> sil2100, erm.. wat? :D
[15:01] <sil2100> mzanetti: so, silo 003 is for wily, right?
[15:02] <mzanetti> sil2100, yes
[15:02] <mzanetti> but we want to keep unity8 in sync between wily and vivid as long as possible
[15:08] <vrruiz> kenvandine: ping
[15:09] <kenvandine> vrruiz, pong
[15:09] <vrruiz> kenvandine: Why there are no merge proposals on silos 35 and 39?
[15:09] <kenvandine> they are syncs
[15:09] <kenvandine> well, 35 isn't
[15:09] <kenvandine> it's a dput to the silo
[15:10] <kenvandine> vrruiz, i noticed on the trello board it has the wrong package name for silo 35
[15:10] <kenvandine> it should be systemd-shim
[15:11] <kenvandine> but the fix can be tested using the system-settings UI
[15:11] <kenvandine> but was in the systemd-shim package though
[15:11] <kenvandine> silo 39 is a package sync from wily
[15:11] <kenvandine> already landed in trunk
[15:12] <vrruiz> kenvandine: Title fixed
[15:12] <kenvandine> vrruiz, silo 35 is on the ota4 milestone, so i'm quite anxious to get that landed
[15:12] <Ursinha> ogra_: after all that confusion, you can't blame people for not trusting what they are reading :)
[15:12] <kenvandine> vrruiz, thx
[15:14] <vrruiz> kenvandine: Silo 39 has no description of the changes in the spreadsheet
[15:14] <kenvandine> oh... sorry i thought the changelog would be enough there
[15:15] <kenvandine> vrruiz, it's the same as line 79 on the spreadsheet
[15:15] <kenvandine> vrruiz, the testplan is updated to include the url-dispatcher test
[15:18] <vrruiz> kenvandine: I don't see automated tests on that silo :-/
[15:18] <kenvandine> all we have is unit tests, no automated integration tests for content-hub
[15:18] <kenvandine> because to test it you have to run multiple apps
[15:19] <kenvandine> this silo adds a helper, that uses functions that are all unit tested already
[15:27] <alex-abreu> trainguards can you reconfigure silo 26
[15:27] <sil2100> alex-abreu: sure, could you refresh the page and make sure the spreadsheet shows the right merges?
[15:28] <alex-abreu> sil2100, yes it seems to be the case
[15:29] <sil2100> alex-abreu: reconfigured
[15:29] <alex-abreu> thx !
[15:30]  * sil2100 needs to AFK for a while
[15:30] <sil2100> Be back later
[15:50] <Wellark> jodh: sorry, because of the sync problems in the spreadsheet I accidentally overrode your description in line 87 and I have no idea what was there
[15:51] <Wellark> trainguards: how can I request silos now that the spreadsheet is broken?
[15:51] <Wellark> unity8 CI builds are broken and I have a fix to get them unblocked
[15:52] <ogra_> Wellark, mindwaves ... or postcards
[15:53] <Wellark> well, it's not bothering me, but the unity8 team might have different opinions :)
[15:53] <Wellark> tsdgeos: hi! ^^
[15:53] <tsdgeos> :/
[15:54] <tsdgeos> yeah getting that landed would be relaly nice
[15:54] <tsdgeos> otherwise we can't land anything
[15:54] <ogra_> (i guess you simply have to wait for a trainguard to be around and do it ... )
[15:54] <tsdgeos> since our build is broken
[16:04] <jodh> Wellark: np, fixed. Dare I reload the page I wonder...
[16:05] <Wellark> jodh: the chances are that now you overrode a wrong cell :)
[16:09] <jodh> Wellark: :) I'm wondering if the google back-end is actually Lotus Notes...
[16:11] <Wellark> jodh: well, google acquired GoogleDocs from some other company so who knows what they inherited
[16:15] <robru> jodh: if you reload the page and it's not fixed, then it was never really fixed.
[16:17] <robru> Wellark: anyway you can just email me the landing details and I can assign a silo then add it to the spreadsheet later
[16:18] <jodh> robru: sure, I'm being facetious - seeing a lot of google errors today.
[16:18] <Wellark> robru: wily: https://code.launchpad.net/~unity-api-team/indicator-network/lp1456307_15.10/+merge/259502
[16:18] <Wellark> robru: vivid+overlay: https://code.launchpad.net/~unity-api-team/indicator-network/lp1456307_15.04/+merge/259518
[16:19] <Wellark> robru: no testing needed. it's just a .pc file fix
[16:20] <Wellark> tsdgeos: ^^^
[16:20] <robru> Wellark: ok you got silo 38
[16:20] <Wellark> kgunn: ^^^
[16:20] <Wellark> robru: I need to eod :(
[16:20] <Wellark> but maybe tsdgeos can keep an eye on it
[16:20] <Wellark> as he is in the US
[16:20] <Wellark> or charles or ted, maybe ?
[16:20] <tsdgeos> what do you want me to do?
[16:21] <Wellark> robru: need two silos :)
[16:21] <Wellark> they are separate MP's fro separate trunks
[16:21] <robru> Wellark: well just do the wily one first as there is only one silo left, don't want to assign it if you're not around to land it
[16:21] <Wellark> tsdgeos: can you land them? --^
[16:22] <tsdgeos> i'm not really confortable landing anything else than unity8
[16:22] <tsdgeos> Wellark: we can land it tomorrow, no hurries
[16:22] <Wellark> tsdgeos: ack.
[16:24] <Wellark> tsdgeos, robru: I'm trying to lure ted or charles to take care of the landings today
[16:28] <robru> Wellark: ok
[16:29]  * tedg resists :-)
[16:29] <tedg> Is this the pkgconfig change?
[16:31] <Ursinha> popey: that job is passing now, jenkins was feeling unwell
[16:31] <popey> Ursinha: thanks!
[16:31] <Wellark> tedg: yes. no code changes
[16:31] <Ursinha> popey: no problem, if that happens again just let me know
[16:31] <popey> k
[16:32] <Wellark> tedg: .pc filename was accidentally modified. so this restores it. and the contents of the .pc file were wrong as well
[16:32] <Wellark> I inspected the resulting -dev .debs and the contents of .pc on both MP's
[16:33] <Wellark> they are now correct
[16:33] <Wellark> no additional "testing" to do
[16:33] <Wellark> so it's just a matter of getting the silos for both wily and vivid+overlay and as soon as the packages have been build, set testing to DONE and someone hitting publish
[16:34] <tedg> Wellark, Cool
[16:34] <tedg> Wellark, Publish then get beers from tsdgeos? This I can do ;-)
[16:36] <tedg> ?
[16:37] <tedg> Wellark I only see one silo
[16:37] <tedg> Wellark, Is that right? http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu%2Flanding-038
[16:43] <dobey> tedg: btw, i guess you can get row 21 in the spreadsheet archived or deleted or whatever now?
[16:55] <tedg> dobey, Yeah, I think that happens automatically when they archive lines at some point.
[16:55] <tedg> I deallocated it and all that
[16:56] <tedg> trainguards, Oh, I get it now, I need a silo for line 93
[17:03] <robru> tedg: yeah there's a shortage of silos so I only assigned the wily one. once that lands I'll give you the vivid one
[17:03] <tedg> robru, Ah, I see. /me was confused
[17:23] <vrruiz> ping cihelp
[17:23] <Ursinha> vrruiz: oui
[17:23] <vrruiz> Hi Ursinha
[17:23] <vrruiz> Ursinha: As part of silo testing, I'm taking a look to merge proposals
[17:24] <vrruiz> Ursinha: This one https://code.launchpad.net/~jhodapp/qtubuntu-media/fix-1438115-take2/+merge/259178 has a failed job
[17:24] <vrruiz> Ursinha: The job failed because it couldn't install a package
[17:25] <vrruiz> Ursinha: Depends: libmedia-hub-dev (>= 3.2.0) but it is not going to be installed.
[17:25] <vrruiz> Ursinha: Version 3.2 is what the merge proposal provides
[17:26] <Ursinha> vrruiz: let me check
[17:28] <ev> thanks Ursinha
[17:34] <robru> brb
[17:40] <vrruiz> kenvandine: Silo 39 needs an automated test, either autopilot that checks messaging app, or a unit test that check that new feature works properly.
[17:42] <kenvandine> vrruiz, it can only be tested with an integration test, which means running multiple apps
[17:43] <vrruiz> kenvandine: Right, if you need some guidance tips for that, ping ubuntu-qa
[17:43] <kenvandine> vrruiz, can autopilot run multiple apps and introspect the interaction?
[17:43] <kenvandine> last i heard we still couldn't do that
[17:44] <vrruiz> kenvandine: I think so, they has been developing some cool integration tests that span different applications
[17:44] <kenvandine> vrruiz, it's fully unit tested, the only thing that isn't is wrapper that gets exec'd by url-dispatcher
[17:44] <kenvandine> but all the functions are unit tested
[17:46] <kenvandine> vrruiz, and this branch doesn't change anything else, just adds that wrapper that gets exec'd... so it can't cause regressions of existing features
[17:46] <kenvandine> but would be good to test in the future
[17:47] <vrruiz> kenvandine: A new feature was added, and a new test case is in the test plan. If it can be automated, needs to, instead of adding a manual test.
[17:48] <kenvandine> yeah, we haven't figured out how to automate testing of the transfers
[17:48] <kenvandine> so we've relied on unit tests and manual tests
[17:49] <kenvandine> vrruiz, it'll be significant work that wasn't planned for this sprint to step back and figure out how to automate testing of the transfers
[17:50] <vrruiz> kenvandine: Can you ping ubuntu-qa and ask whether it is possible or not? If not possible, I'm ok as it is right now.
[17:50] <kenvandine> it won't be trivial... of the tooling is available to do it, we can plan the work to do that soon
[17:53] <dobey> cihelp: if we have coverage reporting support in our cmake for a project, what do we need to do, to have the pretty coverage stuff in CI/jenkins enabled for that project?
[17:53] <ev> dobey: looking
[17:54] <Ursinha> vrruiz: I'm looking into that to try and understand why it can't find that package
[17:54] <om26er> kenvandine, Hi!
[17:54] <vrruiz> Ursinha: Thanks
[17:54] <om26er> kenvandine, re: silo35, it doesn't seem to fix the bug
[17:55] <kenvandine> om26er, did you reboot?
[17:55] <om26er> kenvandine, multiple times
[17:55] <kenvandine> i tested it on krillen and arale, fixed it for me...
[17:55] <om26er> kenvandine, I am on arale
[17:55] <om26er> kenvandine, I have systemd-shim 9-1bzr3
[17:56] <om26er> I change it to manual, reboot the phone and its back to automatic
[17:56] <kenvandine> so when you change auto to manual then go back a page, then enter the time/date it doesn't show your change?
[17:56] <kenvandine> you can test it without rebooting, it wasn't changing the value at all
[17:56] <kenvandine> om26er, try this in a terminal
[17:57] <kenvandine> timedatectl
[17:57] <kenvandine> what does that say for "NTP enabled"
[17:57] <om26er> kenvandine, 'no'
[17:57] <kenvandine> interesting
[17:58] <kenvandine> ok, without the systemd-shim fix, that would have said 'n/a'
[17:58] <kenvandine> because it didn't support NTP at all
[17:58] <kenvandine> so that means it should be working
[17:59] <kyrofa> Hey all. I have a project written in Go, and I'd like to see if I can get it hooked into the CI's pretty coverage graphs and such. I don't really know where to start
[18:00] <kenvandine>      NTP enabled: yes
[18:00] <om26er> kenvandine, change to manual, reboot, its automatic.
[18:00] <kyrofa> What sort of format does the CI expect for coverage?
[18:00] <kenvandine>      NTP enabled: no
[18:00] <om26er> kenvandine, ...and NTP enabled: yes
[18:00] <om26er> let me try without the silo
[18:00] <kenvandine> so it is changing it without rebooting?
[18:00] <kenvandine> just losing it on reboot?
[18:01] <kenvandine> without the silo it would say "n/a"
[18:01] <kenvandine> because ntp just wasn't supported at all
[18:01] <kenvandine> with the other version of systemd-shim
[18:01] <ev> dobey: what autolanding job is this for?
[18:01] <dobey> ev: for lp:unity-scope-click
[18:03] <ev> http://s-jenkins.ubuntu-ci:8080/job/unity-scope-click-ci ?
[18:03] <kenvandine> om26er, i'm confused... i just tested it again, and rebooted 3 times, each time my arale preserved the change
[18:04] <dobey> looking
[18:04] <kenvandine> current build number: 5
[18:04] <kenvandine> device name: arale
[18:04] <kenvandine> channel: ubuntu-touch/rc-proposed/meizu
[18:06] <kenvandine> bfiller, can you test silo 35 too?  it definately works for me on arale and krillin, but doesn't seem to for om26er
[18:06] <kenvandine> at least it shows his device supports ntp now, so must have the right version
[18:07] <om26er> kenvandine, it could be you are on r/w image ?
[18:07] <kenvandine> oh... perhaps!
[18:07] <kenvandine> then we have a lower level problem
[18:07] <dobey> ev: so i think so, but i'm a little confused as that seems to have even branches for vivid building in wily, while also is apparently doing the testing on the trunk branches too
[18:07] <kenvandine> i don't know how any of that works
[18:08] <kenvandine> om26er, even if that is the case, this definately fixes a big part of the problem though
[18:08] <om26er> kenvandine, what directory does that write to, we might need to get that whitelisted for r/w
[18:08] <kenvandine> without this systemd-shim thinks ntp isn't even supported
[18:08] <kenvandine> no idea
[18:09] <om26er> kenvandine, I agree, I can verify its better than 'n/a'
[18:09] <kenvandine> any of fix would be in addition of this fix
[18:09] <kenvandine> s/of/other/
[18:10] <ev> dobey: on it
[18:11] <kenvandine> om26er, but... how are you testing this if your device isn't "rw?
[18:12] <om26er> kenvandine, installed the deb after remount as r/w
[18:12] <kenvandine> i see
[18:12] <om26er> kenvandine, let me permanently enable r/w and check what happens
[18:13] <robru> tedg: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-038/+build/7445002 oops, that's not off to a good start, just noticed
[18:14] <om26er> kenvandine, yeah, its fine with r/w
[18:18] <robru> tedg: i'm not familiar with cmake-extras but whoever's hiding v0.4 forgot to ever release it to ubuntu: https://launchpad.net/ubuntu/+source/cmake-extras
[18:20] <om26er> kenvandine, while it fixes the core issue, I am afraid that alone won't change much for the user. Personally I think it needs to go in with the other relevant fix
[18:20] <kenvandine> yeah, just need to figure out the path that needs to be made writable
[18:21] <kenvandine> om26er, how do we whitelist writeable paths?
[18:21] <kenvandine> is that in a package somewhere?
[18:22] <om26er> kenvandine, I think, yes its in a package. I once landed a silo doing something similar. ogra_ would know
[18:22] <om26er> perhaps it was his landing
[18:23] <kenvandine> looks like it's in lxc-android-config
[18:33] <tedg> robru, So it seems that cmake extras was updated in vivid overlay, but not wily. Is it possible to get a copy there?
[18:34] <robru> tedg: well you'd have to do a landing of some kind. I'm not sure how possible it is to sync really.
[18:35] <tedg> robru, Ah, okay. I thought there was going to be some copies of stuff that had landed before wily opened.
[18:35] <tedg> robru, It's blocking that indicator-network silo as it needs the new version (build dep)
[18:35] <robru> tedg: i heard that happened, cmake extras must have missed it
[18:37] <tedg> Perhaps this is something the super sexy slangasek can do?
[18:37] <tedg> :-)
[18:37] <robru> tedg: I'm not sure how best to handle this. I guess i need you to branch cmake extras so there's a vivid branch and wily branch. Then null mp against wily in a silo to trigger a release.
[18:37] <slangasek> super sexy slangasek is out to lunch; you'll have to settle for grumpy codger slangasek
[18:38] <tedg> Man, I always get grump codger slangasek! ;-)
[18:38] <slangasek> robru: we should not be asking upstreams to create separate branches for vivid vs. wily if they don't have any code differences.  how's dual landing support coming along?
[18:38] <robru> slangasek: so cmake-extras 0.4 was released to vivid overlay but not wily. Now we need it in wily
[18:39] <slangasek> robru: is there any reason not to do this as a straight archive copy in this case, since it's been tested for vivid?
[18:39] <robru> slangasek: dual landing code exists but is bitrotty. Been working on spreadsheet replacement
[18:39] <vrruiz> jhodapp: Hi. Silo 25 is blocked, it has no information about the merge proposal, lacks infot about how to test it and comes with automated test.
[18:39] <slangasek> robru: ok - let's sync on that this afternoon
[18:39] <robru> slangasek: I'm not sure what the implications are of a copy vs a new branch landing
[18:40] <jhodapp> vrruiz, how to test it is in the bug report
[18:40] <slangasek> robru: the only implication is that the code will not have been separately tested against the wily archive in a silo before landing
[18:40] <robru> slangasek: isn't there some problem with vivid and wily having identical version numbers?
[18:40] <vrruiz> jhodapp: Which bug report?
[18:41] <jhodapp> vrruiz, let me link you to it, it was linked to the MR
[18:41] <slangasek> robru: there's only a problem with them having identical version numbers if they're not the identical /packages/.  In this case I'm doing a binary copy
[18:42] <robru> slangasek: Ooooooooooh ok thanks.
[18:42] <jhodapp> vrruiz, sorry it was not linked, that was in the other MR that mistakenly got landed for this fix
[18:42] <kenvandine> seb128, do you know where the ntp setting gets saved to disk?
[18:42] <kenvandine> Laney, ^^
[18:43] <jhodapp> vrruiz, https://bugs.launchpad.net/music-app/+bug/1438115
[18:43] <slangasek> tedg, robru: what's the exact version number of cmake-extras I should be looking to copy?
[18:43] <jhodapp> vrruiz, let me share the media used to reproduce the bug
[18:43] <tedg> slangasek, 0.4+15.04.20150513-0ubuntu1
[18:43] <kenvandine> we found that systemd-shim fix only partially fixes it, it only works on a device that's rw, readonly doesn't persist
[18:43] <kenvandine> so we need to add a path to the writeable paths
[18:44] <slangasek> tedg, robru: copied
[18:44] <tedg> slangasek, Thanks!
[18:44] <jhodapp> vrruiz, https://drive.google.com/open?id=0BzU5F_BCeEOHQlZ2RC10UEp2ZE0&authuser=0
[18:44] <slangasek> tedg, robru: note that going forward the goal is that the silo will support a "sync" landing request (this is something sil2100 is working on), and we will also need to support dual landings so that we can land to both releases in parallel
[18:45] <slangasek> binary copies are ok right now but will become increasingly unreliable over time
[18:45] <sil2100> Yeah, although it's only in the works still ;)
[18:45] <robru> slangasek: right
[18:50] <vrruiz> jhodapp: Do silo 24 and 25 fix the same bug?
[18:50] <jhodapp> vrruiz, yeah, just vivid/wily silos
[18:51] <vrruiz> jhodapp: Which one is wily? You can land that directly.
[18:52] <jhodapp> vrruiz, yeah it mistakenly got labeled as needing QA...it's silo 24
[18:53] <vrruiz> jhodapp: Ok, I'm approving it.
[18:53] <jhodapp> vrruiz, ok
[18:55] <kyrofa> cihelp: I have a project written in Go, and I'd like to see if I can get it hooked into the CI's pretty coverage graphs and such. What sort of format does the CI expect?
[18:56] <ev> kyrofa: gcov
[18:59] <kyrofa> ev, like .gcno/.gcda files, or gcovr xml or html?
[18:59] <ev> xml
[19:00] <ev> it specifically looks for a coverage.xml file
[19:00] <ev> fginther might be able to say more to that
[19:00] <kyrofa> ev, thank you for the information!
[19:00] <ev> sure thing
[19:01] <ev> dobey: just an update; rolling out the change now. I'll let you know after I've kicked off a new build to confirm the coverage stuff works
[19:02] <davmor2> sil2100: vivid tarball is good I've mailed alextu
[19:02] <dobey> ev: ok, thanks
[19:04] <sil2100> davmor2: \o/ tahanks!
[19:20] <vrruiz> boiko: ping
[19:21] <boiko> rvr: pong
[19:22] <rvr> boiko: I'm in silo 28, and I'm not sure whether I am doing anything wrong
[19:22] <boiko> rvr: what's up?
[19:22] <rvr> boiko: Tapping back on the messaging app should go back to address book, right?
[19:23] <boiko> rvr: let me check the bug description
[19:24] <rvr> boiko: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1328915
[19:25] <boiko> bfiller: do you know if that's the expected behavior? ^
[19:26] <bfiller> rvr: which scenario exactly?
[19:27] <boiko> bfiller: go to address-book-app, tap messaging icon of a contact, compose a message, send it, once tapping back should go back to address-book-app?
[19:27] <sil2100> btw. everyone, the spreadsheet seems to be better now
[19:27] <bfiller> boiko: not sure, let me try
[19:27] <rvr> bfiller: Well, I'm testing silo 28, and it links to the above bug. I opened the messaging application, tapped on a contact, tapped in the message icon, which opens the messaging app, and when I press the back button there, it shows the main messaging app, doesn't go back to address book.
[19:27] <sil2100> The last failure seems to be from 4 hours ago
[19:28] <bfiller> rvr: that seems wrong, but it's what it does without silo 28
[19:29] <boiko> bfiller: that will require changes in messaging-app that are not present on that silo
[19:30] <bfiller> rvr: so that bug is not fixed by this silo, it shouldn't have been marked as such
[19:31] <boiko> rvr: it's my bad, I was focused on testing and looking for regressions and I actually didn't test that the bug was fixed. The main purpose of this silo is actually to support contact editting from inside dialer and messaging apps
[19:32] <rvr> boiko: I see, where is the test case for that?
[19:33] <boiko> rvr: not sure renato updated the manual test case, but he wrote autopilot tests for that for sure (I reviewed those)
[19:38] <boiko> rvr: I am updating the MRs with the correct bug reports linked, sorry for that, I will also add entries to the manual test plans regarding contact editing
[19:39] <rvr> boiko: Nice
[19:39] <boiko> rvr: should be ready pretty soon, but other than the contact editing and the expansion removal, it is worth going through all the test plan to make sure there are no regressions
[19:45] <boiko> rvr: sorry for the confusion, btw
[19:46] <rvr> boiko: No problem
[19:49] <robru> sil2100: are you still using staging area? i might need to blow it away soonish
[19:52] <sil2100> robru: feel free :)
[19:52] <robru> sil2100: thanks
[19:53] <rvr> boiko: Share contact doesn't work in dialer app
[19:53] <sil2100> robru: not sure if I'll need it tomorrow or not, I don't seem to be in the stage that I could use formal testing
[19:53] <rvr> boiko: Neither in address book
[19:54] <rvr> boiko: Tapping on the share button shows nothing, whereas doing that in the address book shows some Tagger and Messaging
[19:54] <robru> sil2100: ok I'll try not to leave it in a broken state at the end of my shift ;-)
[20:00] <boiko> rvr: let me check
[20:03] <boiko> rvr: reinstalling the silo to check, just a sec
[20:18] <rvr> boiko: Also, the address book has now a settings button. Nothing happens when tapped.
[20:18] <robru> tedg: ok looks like silo 38 built, can you verify that it works as advertised and then we'll move forward with the vivid fix
[20:19] <tedg> robru, It's still publishing, give it a couple seconds more :-)
[20:19] <rvr> boiko: Actually, something happens. The contacts disappear.
[20:20] <robru> tedg: oh heh, thanks for keeping on top of that ;-)
[20:20] <elopio> kenvandine: rvr: you can run multiple apps in an autopilot test.
[20:21] <elopio> you just have to make sure that they have the testability enabled. And if you don't launch them with self.launch_*_application, you will have to use the method to get the proxy object from the process name.
[20:21] <sil2100> robru: just for your info, https://wiki.ubuntu.com/citrain/SyncSilos
[20:21] <elopio> (sorry for the late pong)
[20:21] <sil2100> robru: in case you need it ;)
[20:22] <robru> sil2100: is that active in production now?
[20:22] <sil2100> robru: yes, works for CI Train released packages
[20:22] <boiko> rvr: let me look into those, I will get back to you once they are fixed and reviewed
[20:23] <sil2100> I wouldn't use it for non-train projects as then it doesn't change the versions ;/
[20:23] <sil2100> Since I don't want to play guessing game about how upstreams version their packages
[20:24] <elopio> kenvandine: rvr: you just have to be careful of not adding an unnecessary dependency on the branch. For example, it's not necessary to test that the messaging app launches the address book app. We can just test that the messaging app sends the right message to url-dispatcher.
[20:24] <sil2100> Ok, I need to go now
[20:24] <sil2100> o/
[20:54] <tedg> robru, I think we're gonna have to wait on Wellark here.
[20:54] <tedg> robru, It seems the previous version of indicator-network wasn't sync'd to Wily as well.
[20:55] <tedg> robru, So that silo is actually huge
[20:56] <robru> tedg: erk, ok
[20:57] <robru> tedg: oh i see, yes changelog is epic
[21:05] <elopio> cihelp: can you help me figuring out what went wrong here? https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily-mako/11/console
[21:06] <plars> elopio: it looks like it just failed to install
[21:06] <plars> elopio: probably related to the email I sent earlier, it should just be retried I think
[21:08] <elopio> plars: ack. I'll retry and look for your email.
[21:08] <elopio> thanks.
[21:09] <fginther> kyrofa, ev had it right, a gcovr xml file is the expected format
[22:29] <ev> dobey: it's set up, but not properly collecting the coverage data yet. I won't have another chance today to dig at why, so I've kicked it off to the next vanguard (tomorrow)
[22:30] <ev> http://s-jenkins.ubuntu-ci:8080/job/unity-scope-click-wily-amd64-ci/12/