[00:32] <bregma> hey robru question for you: I have an old silo with a bunch of MPs for packages I want to get rid of, is there a way to remove them or should I just abandon the silo and start afresh?
[01:03] <robru> bregma: you can abandon and reassign the same ticket, no need to make a new ticket. I'm also capable of clearing out the old packages but I'm afk and in vacation ;-)
[03:05] <bzoltan_> jibel: 047
[03:06] <bzoltan_> jibel: https://requests.ci-train.ubuntu.com/#/ticket/1322
[05:59] <jibel> bzoltan_, ok, it's already in our queue, I thought there was another one.
[06:00] <jibel> bzoltan_, it should land this week
[06:00] <bzoltan_> jibel:  given that you will not find a problem what I missed
[06:00] <ToyKeeper> charles, ondra: Question for you on ticket 1299 (indicator-display): https://trello.com/c/gzf3hdwh/3111-1299-ubuntu-landing-035-indicator-display-charles-ondra
[06:00] <bzoltan_> jibel: :)
[07:10] <mterry> trainguards: got an odd publish error, what's this mean? https://ci-train.ubuntu.com/job/ubuntu-landing-033-2-publish/3/console
[07:11] <robru> mterry: it means everything published successfully
[07:11] <mterry> robru, got a funny way of showing it!
[07:12] <robru> mterry: (the error is that there's no artifacts, artifacts are only used for publishing to archive, but duals go to overlay ppa)
[07:12] <robru> mterry: yeah Jenkins is poorly configured, sorry
[07:12] <mterry> robru, huh ok I get that
[07:12] <mterry> robru, but yup ^ merging, cool
[07:13] <mterry> robru, thanks man
[07:13] <robru> mterry: you're welcome. Jenkins is slowly on its way out so things will make more sense eventually
[07:51] <oSoMoN> Mirv, good morning! do you have permissions to re-run the failed run at https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-010/excuses.html ? I apparently don’t
[07:54] <jibel> sil2100, do I need a silo to revert lxc in xenial in the overlay or you just copy the packges?
[07:58] <oSoMoN> jibel, do you know if there are packages in the archive with autopkgtests that run autopilot tests? I wanna do that for webbrowser-app but getting "X11: DisplayNameError('',)" when the tests are run by britney
[07:58] <sil2100> jibel: let me just copy those over, only the lxc source was needing revert right?
[07:59] <sil2100> What about the fixed lxc-android-config?
[07:59] <jibel> yeah we'd need to revert to lxc 2.0.0~rc2-0ubuntu2
[08:00] <jibel> sil2100, and this change in lxc-android-config.conf http://paste.ubuntu.com/16092480/
[08:01] <jibel> sil2100, devel-proposed won't be awesome, but at least it'll boot
[08:01] <jibel> (all the scopes are blank, cannot setup wifi, cellular connection is unreliable, clicks don't work, lot of blank pages everywhere, ...)
[08:06] <sil2100> Ok
[08:06] <sil2100> Remember, devel-proposed is yakkety right now, so staging will be awesome - I'll leave yakkety as it is
[08:08] <jibel> sil2100, right, staging
[08:08] <jibel> won't be awesome either
[08:41] <oSoMoN> sil2100, hey, do you have permissions to re-run the failed run at https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-010/excuses.html ? I apparently don’t
[08:42] <Saviq> mterry, can you recycle for oSoMoN ↑
[08:42] <Saviq> and we really need to look into the wizard tests
[08:44] <sil2100> oSoMoN: on it
[08:44] <sil2100> oSoMoN: re-running
[08:45] <jibel> oSoMoN, not from the top of my head. Maybe autopilot itself?
[08:45] <oSoMoN> Saviq, sil2100: thanks
[08:45] <oSoMoN> Saviq, is that test known to be flaky?
[08:45] <Saviq> oSoMoN, yes
[08:46] <oSoMoN> :/
[08:46] <oSoMoN> jibel, thanks, I’ll check autopilot itself
[08:47] <jibel> oSoMoN, if the failing test is test_account something, it's a know flaky test fixed in another silo
[08:48] <oSoMoN> good
[08:48] <Saviq> oSoMoN, we've got a landing which fixes that up for QA already, though
[08:49] <oSoMoN> jibel, given that it’s the only failed test and that it’s known to be flaky, is it really worth a re-run? or can silo 10 go to QA validation directly maybe?
[08:49] <jibel> oSoMoN, I'll move it to ready
[08:49] <oSoMoN> cheers
[08:51] <oSoMoN> autopilot doesn’t seem to have autopkgtests
[08:52] <jibel> oSoMoN, we have a discussion next week to run autopilot tests as part of the landings after autopkgtests and before manual verification
[08:52] <jibel> oSoMoN, we'll start with unity8 but can also involve you in the discussion if you want to
[08:52] <oSoMoN> jibel, fwiw I always run the autopilot tests myself on at least one device and desktop before marking a silo ready for QA, and I would expect others to do the same
[08:53] <oSoMoN> running the tests really is (should be) part of the development process
[09:24] <Mirv> oSoMoN: mterry sorry guys I'm not feeling well today
[11:04] <jibel> davmor2, ^ thanks!
[11:06] <davmor2> jibel: no worries nice improvement in speed/flow on krillin and frieza with it :) which I'm sure Mirv will confirm for you :)
[11:08] <jibel> davmor2, I confirm. I tried it too
[11:16] <rvr> Mirv: mzanetti: Apart from the usual location apps, anything else to check in silo 67?
[11:16] <oSoMoN> jibel, I’m not seeing silo 10 on the QA trello board, anything (other than the unity8 flaky test) blocking it?
[11:18] <rvr> oSoMoN: Automated Signoff	Failed
[11:18] <rvr> oSoMoN: I think is that
[11:19] <sil2100> \o/
[11:19] <jibel> oSoMoN, looking
[11:20] <jibel> oSoMoN, the status was still 'Required'
[11:20] <jibel> changed again
[11:20] <oSoMoN> jibel, thanks
[11:21] <davmor2> and sil2100 there randomly cheering for himself
[11:21] <sil2100> I'm just cheering for the mir silo, woo!
[11:23] <sil2100> seb128: hey! We have a new ABI bump of mir with new sonames, can I get a +1 from your archive-admin binNEW powers on it? All looks good as always:
[11:23] <sil2100> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-1303/2016-04-27_09:13:44/xenial/mir/packaging_changes.diff
[11:24] <seb128> sil2100, why is that change not documented in the changelog?
[11:24] <seb128> -               android-headers (>=4.4.2) [i386 amd64 armhf],
[11:24] <seb128> +               android-headers-23,
[11:24] <seb128> the arch list is not needed anymore?
[11:25] <seb128> looks fine otherwise
[11:37] <mzanetti> rvr, one sec, I'll give you an app to test with
[11:38] <mzanetti> rvr, http://notyetthere.org/data/mambogps.mzanetti_0.1_armhf.click
[11:38] <rvr> mzanetti: Ack
[11:38] <mzanetti> rvr, without the silo, routing will not work
[11:38] <mzanetti> rvr, with the silo, it should
[11:39] <rvr> mzanetti: These test instructions should be added to the silo :-/
[11:39] <mzanetti> rvr, right... sorry... I didn't set up that silo and Mirv did not know about this app
[11:41] <rvr> mzanetti: How do I add a route?
[11:44] <mzanetti> rvr, bottom edge
[11:45] <rvr> mzanetti: Nice, it works
[11:45] <mzanetti> cool :)
[11:46] <rvr> Silo approved
[12:53] <rvr> oSoMoN: Hi
[12:54] <rvr> oSoMoN: I'm testing silo 10. I shared a link to twitter, but I can't see the title
[12:56] <rvr> oSoMoN: Hmm.. reading the bug thread, seems it needs changes in other projects. So, anything special to check?
[13:13] <oSoMoN> rvr, indeed, there’s also a bug in content-hub, so there is no visible change in the browser atm
[13:14] <oSoMoN> so nothing to check, really
[13:14] <oSoMoN> rvr, you can check that when sharing a link the URL is correctly being shared (no regression)
[13:16] <rvr> oSoMoN: Yeah, it shares the URL fine
[13:17] <rvr> oSoMoN: Then, approving the silo
[13:22] <oSoMoN> rvr, thanks
[13:25] <oSoMoN> Mirv, sil2100: can one of you publish silo 10 please? I’m not allowed to due to packaging changes
[13:50] <kenvandine> tedg, did you get a preNEW review for silo 53?
[13:51] <tedg> kenvandine: For the polkit agent?
[13:51] <kenvandine> yeah
[13:51] <tedg> kenvandine: Yes, I got seb128 to review it, and suggest changes. He wanted to double check those changes but is sprinting.
[13:52] <kenvandine> ok
[13:52] <kenvandine> tedg, so you made the changes right?
[13:52] <tedg> kenvandine: Yes, of course :-)
[13:53] <kenvandine> sure... :)
[13:54] <kenvandine> tedg, i'm going to hold off publishing it then
[14:17] <awe_> sil2100, morphis asked me about the required change to livecd-rootfs that we want to coordinate with the NM 1.2 landing
[14:17] <awe_> it looks like davmor2 will finish silo testing today
[14:42] <davmor2> morphis: get ready for it
[14:49] <bzoltan_> Mirv: or sil2100: would you know somebody who could trigger a retest for this https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-047/excuses.html ?
[15:20] <greyback> sil2100: hey, dednick and I flashed our mako with latest rc-proposed, but noticed that the mir version that is installed is from vivid, not from the overlay
[15:20] <greyback> something seems to be preventing the newer mir installing
[15:45] <greyback> sil2100: please ignore, whatever it was has gone away
[16:32] <Mirv> bzoltan_: restarting
[16:33] <Saviq> trainguards, can someone please copy oxide (both vivid and xenial) in ppa:saviq/train to silo 69, thanks!
[16:33] <Saviq> (and potentially cancel the current builds so that we don't waste builders' time)
[16:45] <Mirv> Saviq: done
[16:45] <Saviq> Mirv, thanks
[16:52] <Saviq> sil2100, can you please recycle the failure in https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-027/excuses.html - I'll keep an eye out for whether it repeats
[17:12] <bzoltan_> Mirv:  would you do the same for th eamd64 too please https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-047/excuses.html
[18:25] <kgunn> trainguards could someone retrigger arm64 vivid build on https://requests.ci-train.ubuntu.com/#/ticket/1336
[18:40] <robru> kgunn: done
[18:40] <kgunn> thanks
[18:41] <robru> Yw
[20:03] <jgdx> rvr, I'm here for an hour if you need anything
[21:44] <tedg> When will xenial-overlay packages be pushed into Yakety