/srv/irclogs.ubuntu.com/2016/05/19/#ubuntu-ci-eng.txt

=== chihchun_afk is now known as chihchun
=== marcusto_ is now known as marcustomlinson
dbarth_sil2100: hey, just to confirm: there's a xenial overlay now, right?07:26
dbarth_ie, if we land a dual silo with oxide, it's not going to touch the archive for real?07:26
sil2100dbarth_: hey! Yes07:32
sil2100dbarth_: the phone is operating on the xenial-overlay now in dual landings07:32
dbarth_sil2100: cool, thanks07:35
dbarth_oSoMoN: so I think we're good to go with the silo now07:36
oSoMoNdbarth_, except for the fact that the xenial build of oxide on armhf failed in the silo (and consequently the corresponding webbrowser-app build failed too)07:37
=== chihchun is now known as chihchun_afk
oSoMoNdbarth_, we should also put oxide 1.15.3 in the silo07:37
oSoMoNsil2100, would it be ok to do a binary copy of oxide packages from https://launchpad.net/~oxide-builds/+archive/ubuntu/oxide-next-for-stable-phone-overlay/+packages to silo 3 ?07:38
oSoMoN(that PPA is built against the overlay)07:39
sil2100oSoMoN: the problem might be the lower version of the one in the PPA07:43
sil2100oSoMoN: let me delete the silo 3 oxide and try to bin-copy the one from the PPA07:43
sil2100But I anticipate the version number to be a problem07:43
sil2100oSoMoN: you ok with me deleting the old oxide in silo 3?07:44
oSoMoNsil2100, that’s fine, but I’m not sure I understand the issue? the version in the oxide-next-for-stable-phone-overlay PPA is higher than the version in the silo, isn’t it?07:44
sil2100Oh07:45
sil2100Sorry, right!07:45
sil2100I didn't read the main version correctly, yeah, .2 here and .3 there07:46
sil2100Copying07:47
oSoMoNthanks!07:48
=== chihchun_afk is now known as chihchun
Mirvsil2100: bzoltan: where the meeting?09:01
bzoltanMirv: sil2100: https://plus.google.com/hangouts/_/canonical.com/liberating-the?authuser=0&hceid=em9sdGFuLmJhbG9naEBjYW5vbmljYWwuY29t.bj95cmk4g3496q75m0jr9e2pvo09:01
=== chihchun is now known as chihchun_afk
sil2100bzoltan: crap!09:30
bzoltansil2100:  no worries :)09:30
=== chihchun_afk is now known as chihchun
Mirvsil2100: I was trying to explain that once I get my Meizu Pro 5 tomorrow I should hopefully have fast unbreaking 4G connection even outside :)09:48
Mirvok, now I really continue to the lunch09:49
sil2100Mirv: hah!09:56
sil2100:)09:56
MirvI'm eagerly waiting for it also because that frees up my krillin for development and I can finally do side-by-side comparisons (with mako)09:58
Mirvit has arrived to Finland now09:59
=== greyback is now known as greyback|bbiab
=== marcusto_ is now known as marcustomlinson
sil2100dbarth_: hey! Did you guys have the oxide weekly meeting already?11:27
Saviqrvr, jibel, looks like 58 request got duped on your Trello board11:56
rvrSaviq: Let me see11:56
Saviqrvr, there's one at the top of Ready and one at the bottom of Need QA11:56
jibelSaviq, it happens when a silo is rebuilt and ready for qa again11:57
rvrNew card removed11:57
Saviqack, tx11:57
Saviqthought it checked for an existing card (probably does, in Need QA)11:58
jibelSaviq, it doesn't, this trello board and the bot were not supposed to live that long11:59
jibelthe bot needs some love now11:59
Saviqnothing is11:59
Saviq(supposed to live long)11:59
dbarth_sil2100: we did, that was on tuesday; what's up?12:19
sil2100dbarth_: any news on the arm64 oxide bits?12:37
Trevinhosil2100: hey, how can I get rid of unity-settings-daemon pacakges from the silo https://requests.ci-train.ubuntu.com/#/ticket/141912:49
Trevinho?12:49
pmcgowansil2100, thats going to take some time, just started investigating12:52
dbarth_sil2100: yes, chrisccoulson is going to look into that; it's not a simple build option to turn on, considering all of the bit that go into blink itself, but he feels it's doable in a reasonable timeframe12:53
dbarth_sil2100: what is reassuring is that there are arm64 builds of chrome already12:53
pmcgowandbarth_, do you have a 15.2 silo coming?12:53
sil2100Trevinho: hey! Let me try helping you13:04
sil2100dbarth_, pmcgowan: phew, thanks, since that will be one of the biggest xenial blockers right now13:04
sil2100dbarth_, pmcgowan: the other big one, platform-api, already has a fix in a silo13:05
pmcgowandbarth_, maybe santosh can get that going unless you already thought of that13:07
dbarth_pmcgowan: it's going to be chris initially mostly; santosh is up next on a memory optimization bug14:01
pmcgowandbarth_, ack14:01
dbarth_https://bugs.launchpad.net/oxide/+bug/150129714:01
ubot5Launchpad bug 1501297 in Oxide "Try to reduce memory consumption before an application is backgrounded" [High,Triaged]14:01
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
Trevinhosil2100: have you been able to get rid of that pkg? :)14:46
sil2100Trevinho: aaaaaa... no, but I removed it now :)14:47
Trevinhosil2100: thanks14:47
sil2100Sorry!14:47
Trevinhosil2100: np... you'll have to publish that silo soon anyway :=14:47
Trevinho:)14:47
Trevinhosil2100: was just removing it from the ppa enough, or is there something to do at ci-train level too?14:48
sil2100Trevinho: no, it should be gone now on the next silo refresh14:49
Trevinhok14:49
seb128so just ppa delete?14:49
sil2100(as long as no merges for it are added)14:49
Trevinhoseb128: FYU ^14:49
seb128I could have done that14:49
seb128but I though it would confuse the CI train14:49
Trevinhoseb128: damn, you've eyes everywhere!14:49
seb128that at least the silo would need to be reconfigured14:49
seb128Trevinho, ;-)14:49
Trevinhoand... s/FYU/FYI/14:50
robrusil2100: I see you merged the branches, did you get webops to do the rollout15:09
sil2100robru: not yet, wait a moment with that if you can15:09
sil2100I wanted to do the batch copy first but I see that it would overwrite some bits so I need to consult slangasek first before proceeding15:10
robrusil2100: yeah so the thing is, lp:cupstream2distro auto-rolls-out every hour but lp:bileto doesn't, so currently in production dual silos will now publish xenial to SRUs15:10
sil2100Oh, it does? Oh man, I forgot about that15:10
robrusil2100: I guess it's fine as long as nobody published anything15:10
sil2100No, not that I know of at least15:11
robrusil2100: ok, I need breakfast, we probably should rollout bileto sooner rather than later.15:12
sil2100Yeah, I guess everything will be good after the meeting is over15:12
robrusil2100: what was the issue? some yakkety uploads conflict with what's in xenial overlay?15:28
sil2100robru: yeah, I can't do a full batch binary copy of all xenial overlay to yakkety as yakkety moved forward - this means that core-devs had to no-change rebuild some of them due to toolchain changes15:30
sil2100So when I would overwrite those with our old binaries, those packages would be again stuck in limbo as they would dep on old libraries and binaries15:30
oSoMoNubuntu-qa: what’s the current throughput of the QA team for silo validation? any chance silo 53 will be tested before EOW ?15:30
rvroSoMoN: It's on the queue15:31
rvrNot sure it will land this week, but we'll do our best15:31
sil2100robru: will have to probably skip those packages that are conflicting and do source-copies with version numbers changed15:31
sil2100But I want to confirm with Steve first15:31
robrusil2100: yeah source copy with bumped version number sounds like the right approach to me15:34
sil2100robru: ok, so anyway, if you have a moment I guess it's good to update bileto15:40
sil2100I'll be performing the batch copy in a moment but I guess having bileto switched won't make a difference15:40
oSoMoNrvr, thanks! you’re doing a great job, much appreciated15:49
=== chihchun is now known as chihchun_afk
kdubI think my autopackage tests got stuck somehow... looks like its stuck downloading something? https://requests.ci-train.ubuntu.com/#/ticket/137917:04
Saviqrobru, hey, I think something went wrong after trying to make this silo triple https://requests.ci-train.ubuntu.com/#/ticket/142617:36
robruwat17:37
robruSaviq: just abandon and reassign17:38
Saviqack17:38
Saviqmterry, FYI ↑17:38
mterrySaviq, hrm17:38
SaviqI think it tried to get the highest version from yakkety17:39
Saviqand apply to overlay, which was already ahead17:39
robrukdub: not sure what makes you think that. grep for 069 in http://autopkgtest.ubuntu.com/running.shtml and it shows a test running with some failures17:40
robruSaviq: oh that's possible. yeah the versioning would go by yakkety and then it would decrease the series value for xenial and vivid.17:40
Saviqnot series, but $date.$rebuild17:40
kdubrobru, yeah, you're right, it just paused for a long time, but looks like it got going again17:41
robruSaviq: no but I mean when it decides what $date.$rebuild to use, it looks exclusively at yakkety, and then for xenial and vivid it literally just s/16.10/$series/17:41
Saviqright, yes17:41
dobeyrobru: i guess the overlay xenial packages haven't been copied to yakkety?17:41
robrudobey: sil is working on it, I dunno how far along he is.17:41
Saviqdobey, still would be an issue if you've rebuilt in silo17:42
Saviqrobru, you might wanna mention that Re: your trio announcement17:42
robruSaviq: your other option is to wait for tomorrow then $date will be one higher and it'll work ;-)17:42
Saviqlol17:42
dobeywell, i tried to rebuild. but libual isn't new enough17:42
robruSaviq: actually it goes by UTC so UTC tomorrow is only a few hours away17:42
Saviqmeh, looks like I got the same silo :P17:43
dobeyand apparently somoene did a manual upload to y for another thing17:43
robruSaviq: same silo is fine, all the old packages will be deleted.17:43
Saviqstill need to wait for them to be deleted, no?17:43
Saviqi.e. it will take an hour or so17:43
robruSaviq: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-059/+packages lgtm17:44
dobey*sigh*17:44
Saviqrobru, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-059/+packages?field.name_filter=&field.status_filter=&field.series_filter=17:44
mterrySaviq, are you going to triple-ize silo 58?17:44
Saviqmterry, no17:44
robruSaviq: oh yeah right. you might have to wait for utc tomorrow.17:45
robruSaviq: or get a dummy upload to yakkety with that version number so that it knows to +.1 it17:45
Saviqrobru, or, since it uploads fine for yakkety, we just need to try twice more ;D17:45
robruheh17:45
Saviqmterry, 58 is already queued for QA, don't wanna mess with that17:46
robruSaviq: oh that'll be tricky because if you try to publish a xenial+vivid, xenial is now an SRU (the silo logic is that the primary one goes to main archive and any +series go to overlay)17:49
robruSaviq: could manually copy to overlay I guess.17:49
Saviqrobru, does your new'n'shiny bileto jenkins replacement build straight away if it's never been built? waiting for it to realize it needs to build is a meh17:49
robruSaviq: best if you rebuild so that we have yakkety binaries that can be published17:49
Saviqrobru, hmm ok, it's probably not gonna be touched before tomorrow anyway17:50
robruSaviq: well right now it builds everything straight away, that "detect new commits" thing isn't implemented17:50
Saviqwfm ;D17:50
robruSaviq: but it'll have lots of speedups once I implement that again, doing things in parallel is absurdly faster at everything.17:50
Saviqcpt. Obvious17:51
Saviqmterry, FYI ↑ we're triplifying 58 after all, robru forgot to mention in his email that's roughly mandatory ;P17:51
mterryheh17:52
SaviqI think I rebuilt it today so we'll have the same issue with yakkety vs. overlay versions17:52
Saviqoh maybe not, it was last night17:52
robruSaviq: mterry: "so if you currently have any active dual silos, you need to edit your ticket, switch to yakkety+xenial+vivid and rebuild."17:53
Saviq"need to" sounds like "if you want to have it trio-ed"17:53
Saviqbut yeah I was probably just hoping ;)17:53
robruSaviq: I dunno, seems pretty clear to me. "if you have a dual silo, you need to edit it"17:53
Saviqpotehto, potahto17:54
Saviqgrr 50318:01
Saviqgaaarhghahghra18:17
Saviqrobru, we really need overlay copied to yakkety, we're missing dependencies in there18:18
SaviqIMO should've happened before trio silos :[18:20
seb128Saviq, the overlay was copied over this afternoon I think (from yakkety-changes list at least it looks like it was)18:20
* Saviq gets a yakkety chroot18:21
dobeytrainguards: can someone click retry for https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-056/+build/9772513 please?18:23
dobeyppc64el898 jobs (2 hours)18:24
dobeymeh. 8 builders and 98 jobs in queue18:24
=== chihchun_afk is now known as chihchun
seb128dobey, there is some infra issues since this afternoon, #is has been looking at it18:27
dobeyseb128: sure. i'm just lamenting for my poor silos :)18:28
dobeyand foundations people creating more work for me without warning18:29
oSoMoNrobru, re your last e-mail to bileto-announce, can you confirm that dual silos currently awaiting QA verification need to be rebuilt as trio silos?18:31
SaviqoSoMoN, yes18:32
oSoMoNthat’s what I feared18:33
SaviqoSoMoN, dual landings would mean SRU now18:33
oSoMoNubuntu-qa: https://trello.com/c/I5HJ3brK/3224-1387-ubuntu-landing-053-webbrowser-app-osomon-dbarth can be deleted as I’m rebuilding the silo as 3×landing18:38
robruSaviq: talk to sil2100, he flipped the switch on trio silos because he was ready to copy xenial overlay into yakkety. He mentioned having some conflicts but I'm not following him that closely, I dunno why he isn't finished yet.18:40
Saviqrobru, maybe it is, trying to find out what's going on now18:40
robruoSoMoN: yeah sorry, it's hard to coordinate this switch, lots of moving pieces18:40
oSoMoNrobru, I understand, no worries18:41
Saviqhmm no lxd images for yakkety yet ¿?18:56
Saviqohnoes overlayfs not supported on zfs 8-O18:57
Saviqrobru, sil2100, ok found the culprit - mir didn't get into yakkety https://launchpad.net/ubuntu/+source/mir19:11
Saviqand a lot of http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html is waiting for that19:11
robrujhodapp: one more should do it19:13
jhodapprobru, hehe ok :)19:14
jhodapprobru, you were faster to the draw than me, was about to contact you :)19:14
robrujhodapp: just happened to see the irc logs of the failure and checked the PPA contents19:16
jhodappawesome thanks19:16
Saviqmterry, can you do anything about mir and platform-api (at least) missing from the overlay → yakkety copy? or would you rather not touch it without sil2100?19:26
mterrySaviq, uh...  just needs a copy?19:27
dobeyno19:28
Saviqno?19:28
dobeythere have been manual uploads of mir to y19:28
dobeyso the conflicts need resolved19:28
Saviqoh fook and they were not put back into trunk?19:29
mterryplatform-api looks fine though, right?  It's already in sync between yakkety and overlay?19:29
dobeywell platform-api hasn't had any manual uploads to y19:30
dobeybut it might depend on mir or something?19:30
Saviqmterry, hmm maybe it's supposed to be that old19:30
dobeyugh19:31
Saviqright, with the exception there's a failed upload in the overlay19:31
dobeyit looks like lukascz did a no-change rebuild upload of platform-api to the overlay19:31
Saviqhttps://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6391641/+listing-archive-extra19:31
dobeyand it blew up19:31
Saviqthat FTBFS'd19:31
dobeywhy was that not done through a silo19:32
Saviqah I think it might've been the libhybris fiasco19:32
Saviqthat made it fail19:32
dobeybloody arm6419:32
Saviqthis is a mess19:32
dobeyindeed19:32
dobeydidn't we invent this whole ci train thing to avoid most of this mess?19:32
Saviqapparently not19:33
=== salem_ is now known as _salem
cyphermoxSaviq: dobey: seems to me like platform-api FTBFS there in tests because there's something different between the overlay and the real xenial archive.19:41
Saviqthere was also a libhybris release since then that fixed a similar issue, maybe we could just retry the mir build19:41
sil2100Saviq: I'm working on it19:48
sil2100mterry, Saviq: just give me a minute19:48
sil2100THe package copies are still in progress19:48
Saviqack19:48
sil2100The mir packages need a source copy so it takes a while, had a bunch of packages that needed uploading like that19:49
sil2100(and I need to preserve the mir changes)19:50
* sil2100 hopes xnox pushed all those changes upstream19:50
robrudobey: indeed, but if there's a manual upload to the overlay PPA that failed, that's not a train failure, that's a failure to use the train properly.19:51
robrusil2100: uh? Core devs uploading to devel never sync to trunk, that's the landers job to notice and sync trunk19:52
sil2100Well, that's not how the archive should work, for every project in Ubuntu we always first upstream the changes and then release downstream19:53
sil2100So I would expect the same policy for people using the train19:53
sil2100But if people are used to that, then good19:53
dobeyrobru: of course19:53
robrusil2100: i dunno where you're getting this idea from. I've butted heads with release team on several occasions, they upload direct to distro and don't care at all about upstream trunks.19:54
robrusil2100: this is why train has "... missing from changelog" check, so the lander knows to sync distro back to trunk19:54
sil2100robru: then those are bad practices, even doko pokes me everytime (or most of the times) he uploads a change to a train-managed project19:55
sil2100With all +1 maintenance it's always: "be sure the patch is submitted upstream"19:55
robrusil2100: good luck convincing them of that19:55
* sil2100 sighs19:55
dobeysil2100: how did you get doko to do that?19:55
sil2100dobey: he was doing it himself! I seem to be his point of contact for all train projects though - still, that's better than not caring at all ;)19:56
dobeysil2100: well, there's a difference to a patch (things in debian/patches/) and packaging changes19:56
dobeysil2100: "push packaging changes upstream" has never been a thing19:56
robrusil2100: i hope you haven't been clobbering yakkety uploads with old xenial ones, we need those diffs committed to trunk19:56
sil2100Right, but for instance the mir changes I'm seeing now are mods in the code contents, not packaging19:56
robrudobey: the difference now is that we have packaging in the "upstream"trunks when we are upstream19:57
robruMaybe that was a mistake, i dunno19:58
dobeysil2100: well i don't know what exactly changed in mir, but i've never been consulted about manual uploads to any train-managed projects i manage19:58
sil2100That's so sad19:58
dobeyrobru: well, sure, but there are other upstreams that have done that before us too.19:58
dobeybut yeah, it's a mess19:58
robrusil2100: i wanted to auto sync distro uploads back to trunks but slangasek veto'd because he didn't want silos that were more than "trunk + MPs"19:59
sil2100I remember being yelled at when I once released a package without mirroring the same change in the given project's branch20:00
sil2100During my +1 maintenance20:00
robrusil2100: new rule maybe? That's not consistent with my experience of distro uploads20:00
sil2100robru: looks like a very old rule, even the CodeReview page mentions this when sponsoring someone's work: "make sure to ask the patch author to submit the patch to Debian and/or Upstream. "20:02
robrusil2100: in fact it used to be part of the official train docs that you'd put a comment in the packaging that said "feel free to do manual distro uploads, upstream will notice and sync back to trunk for you"20:02
sil2100Well, anyway, I certainly would prefer this to work the 'proper' way, but yeah20:03
robrusil2100: yeah i used to get mad at uploaders but gave up years ago, now it's just a fact of life that distro sometimes has surprise non-train uploads in it and landers have to deal wth that20:04
dobeysil2100: well that comment in the codereview page is still about patches, not packaging. i think right now foundations is just trying to get yakkety rebuilt, and concentrating on fixing things in the archive, rather than pushing any patches necessary for fixing FTBFS upstream20:07
dobeysil2100: the more annoying thing to me is all the little things like 'enable arm64 builds'20:07
sil2100No-change rebuilds are understandable and not require any upstreaming, but code changes should always (IMO) be upstreamed20:09
sil2100Ok, but anyway, I think I copied (and rebuilt) what I could20:14
sil2100Now I need to go AFK to regular life business, I'll be around in an hour still if anything20:14
robruSaviq: any luck with mir? ^20:52
Saviqrobru, can you retry these builds https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-058/+sourcepub/6439825/+listing-archive-extra20:54
Saviqthe rest should resolve itself20:55
Saviqnot sure why these decided to be FTBFS and not dep waits20:56
robruSaviq: done, will try to keep an eye on it21:00
Saviqrobru, not sure why https://requests.ci-train.ubuntu.com/#/ticket/1426 was so unhappy (mismatches, ready to builds etc.), ran a diff only now21:01
Saviqah but it's also missing a few packages there, running a normal build then21:02
robruSaviq: version mismatch means the branch it pushed to lp doesn't match what's in the ppa, which could be a result of the versions isues you were having earlier.21:02
Saviqack, let's see what's gonna happen21:03
dobeybah i give up for today21:04
Saviqrobru, ah, too early - it's still building https://launchpad.net/ubuntu/+source/mir/0.22.1+16.04.20160516.2-0ubuntu221:15
robruSaviq: OIC.21:15
=== _salem is now known as salem_
robrugoddamn 503s, why, every time.21:59

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