/srv/irclogs.ubuntu.com/2016/01/14/#ubuntu-ci-eng.txt

dobeytrainguards: hi, can someone click retry on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-041/+build/8845368 please? thanks03:35
robrudobey: on it03:36
robrudobey: big train rollout today, let me know if you have any issues03:41
dobeyrobru: ok, thanks. yeah, i came back from dinner/etc, and saw the request page changed03:44
dobeywas slightly startling :)03:44
robrudobey: haha, auto reload feature waiting ;-)03:44
robruWorking03:45
Mirvrobru: \o/ for Lander Signoff / QA Signoff06:38
robruMirv: sorry that took so long ;-)06:45
Mirvno problem!06:46
=== chihchun_afk is now known as chihchun
morphissil2100, Mirv: morning! time for another silo-upload? :-)08:55
sil2100morphis: sure thing!08:55
morphissil2100: great08:55
jibeltvoss, ^ it worked, proposed-migration passed and QA status changed to ready, the card should be added to the qa board in 8 min09:52
rvrmardy: ping09:52
tvossjibel, ack09:53
morphissil2100: looks like I am running into corner cases everytime :-)10:00
morphissil2100: I am right that I can't add a vivid-only MP and a xenial-only MP to a dual-landing silo, right?10:00
sil2100morphis: hey, yeah... sadly that's not possible, dual landings are either manual uploads or one MP for both :)10:00
morphisperfect10:01
morphissil2100: then I will need three silos ...10:01
mardyrvr: pong10:09
rvrmardy: Silo 3410:30
rvrmardy: There are two programs now installing for Account Tester. What is SASL?10:31
mardyrvr: you can ignore that, it's not relevant for this silo10:32
mardyrvr: use the non SASL one10:32
rvrmardy: Ah, good. Then it's ok :)10:32
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== _salem is now known as salem_
=== alan_g is now known as alan_g|afk
dbarthhey trainguards, i need help to upload an oxide release into a silo13:21
dbarththis is https://requests.ci-train.ubuntu.com/#/ticket/871 (ie silo 048)13:21
=== chihchun is now known as chihchun_afk
Mirvdbarth: just give the info what needs to be copied14:15
Mirvnot mozilla-security ppa this time it seems14:15
morphisMirv, sil2100: time for another upload?14:18
Mirvmorphis: sure14:23
morphisMirv: great14:23
* sil2100 is AFKish for lunch now14:27
* davmor2 bets sil2100 isn't really away and it just pretending14:28
dobeysil2100: hi. the trust-store dual-landing branch in itself is't critical, but we have it along with some other critical changes to trust-store in the pay-service silo, so that we can land them all together rather than having complexity of landing multiple trust-store silos and then blocking the pay-service changes on those landing first.15:08
sil2100dobey: hm, ok - need to consult this with some other core-devs15:15
sil2100But I suppose we could conditionally land it + fill in a bug as we did for media-hub then15:16
dobeyok15:16
davmor2sil2100, jibel: both silo 40 and 46 I've marked as qa approved but I've not seen a notice here to tell charles and tvoss is the bot a bit broken now?15:31
charlesdavmor2, I appreciate the manual ack, then :-)15:32
sil2100davmor2: the bot is probably b0rken (e.g. not updated)15:32
davmor2sil2100: okay add it to the list so it isn't forgotten ;)15:33
sil2100davmor2: you'd have to poke robru about that, I don't know much abut the bot ;)15:33
sil2100robru: ^15:33
* sil2100 goes off to publish stuff now15:33
jibeldavmor2, the 'ready for qa' queue is empty then15:33
davmor2sil2100: I don't care who you blame, it's landing stuff so it's all your fault ;)15:34
jibelpopey, do you know what this request is https://requests.ci-train.ubuntu.com/#/ticket/342 ? seems old15:34
davmor2jibel: unless our bot needs updating to create new tickets of course :)15:35
popeyit is old.15:35
tvossdavmor2, my irc nick does not correspond to my launchpad nick15:35
popeyi will re-submit15:35
popey(a new one)15:35
davmor2tvoss: no there was no announcement I checked15:35
jibelsil2100, and what it https://requests.ci-train.ubuntu.com/#/ticket/115 ? it is also marked ready for qa15:36
jibelis*15:36
jibelpopey, okay I removed the status ready for qa15:36
davmor2tvoss: see the one above I expected something similar for qa approved which would ping you and sil2100 so you can land it15:37
sil2100jibel: well, robru mentioned something about old silos possibly having some erroneous statuses15:38
jibelsil2100, k, i'll remove the status ready for qa too15:39
sil2100Thanks!15:39
jibelYay, ready for QA = 'No Results'15:40
=== chihchun_afk is now known as chihchun
robruBlah, need to clear lander signoff when ppa gets rebuilt16:17
ChrisTownsendrobru: Hey, when I try setting "QA Signoff" to "N/A", it keeps resetting back to "Required".  Is this expected?16:34
robruChrisTownsend: yep, the train is enforcing qa states, anything that targets the phone requires qa16:35
ChrisTownsendrobru: Oh...16:35
robruChrisTownsend: i meant to take it a step further and only let qa people set that field, but didn't get around to it yet16:36
ChrisTownsendrobru: Alright.  I'll see what we need to do about QA then.16:37
ChrisTownsendrobru: Thanks16:37
robruChrisTownsend: you'll have to explain to a qa person why you think you don't need qa and get them to just approve it without reading anything16:37
robruChrisTownsend: yw16:37
ChrisTownsendrobru: Alright16:37
robru"Without testing anything" (on mobile)16:38
robruChrisTownsend: to clarify, it was always a requirement that anything targeting the phone requires qa, it's just that the train was on the honor system before and now it's more rigidly enforcing rules16:45
ChrisTownsendrobru: I understand.  It's just that Libertine is only on the PD image right now, so it's not on the proper phone image.16:46
robruChrisTownsend: pd?16:46
ChrisTownsendrobru: Pocket Desktop image.16:46
robruAh16:47
robruChrisTownsend: i guess just let qa know that it's not in the images then they can rubberstamp it16:47
ChrisTownsendrobru: Right, just trying to figure out who to let know so we can get this moving as it fixes a very critical issue holding up MWC stuff.16:48
robruChrisTownsend: probably jibel or davmor216:49
ChrisTownsendrobru: Ok, thanks16:51
robruYou're welcome16:51
rvrsil2100: meeting?17:02
=== timp is now known as t1mp
=== chihchun is now known as chihchun_afk
ChrisTownsendrobru: Britney sign off failed for https://requests.ci-train.ubuntu.com/#/ticket/875.  Is this something I need to be concerned about?17:58
robruChrisTownsend: the excuses page says you have an unsatisfiable depends, so yeah you're going to want to figure that out...17:59
robruChrisTownsend: i mean i suppose it's possible that it's a false positive but if you publish the silo in this state it will most likely just get stuck in proposed, so this is an early warning for you18:01
ChrisTownsendrobru: Hmm, ok, I'll look into it, but it's the unsatisfiable depends causing the failures, right?18:01
robruChrisTownsend: yup. Note that there's two in vivid and one in xenial18:02
ChrisTownsendrobru: Right, ok.  I think the Vivid one we've accounted for in the past.  Need to check out why the powerpc one is complaining.  Thanks!18:03
robruChrisTownsend: you're welcome18:03
charlesyay18:57
dobeyrobru: where to the autopkgtests for britney signoff run?19:36
robrudobey: in bileto19:36
robrudobey: no wait19:36
robrudobey: the *autopkgtest* are run in the standard autopkgtest hardware, same as proposed-migration19:36
robrudobey: bileto is just running britney which triggers them19:36
dobeyhmm19:37
dobeyok, i think i found the ones triggered by my silo on running now19:40
robrudobey: yeah the 'running' page is a bit of a maze19:41
dobeyhmm, would be nice if it was a bit more optimized20:00
dobeyhaving N things in a silo that all trigger different autopkgtest runs for the same package N times is a bit much.20:01
ChrisTownsendrobru: If I rebuild a silo, does the britney test automatically start again?20:12
robrudobey: raise that with pitti20:13
dobeyomg it takes 1.5hrs to run unity8 autopkgtests?!20:13
robruChrisTownsend: as long as the lander signoff is 'Approved' then britney will continuously run and continuously notice new packages & trigger new tests, yeah20:13
dobeyrobru: yeah, maybe i'll file a bug. the PPA is added in both, so the sames packages should be installed in both executions anyway.20:14
ChrisTownsendrobru: Hmm, ok.  I've been waiting for a bit and I don't see any evidence that is running again.  How long should I wait?20:14
robruChrisTownsend: it currently takes britney about 30m to run, and it's triggered in 5 minute intervals, so generally I'd expect it to update every 35 minutes for the time being.20:15
robruChrisTownsend: which request?20:16
ChrisTownsendrobru: Ok...now it says it's running.  I'm just not patient enough:)20:16
ChrisTownsendrobru: Thanks20:16
robruhehe20:17
dobeyhmm20:18
Saviqfginther, read my email further down20:24
fgintherSaviq, regarding them "showing up as you go deeper"?20:27
Saviqfginther, yeah20:27
Saviqfginther, so you can discover what jobs were triggered from a particular run, not even going up to project, finding the downstream ones and matching them20:28
fgintherSaviq, but can they be found programmatically through the API? That's the problem I see at the moment20:29
Saviqfginther, https://unity8-jenkins.ubuntu.com/job/lp-unity8-1-ci/73/api/json?depth=4&pretty=true20:29
Saviqfginther, look for "triggeredBuilds"20:30
Saviqor rather, look at them20:30
fgintheroh20:30
Saviqdepth could be an arg to voteOnMergeProposal20:30
fgintherI see it now, interesting20:32
fgintheryeah, that would be the way to go. Add the extra "depth=4" to the url and then parse through the triggeredBuilds20:33
fgintherof course the older version of the plugin doesn't output 'triggeredBuilds'20:34
fgintherbut that may be a don't care20:34
Saviqwe could leave the current support as is20:35
fgintherSaviq, yes, that shouldn't be too difficult to support both20:36
Saviqfginther, do you remember, when we were collecting test results from unity8's qmluitests, what was used to parse them? I have the xunit plugin here but have trouble selecting the right parser20:50
fgintherSaviq, they are parsed as JUnit results20:51
fginther"Publish JUnit test result report"20:52
dobeyrobru: ok, so i guess this new thing isn't handling the "always failed" situation?20:52
dobeyrobru: https://requests.ci-train.ubuntu.com/#/ticket/780 says "Failed" but there are no failures that weren't "always failed" in the excuses page20:53
* Saviq needs to touch them all, d'oh :/20:53
dobeyhmm, oh weird s390x thing on xenial20:53
robrudobey: yeah, failures include autopkgtest regressions but also anything 'Not considered' for any other reason20:54
Saviqfginther, do you know what "Test reports were found but none of them are new." is about?20:55
Saviq... is 53 sec old ORLY?20:55
dobeybah, bloody s390x20:56
fgintherSaviq, not sure. I thought it checked the timestamps of the files as they were parsed in case they were left in the workspace from an old build20:56
Saviqfginther, well, yeah, I touched them all... 53 sec old is "not new"?20:56
Saviqunless it compares with job start20:57
fginthercomparing with the job start would make sense20:57
Saviq\o/20:58
Saviqseems I just overcomplicated things20:59
Saviqwith the xUnit plugin20:59
fgintherSaviq, FWIW, pretty much everything we did could be consumed by the JUnit parser20:59
Saviqfginther, not by the xUnit parser for JUnit format, apparently ;)21:00
fginther:-)21:01
ChrisTownsendrobru: Sorry to keep bothering you, but another question.21:24
robruChrisTownsend: please, go ahead21:24
ChrisTownsendrobru: The britney test has failed again, but the log links still point to the old failures.  Does it take a bit for those logs to be updated?21:24
robruChrisTownsend: the logs are updated at the same time the status on the ticket is set. what ticket is it?21:25
robruChrisTownsend: you might be looking at a cached page, try reloading?21:25
ChrisTownsendrobru: https://requests.ci-train.ubuntu.com/#/ticket/87521:25
ChrisTownsendrobru: Ah, ok, it was cached.21:26
=== salem_ is now known as _salem
robruChrisTownsend: I'm seeing "python3-libertine-chroot/arm64 unsatisfiable Depends: proot" in vivid21:26
ChrisTownsendrobru: Yeah, that is expected.21:27
robruChrisTownsend: is that package in the overlay ppa but not in vivid proper or something?21:28
ChrisTownsendrobru: Um, let me check on that.21:28
robruChrisTownsend: the way it's currently set up is that as long as that failure stays there, the request will be marked as a failure, but if you go to publish it it'll probably be fine because vivid doesn't go through -proposed when publishing, it's just copied directly to the ppa.21:29
ChrisTownsendrobru: No, the arm64 proot is not in the PPA nor the main archive.21:29
dobeyrobru: so if i added another MP and built it in my silo, the britney stuff will pick it up ~35min after it's published in the PPA or what?21:30
robrudobey: yeah thereabouts.21:30
ChrisTownsendrobru: Ok, thanks again.21:31
robrudobey: there's timing issues, like I've seen it where britney will run *just* before your binaries get published, and it'll report everything as a failure "no binaries on any arch" or whatever, then it'll fix itself 35 min later.21:31
robruChrisTownsend: you're welcome21:31
dobeyrobru: yeah, cron jobs will always have weird race issues like that21:33
ChrisTownsendrobru: Now that I'm satisfied with this, do I leave QA Signoff as Required?21:33
dobeyugh, and like 2/3 of the x86 ppa builders are gone21:34
robruChrisTownsend: I guess so. technically you could set it to 'approved' but that's probably a bad habit to get in...21:34
ChrisTownsendrobru: Ready seems appropriate, but it keeps getting set back to Required.21:34
dobeyhmm, although lp builders says those are all virtual21:35
robruChrisTownsend: yeah it can't be ready unless britney approves and britney isn't going to approve it.21:35
ChrisTownsendrobru: Ah, ok.21:35
ChrisTownsendrobru: Thanks21:35
robruChrisTownsend: you're welcome21:35
dobeybut doesn't show any builders for non-virt x8621:35
ChrisTownsendubuntu-qa: Hi, anyone disagree about no QA needed for https://requests.ci-train.ubuntu.com/#/ticket/875 and just setting it to Approved?21:38
kgunnrobru: hey, is there a way to rebuild on train for one specific arch on one specific target archive ?22:45
kgunnlike in case the build failed and it might be a fluke22:45
robrukgunn: yes! all you have to do is ask me ;-)22:45
kgunnrobru: sweet! silo 36 amd64 for vivid22:45
robrukgunn: one sec22:47
robrukgunn: ok it's started apparently the x86 builders are stressed today so it might be slower than usual to build.22:51
kgunn np, thanks22:52
robruyou're welcome22:55

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