/srv/irclogs.ubuntu.com/2016/04/28/#ubuntu-ci-eng.txt

bregmahey 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?00:32
robrubregma: 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 ;-)01:03
=== fginther` is now known as fginther
bzoltan_jibel: 04703:05
bzoltan_jibel: https://requests.ci-train.ubuntu.com/#/ticket/132203:06
=== chihchun_afk is now known as chihchun
jibelbzoltan_, ok, it's already in our queue, I thought there was another one.05:59
jibelbzoltan_, it should land this week06:00
bzoltan_jibel:  given that you will not find a problem what I missed06:00
ToyKeepercharles, ondra: Question for you on ticket 1299 (indicator-display): https://trello.com/c/gzf3hdwh/3111-1299-ubuntu-landing-035-indicator-display-charles-ondra06:00
bzoltan_jibel: :)06:00
mterrytrainguards: got an odd publish error, what's this mean? https://ci-train.ubuntu.com/job/ubuntu-landing-033-2-publish/3/console07:10
robrumterry: it means everything published successfully07:11
mterryrobru, got a funny way of showing it!07:11
robrumterry: (the error is that there's no artifacts, artifacts are only used for publishing to archive, but duals go to overlay ppa)07:12
robrumterry: yeah Jenkins is poorly configured, sorry07:12
mterryrobru, huh ok I get that07:12
mterryrobru, but yup ^ merging, cool07:12
mterryrobru, thanks man07:13
robrumterry: you're welcome. Jenkins is slowly on its way out so things will make more sense eventually07:13
oSoMoNMirv, 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’t07:51
jibelsil2100, do I need a silo to revert lxc in xenial in the overlay or you just copy the packges?07:54
oSoMoNjibel, 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 britney07:58
sil2100jibel: let me just copy those over, only the lxc source was needing revert right?07:58
sil2100What about the fixed lxc-android-config?07:59
jibelyeah we'd need to revert to lxc 2.0.0~rc2-0ubuntu207:59
jibelsil2100, and this change in lxc-android-config.conf http://paste.ubuntu.com/16092480/08:00
jibelsil2100, devel-proposed won't be awesome, but at least it'll boot08:01
jibel(all the scopes are blank, cannot setup wifi, cellular connection is unreliable, clicks don't work, lot of blank pages everywhere, ...)08:01
sil2100Ok08:06
sil2100Remember, devel-proposed is yakkety right now, so staging will be awesome - I'll leave yakkety as it is08:06
jibelsil2100, right, staging08:08
jibelwon't be awesome either08:08
oSoMoNsil2100, 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’t08:41
Saviqmterry, can you recycle for oSoMoN ↑08:42
Saviqand we really need to look into the wizard tests08:42
sil2100oSoMoN: on it08:44
sil2100oSoMoN: re-running08:44
jibeloSoMoN, not from the top of my head. Maybe autopilot itself?08:45
oSoMoNSaviq, sil2100: thanks08:45
oSoMoNSaviq, is that test known to be flaky?08:45
SaviqoSoMoN, yes08:45
oSoMoN:/08:46
oSoMoNjibel, thanks, I’ll check autopilot itself08:46
jibeloSoMoN, if the failing test is test_account something, it's a know flaky test fixed in another silo08:47
oSoMoNgood08:48
SaviqoSoMoN, we've got a landing which fixes that up for QA already, though08:48
oSoMoNjibel, 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
jibeloSoMoN, I'll move it to ready08:49
oSoMoNcheers08:49
oSoMoNautopilot doesn’t seem to have autopkgtests08:51
jibeloSoMoN, we have a discussion next week to run autopilot tests as part of the landings after autopkgtests and before manual verification08:52
jibeloSoMoN, we'll start with unity8 but can also involve you in the discussion if you want to08:52
oSoMoNjibel, 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 same08:52
oSoMoNrunning the tests really is (should be) part of the development process08:53
MirvoSoMoN: mterry sorry guys I'm not feeling well today09:24
=== jin_ is now known as jin-eat
jibeldavmor2, ^ thanks!11:04
davmor2jibel: no worries nice improvement in speed/flow on krillin and frieza with it :) which I'm sure Mirv will confirm for you :)11:06
jibeldavmor2, I confirm. I tried it too11:08
rvrMirv: mzanetti: Apart from the usual location apps, anything else to check in silo 67?11:16
oSoMoNjibel, I’m not seeing silo 10 on the QA trello board, anything (other than the unity8 flaky test) blocking it?11:16
rvroSoMoN: Automated SignoffFailed11:18
rvroSoMoN: I think is that11:18
sil2100\o/11:19
jibeloSoMoN, looking11:19
jibeloSoMoN, the status was still 'Required'11:20
jibelchanged again11:20
oSoMoNjibel, thanks11:20
davmor2and sil2100 there randomly cheering for himself11:21
sil2100I'm just cheering for the mir silo, woo!11:21
sil2100seb128: 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
sil2100https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-1303/2016-04-27_09:13:44/xenial/mir/packaging_changes.diff11:23
seb128sil2100, 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
seb128the arch list is not needed anymore?11:24
seb128looks fine otherwise11:25
mzanettirvr, one sec, I'll give you an app to test with11:37
mzanettirvr, http://notyetthere.org/data/mambogps.mzanetti_0.1_armhf.click11:38
rvrmzanetti: Ack11:38
mzanettirvr, without the silo, routing will not work11:38
mzanettirvr, with the silo, it should11:38
rvrmzanetti: These test instructions should be added to the silo :-/11:39
mzanettirvr, right... sorry... I didn't set up that silo and Mirv did not know about this app11:39
rvrmzanetti: How do I add a route?11:41
mzanettirvr, bottom edge11:44
rvrmzanetti: Nice, it works11:45
mzanetticool :)11:45
rvrSilo approved11:46
=== alan_g is now known as alan_g|lunch
=== _salem is now known as salem_
rvroSoMoN: Hi12:53
rvroSoMoN: I'm testing silo 10. I shared a link to twitter, but I can't see the title12:54
rvroSoMoN: Hmm.. reading the bug thread, seems it needs changes in other projects. So, anything special to check?12:56
=== alan_g|lunch is now known as alan_g
oSoMoNrvr, indeed, there’s also a bug in content-hub, so there is no visible change in the browser atm13:13
oSoMoNso nothing to check, really13:14
oSoMoNrvr, you can check that when sharing a link the URL is correctly being shared (no regression)13:14
rvroSoMoN: Yeah, it shares the URL fine13:16
rvroSoMoN: Then, approving the silo13:17
oSoMoNrvr, thanks13:22
oSoMoNMirv, sil2100: can one of you publish silo 10 please? I’m not allowed to due to packaging changes13:25
=== chihchun is now known as chihchun_afk
kenvandinetedg, did you get a preNEW review for silo 53?13:50
tedgkenvandine: For the polkit agent?13:51
kenvandineyeah13:51
tedgkenvandine: Yes, I got seb128 to review it, and suggest changes. He wanted to double check those changes but is sprinting.13:51
kenvandineok13:52
kenvandinetedg, so you made the changes right?13:52
tedgkenvandine: Yes, of course :-)13:52
kenvandinesure... :)13:53
kenvandinetedg, i'm going to hold off publishing it then13:54
=== _morphis is now known as morphis
awe_sil2100, morphis asked me about the required change to livecd-rootfs that we want to coordinate with the NM 1.2 landing14:17
awe_it looks like davmor2 will finish silo testing today14:17
davmor2morphis: get ready for it14:42
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 ?14:49
greybacksil2100: 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 overlay15:20
greybacksomething seems to be preventing the newer mir installing15:20
greybacksil2100: please ignore, whatever it was has gone away15:45
Mirvbzoltan_: restarting16:32
Saviqtrainguards, 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:33
MirvSaviq: done16:45
SaviqMirv, thanks16:45
Saviqsil2100, 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 repeats16:52
=== alan_g is now known as alan_g|EOD
bzoltan_Mirv:  would you do the same for th eamd64 too please https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-047/excuses.html17:12
kgunntrainguards could someone retrigger arm64 vivid build on https://requests.ci-train.ubuntu.com/#/ticket/133618:25
robrukgunn: done18:40
kgunnthanks18:40
robruYw18:41
jgdxrvr, I'm here for an hour if you need anything20:03
tedgWhen will xenial-overlay packages be pushed into Yakety21:44

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!