Friday, 2019-07-12

openstackgerritMerged zuul/zuul master: Switch to opendev release/docs jobs  https://review.opendev.org/67038800:22
*** armstrongs has quit IRC00:29
*** dmsimard4 is now known as dmsimard00:32
*** panda has quit IRC00:48
*** panda has joined #zuul00:50
openstackgerritJames E. Blair proposed zuul/nodepool master: Switch to zuul tenant jobs for docs/release  https://review.opendev.org/67042200:53
*** irclogbot_3 has joined #zuul00:56
*** irclogbot_3 has quit IRC01:00
*** irclogbot_0 has joined #zuul01:26
openstackgerritMerged zuul/nodepool master: Switch to zuul tenant jobs for docs/release  https://review.opendev.org/67042201:32
*** irclogbot_0 has quit IRC01:34
*** igordc has quit IRC01:35
*** swest has quit IRC01:36
*** swest has joined #zuul01:51
*** irclogbot_3 has joined #zuul02:26
*** irclogbot_3 has quit IRC02:30
*** altlogbot_1 has joined #zuul02:48
*** altlogbot_1 has quit IRC02:52
*** bhavikdbavishi has joined #zuul03:00
*** bhavikdbavishi has quit IRC03:02
*** michael-beaver has quit IRC03:08
*** rlandy has quit IRC03:16
*** irclogbot_2 has joined #zuul03:22
*** irclogbot_2 has quit IRC03:26
*** irclogbot_1 has joined #zuul03:52
*** irclogbot_1 has quit IRC03:56
*** swest has quit IRC04:26
openstackgerritMerged zuul/zuul-jobs master: Normalize test jobs yaml  https://review.opendev.org/67019804:31
*** bolg has joined #zuul04:39
openstackgerritMerged zuul/zuul-jobs master: Add add-authorized-keys test job  https://review.opendev.org/67019904:45
*** toabctl has quit IRC04:53
*** toabctl has joined #zuul04:55
*** irclogbot_2 has joined #zuul05:00
*** bhavikdbavishi has joined #zuul05:01
*** pcaruana has joined #zuul05:13
*** irclogbot_2 has quit IRC05:16
*** swest has joined #zuul05:24
*** altlogbot_0 has joined #zuul06:10
*** altlogbot_0 has quit IRC06:14
openstackgerritMerged zuul/zuul-jobs master: Advance ansible-lint cap to test with 4  https://review.opendev.org/66769506:31
*** irclogbot_0 has joined #zuul06:36
*** irclogbot_0 has quit IRC06:40
*** saneax has joined #zuul06:53
*** tosky has joined #zuul07:19
openstackgerritTobias Henkel proposed zuul/zuul master: Evaluate CODEOWNERS settings during canMerge check  https://review.opendev.org/64455707:21
*** badboy has joined #zuul07:35
badboyhi guys07:35
badboyI have a problem with web console07:41
badboyI have a problem with web console07:41
badboy2019-07-11 09:16:21.248160 | [ubuntu-bionic] Waiting on logger07:42
badboyThis is what I get07:42
badboyadditionally this is in the logs: http://paste.openstack.org/show/754332/07:42
*** hashar has joined #zuul07:49
*** altlogbot_3 has joined #zuul08:03
*** altlogbot_3 has quit IRC08:04
*** yolanda has quit IRC08:08
*** yolanda has joined #zuul08:09
openstackgerritJan Kubovy proposed zuul/zuul master: Overriding max. starting builds.  https://review.opendev.org/67046108:09
*** altlogbot_3 has joined #zuul08:12
*** altlogbot_3 has quit IRC08:16
*** altlogbot_1 has joined #zuul08:18
*** altlogbot_1 has quit IRC08:22
*** altlogbot_2 has joined #zuul08:24
*** altlogbot_2 has quit IRC08:29
openstackgerritTobias Henkel proposed zuul/zuul master: Evaluate CODEOWNERS settings during canMerge check  https://review.opendev.org/64455708:42
*** aluria has quit IRC08:48
*** irclogbot_3 has joined #zuul09:00
openstackgerritTobias Henkel proposed zuul/zuul master: Evaluate CODEOWNERS settings during canMerge check  https://review.opendev.org/64455709:03
*** aluria has joined #zuul09:03
*** irclogbot_3 has quit IRC09:04
*** gtema_ has joined #zuul10:03
*** hashar has quit IRC10:28
openstackgerritJan Kubovy proposed zuul/zuul master: Overriding max. starting builds.  https://review.opendev.org/67046110:31
*** yolanda has quit IRC10:31
*** yolanda has joined #zuul10:32
*** irclogbot_2 has joined #zuul10:32
openstackgerritTobias Henkel proposed zuul/zuul master: Annotate canMerge check with event id  https://review.opendev.org/67049410:35
*** irclogbot_2 has quit IRC10:38
*** irclogbot_2 has joined #zuul10:44
*** irclogbot_2 has quit IRC10:44
*** gtema_ has quit IRC10:47
*** aluria has quit IRC10:56
*** hashar has joined #zuul11:01
*** altlogbot_0 has joined #zuul11:04
*** altlogbot_0 has quit IRC11:08
*** aluria has joined #zuul11:11
*** altlogbot_3 has joined #zuul11:14
*** altlogbot_3 has quit IRC11:16
openstackgerritTobias Henkel proposed zuul/zuul master: Evaluate CODEOWNERS settings during canMerge check  https://review.opendev.org/64455711:26
openstackgerritJan Kubovy proposed zuul/zuul master: Overriding max. starting builds.  https://review.opendev.org/67046111:29
*** saneax has quit IRC11:52
pabelangerbadboy: check your firewall ports, tcp/19885 needs to be open. Also ensure zuul_console is running on the node11:59
openstackgerritMonty Taylor proposed zuul/zuul master: Use a requests session to simplify auth'd calls  https://review.opendev.org/67051112:16
openstackgerritMonty Taylor proposed zuul/zuul master: Use urllib.parse for manipulating client urls  https://review.opendev.org/67051212:16
mordredmhu: I was reviewing your stack and noticed two things ^^ feel free to ignore, use or squash as you see fit12:16
mhumordred, nice; I never think about sessions ...12:18
mordredmhu: I only due because of openstacksdk :)12:19
mhumordred, also I think that self.port is a remnant from a previous patchset, I'll have a look12:20
mhuI must have been distracted by all that red turning blue12:20
mordredmhu: I have had some similar experiences :)12:22
mordredmhu: if self.port is a leftover, then probably that entire patch can just be abandoned12:22
*** electrofelix has joined #zuul12:23
mhumordred, right, let me upload the fixed PS12:23
openstackgerritMatthieu Huin proposed zuul/zuul master: Zuul CLI: allow access via REST  https://review.opendev.org/63631512:27
openstackgerritMonty Taylor proposed zuul/zuul master: Use a requests session to simplify auth'd calls  https://review.opendev.org/67051112:33
mordredmhu: cool. +2 - and I abandoned the urlparse madness patch and rebased the other12:33
mhuthanks!12:33
openstackgerritSimon Westphahl proposed zuul/nodepool master: Don't pause static pool on single label quota  https://review.opendev.org/66737112:37
*** rlandy has joined #zuul12:37
openstackgerritMatthieu Huin proposed zuul/zuul master: Add Authorization Rules configuration  https://review.opendev.org/63985512:41
openstackgerritTobias Henkel proposed zuul/zuul master: Evaluate CODEOWNERS settings during canMerge check  https://review.opendev.org/64455712:42
openstackgerritMatthieu Huin proposed zuul/zuul master: Web: plug the authorization engine  https://review.opendev.org/64088412:45
openstackgerritMatthieu Huin proposed zuul/zuul master: Zuul Web: add /api/user/authorizations endpoint  https://review.opendev.org/64109912:45
openstackgerritMatthieu Huin proposed zuul/zuul master: authentication config: add optional token_expiry  https://review.opendev.org/64240812:45
openstackgerritMatthieu Huin proposed zuul/zuul master: Web: plug the authorization engine  https://review.opendev.org/64088412:54
*** tjgresha_nope has joined #zuul12:59
*** tjgresha has quit IRC13:02
*** sshnaidm|off has quit IRC13:30
*** sshnaidm has joined #zuul13:35
*** sshnaidm is now known as sshnaidm|off13:36
*** irclogbot_2 has joined #zuul13:38
*** irclogbot_2 has quit IRC13:38
Shrewsswest: i havent yet looked at the new patchset on 667371, but i14:01
Shrewsi'm much happier it doesnt touch the generic driver code14:02
*** bolg has quit IRC14:07
*** irclogbot_1 has joined #zuul14:11
*** chandankumar is now known as raukadah14:14
*** altlogbot_3 has joined #zuul14:15
SpamapS#1 most often thing I wish for now that cleanups and filtering on job config changes are implemented: I wish Zuul had a clear way to show why an event didn't result in any jobs running...14:19
SpamapStrying to discern it from the DEBUG logs is nearly impossible with lots of pipelines and trigger rules14:20
SpamapSSo it'd be nice if those things were more succinctly logged and possibly surfaced to a SQL table where one could inspect it more readily.14:20
corvusSpamapS: it's really hard to say why things don't happen (as in all of life, many more things don't happen than do happen)14:21
SpamapSRight, I'm just thinking that when an event gets to the end and nothing happens, I'd like the trail of failed matchers and/or other thing to be summarized.14:21
corvusSpamapS: so i think part of the challenge is that it is logged succinctly, it's just that it might be 200 things that are logged succinctly, and you only care about one14:22
SpamapSRight now the debug log is the only way.. and it's a *huge* mess even if you have the github event ID.. I'm sure gerrit provides a similar breadcrumb.14:22
*** jeliu_ has joined #zuul14:22
SpamapS2019-07-12 00:20:04,421 DEBUG zuul.Pipeline.GoodMoney.gate: [e: caf568d0-a43a-11e9-87ad-dae44ef23b0c] Event <GithubTriggerEvent 0x7fce18157e48 pull_request GoodMoney/funnel-cake refs/pull/31/head labeled github.com/GoodMoney/funnel-cake 31,5885856ca64b47163a04cee4dc37b7f6eff0711f delivery: caf568d0-a43a-11e9-87ad-dae44ef23b0c> for change <Change 0x7fce183dc978 GoodMoney/funnel-cake14:23
SpamapS31,5885856ca64b47163a04cee4dc37b7f6eff0711f> matched <GithubEventFilter types: pull_request ignore_deletes: True actions: labeled labels: shipit> in pipeline <DependentPipelineManager gate>14:23
corvusSpamapS: there's another way: https://zuul-ci.org/docs/zuul/user/config.html#attr-project.%3Cpipeline%3E.debug14:23
SpamapSThat's realy hard to compare to other log entries with similar info.14:23
SpamapSHm that debug thing may be useful, I had not seen it.14:24
corvusSpamapS: you're not going to want to set it permanently, but you can set it as part of an in-repo dynamic config change and get output for that specific change14:24
corvus(it's like dumping the debug logs into the zuul report; though they are formatted slightly nicer)14:25
SpamapSTo be more concrete: This time, I've been having a problem lately where I think users have scripted opening the pr and dropping the shipit label on things.. and I think the caching in github or zuul is making zuul think the label isn't there yet.14:27
SpamapSI don't really have 1 change to debug.. I have a rate of about 10%.14:28
SpamapSAnyway this may yet prove useful for that. I'll play. Thanks.14:28
corvusSpamapS: curious.  i wouldn't expect that to be a problem.  let me know what you find.14:29
pabelangerdelayed events?14:29
pabelangerI've seen a label show up late before14:29
pabelangeralso, see issue with label not getting seen, but haven't really debugged why yet14:30
pabelangerbeen holding off on that until running tobiash latest github updates14:30
SpamapScorvus:I've had that exact problem in the past. I thought we solved it with etags or something.14:31
SpamapSgithub's API is kind of async sometimes. The same happens with statuses... if you set a status and read it back it will often be the old value.14:31
SpamapSwhich is one reason I can't use the "require gate status to be reported success" trick to ensure only Zuul merges PRs.14:32
corvusSpamapS: we could have zuul delay after setting statuses until it reads back correctly14:34
SpamapScorvus:I believe we just need Zuul to set the appropriate E-Tag on the request which will force a cache invalidation.14:34
corvus(there's actually some code in gerrit for something similar -- gerrit itself is sync, but there's some code to make sure that git replicas are updated)14:34
tobiashcorvus: actually this should work, as we also can react on the status event (which should then guarantee that the status is set)14:35
SpamapSThe promote pipeline took pressure off of me to solve this..14:35
SpamapSif the users self-merge, they don't get artifacts built, and promote fails.14:35
SpamapSso Zuul has trained them not to click the merge button14:36
* SpamapS afk14:36
openstackgerritJeff Liu proposed zuul/zuul-operator master: Add Kubernetes Operator Functional Test Job  https://review.opendev.org/66802914:38
openstackgerritJeff Liu proposed zuul/zuul-operator master: [WIP] Verify Operator Pod Running  https://review.opendev.org/67039514:38
*** hashar has quit IRC14:51
corvuspabelanger, mordred, tobiash, SpamapS, clarkb: ^ I think 668029 is ready for review14:59
openstackgerritJeff Liu proposed zuul/zuul-operator master: Remove Operator SDK dependency in Zuul Job  https://review.opendev.org/67058415:17
*** mattw4 has joined #zuul15:37
openstackgerritJeff Liu proposed zuul/zuul-operator master: Remove Operator SDK dependency in Zuul Job  https://review.opendev.org/67058415:58
*** armstrongs has joined #zuul16:00
armstrongshey small query if anyone can help. I am looking at using a timer pipeline.trigger.timer, so if this is used will it just build the latest ref from the projects master branch?16:02
fungiarmstrongs: the short answer is yes (or you can specify the branch you want it to use)16:03
armstrongsis there an example config of where it is used anywhere?16:03
fungialready pulling one up to link16:03
armstrongsthanks you16:03
fungiarmstrongs: here's an example of using one called "periodic-stable" in a project-template: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/project-templates.yaml#L1125-L114616:06
fungiyou can see there how the jobs in the periodic-stable pipeline have branches lists16:06
fungiif you don't supply a branches list, the default is just master16:06
armstrongsthank you will give that a go16:07
armstrongs:)16:07
fungiarmstrongs: for reference, we define that pipeline here: https://opendev.org/openstack/project-config/src/branch/master/zuul.d/pipelines.yaml#L236-L25216:07
fungibut there's really not much to it16:08
*** jangutter has quit IRC16:16
*** jangutter has joined #zuul16:16
SpamapSmmmm operator16:19
* SpamapS would love to throw away his janky spruce scripts16:19
fungibut they really spruce up the place16:22
*** aluria has quit IRC16:26
*** armstrongs has quit IRC16:31
SpamapSyou'd think16:31
corvusjeliu_: now that the pod list command is in place, it does look like the operator is crashing: http://logs.openstack.org/29/668029/19/check/zuul-operator-functional-k8s/cedd11a/ara-report/result/98cfffd4-34d2-40ac-be8b-208bb3129e9f/  that's fine, we don't care that much at this point, but it does mean that once you get the job set up to verify that the operator is running, that is going to (correctly) fail.16:33
corvusjeliu_: regarding the other change, it looks like the plain docker build worked: https://review.opendev.org/670584  \o/16:33
mordredpabelanger, clarkb: https://review.opendev.org/#/c/668029 have 2x+2 but I left it open since you'd reveiwed before in case you want to look again16:34
*** jangutter has quit IRC17:16
pabelangermordred: corvus: +2, too17:20
pabelangerleft +A to clarkb if wanted otherwise good to merge17:20
clarkbI'll look at it now that fedora 28 problems are debugged17:23
clarkbapproved. There was one minor task/play naming thing that I noted but can be cleaned up in a follow on17:25
openstackgerritMerged zuul/zuul-operator master: Add Kubernetes Operator Functional Test Job  https://review.opendev.org/66802917:37
openstackgerritMerged zuul/zuul-operator master: Remove Operator SDK dependency in Zuul Job  https://review.opendev.org/67058417:37
corvusjeliu_: ^ yay!17:37
* mordred does a dane17:38
mordreddane17:38
mordredGAH17:38
mordreddance17:38
mordredapparently a danish dance17:38
* mordred crawls back under his rock17:38
*** igordc has joined #zuul17:43
openstackgerritJames E. Blair proposed zuul/zuul master: Build layout of non-live items with config updates  https://review.opendev.org/67033517:53
clarkbthe zuul zuul tenant has made me wonder if it would be a worthwhile thing to have a status dashboard that allows you to opt into seeing specified tenants?18:08
clarkbso I could see the zuul and openstack tenants in the same dashboard and someone els could have zuul and opendev or whatever18:08
clarkbthough I think I sort of assumed I could see things mixed together but the pipeline defs may not overlap so that won't work generally18:09
corvustenants are completely isolated; so a combined dashboard would have to query multiple endpoints, and yeah, you'd have a lot of duplicate pipelines18:10
clarkbya I'll have to think about this a bit more to see if there is a good way to do it in my head18:11
corvusclarkb: honestly, even a native implementation may not be much more sophisticated than an iframe, which you could try out now :)18:11
clarkbya the initial thing I had thought of was to just stick everything from zuul check and openstack check into one logical pipeline in the dashboard called check18:13
clarkb(and so on with gate promote post release etc)18:13
mordredfor the naive case that's actuall probably "good enough" for visualizing the aggregate system18:14
corvusthe order would convey something which wasn't right18:14
mordredyeah - there's definitely issues and incorrectnesses18:14
mordredsort of depends on what questions you're wanting answered by such a view18:14
clarkbfor me its mostly so I don't have to have multiple status windows open to track progress of chagnes I have in flight udner different tenants18:15
openstackgerritJames E. Blair proposed zuul/nodepool master: Add functional jobs to gate  https://review.opendev.org/67061218:17
corvusclarkb: ^ i think the time has come :)18:18
mordred++18:18
clarkbapproved18:18
*** electrofelix has quit IRC18:18
corvusi'm now very motivated to write the "gate pipeline supercedes check" patch.  but it's #3 on the list.18:19
*** jeliu_ has quit IRC18:42
*** irclogbot_1 has quit IRC18:49
*** edmondsw_ has quit IRC18:49
*** irclogbot_0 has joined #zuul18:53
*** michael-beaver has joined #zuul18:56
Shrewscorvus: so what purpose does check pipeline serve in this scenario w/o clean-check? seems like a waste of test resources. for nodepool, we could move the last remaining non-voting job to gate and not need check at all19:00
fungithe check pipeline is a way to automatically run jobs on any new proposed change, to aid reviewers in determining whether it's ready19:06
fungibut you're right, you *could* go it with no check pipeline, and just rely on the gate to bounce back changes when they're approved19:07
Shrewsoh, i wasnt thinking about the approval requirement.19:08
Shrewsmy "duh" moment for the day19:08
* mordred hands Shrews a beer, suggests maybe it's time for the weekend19:19
Shrewstrue19:20
Shrewsmordred: i'm blaming the pain meds i'm still on, which is also the reason i must decline your beer19:21
corvusi think there's 2 common scenarios: 1) upload a change, people get to it after a day+ and merge it.  check shows us it's ready.  2) upload a change which is simple and obviously works and we should just merge asap.  forget check, go straight to gate, gate tells us if we're wrong.19:21
corvusthe change i'd like to write to zuul would let zuul know that if case #2 happens, it can abort the jobs running in check19:21
fungiyeah, i do think that's a nice optimization to free up resources19:22
Shrewscorvus: sounds like a sensible change19:22
fungigranted, it assumes you run at least all the check jobs in the gate pipeline19:22
fungibut we strongly recommend that anyway19:22
corvuscase 2 works for us, because we're a small group of people who never make mistakes.... or, maybe, we're just small enough and judicious enough with +W that we won't end up backing up gate with a bunch of failing changes.19:22
fungior we're small enough to not be judgemental when someone approves an obviously non-test-passing change19:23
corvusbut in openstack's case, no matter how many times we said "be better programmers", people still wanted to throw complex changes that had no chance of passing tests straight at the gate.  that's why clean-check was invented -- to keep those changes from backing up openstack's huge gate pipeline19:23
corvusprobably, if you get down to basics, if the gate pipeline spends any significant amount of time empty, clean-check isn't necessary.  if it spends most of its time with a multi-hour backlog, it probably is.19:24
fungi"keeping things out of the gate until they work"19:25
corvus                                         ^ probably19:25
fungiheh, right!19:26
fungiand yeah, the deeper your gate pipeline is on average, the more costly gate resets become19:26
clarkbanother reason for clean check in poenstack is there was a lot of forcing code that had races in it through by enqueuing to the gate over and over19:26
clarkbit is very rare for peopel to actualyl debug those problems it seems :/19:27
clarkbzuul seems to do a better job19:27
fungiright, that at least forced changes to be good enough to be able to pass all jobs twice in a row19:27
funginot to pick on openstack... it still has better quality control than 99% of the projects its scale19:29
fungibut complexity and bugs go hand in hand, and in a large interrelated codebase you have to take defensive approaches to nondeterministic behaviors19:30
clarkbya19:32
*** bhavikdbavishi has quit IRC19:48
corvusi have a weird question20:02
corvuscurrently if you have change B depending on change A, and change A breaks zuul's config, when they show up in the check pipeline, change B will be reported with a configuration error.  that's a side effect of the way we build configuration for dependent changes in check.  (weirdly, B would not report an error if it were somehow able to run in gate, but of course it can't.)20:06
corvusof course, A does in all cases have its error reported.20:06
corvusi may have an opportunity to change that, so that we don't see the config error for A on B.  would that be desirable?  what should happen in its place?  attempt to use the broken config anyway (as if we had just restarted zuul with change A merged and then enqueued B)?  or should we say "this change depends on a change with a broken config" and not run any jobs?20:09
fungii desire that, yes20:09
fungii like the latter20:09
fungidon't run jobs for the depending change because the change it depends on is untestable20:09
fungibut limit the configuration error to the change which actually is attempting to add that error20:10
corvusokay, one vote for "don't run the jobs, but report an abbreviated error message"20:10
fungithe alternative of running the jobs with the broken change applied seems inefficient, since the depending change is most likely going to need to be rebased anyway once the dependency is fixed20:11
clarkbya that makes the most sense to me20:12
clarkbfungi: and you could get misleading results that create confusion20:12
corvus(there's a lot of code to do almost exactly that, but i suspect that some of it may be dormant due to some optimizations which i'm semi-undoing; we used to build a config for every change, and that was very inefficient because large stacks would have tons of merge jobs for non-live items; so then we stopped merging non-live items at all, but that means we can't see where in a stack the config broke; the20:13
corvuschange i'm working on would have us merge non-live items with config updates, so we would still usually not merge them, but sometimes we would if we need their data)20:13
corvusit turns out that looking at a change ahead in the pipeline to find out if the config for a job changed is basically the same as looking to see where the config broke.20:14
fungistrangely, that make sense20:28
openstackgerritJames E. Blair proposed zuul/zuul master: Build layout of non-live items with config updates  https://review.opendev.org/67033520:41
corvusoh, let me add more to the commit message about that20:41
openstackgerritJames E. Blair proposed zuul/zuul master: Build layout of non-live items with config updates  https://review.opendev.org/67033520:45
corvusokay.  that's a long change with a long commit message.  :)20:45
corvusnext up is to try to repro and fix the error we saw yesterday -- where an existing broken config in the check pipeline caused us not to be able to fix it.20:47
corvuswe have tests that check that a broken config can be fixed, but in those tests, i don't think the "check" pipeline is the thing that's broken20:49
fungiseems like a bit of a catch-2220:50
corvusthat's more or less how zuul behaved at the time :)20:50
*** pcaruana has quit IRC20:59
openstackgerritJames E. Blair proposed zuul/zuul master: Handle existing broken config in job updates  https://review.opendev.org/67066621:17
corvusAJaeger, clarkb, fungi: ^ that should handle the exciting catch-22 error we hit yesterday21:18
fungiawesome, looking21:21
mordredcorvus: nice21:26
corvuszuul has 32417 lines of test source-code and 33470 lines of application source-code (or about 97% as much test code as app)21:28
corvus(excluding zuul/ansible, which is another 26k very duplicative lines)21:29
corvussome of that should be included, but i'm not curious enough to figure out a fair way to do that21:30
clarkbcorvus: left a comment on 67066621:32
openstackgerritJames E. Blair proposed zuul/zuul master: Handle existing broken config in job updates  https://review.opendev.org/67066621:37
corvusclarkb: good point; i think that'll take care of it ^21:37
clarkbya that should do it21:38
clarkbcorvus: reading the commit message of the non live change could we cache the merge results for each item (maybe we already do?) then we only do it the once (until some ttl times out) for all instances of that item whether live or non live?21:45
corvusclarkb: yeah; i think we could just grab the layout and files objects from an existing copy of the item in the pipeline.  that would help with the pathological case of A, AB, ABC, ... . there would be a behavior difference if, for some reason, A stuck around in the pipeline for a long time, AB showed up, and then was rechecked.  that means we would end up reusing the result from the A item rather than (as21:50
corvuswould happen today) we reperform the merge for AB.  i'm not certain whether we care or not.21:50
corvusit's not going to be a trivial optimization; if we do it, i think it should be a followup (since i don't think the current slight sub-optimization is critical)21:52
corvus(incidentally, we do something kinda similar in the provides/requires thing -- where we look for a live dependent change to find its artifact return data -- so the 'look for a change' part of that won't be unique)21:53
*** ianychoi has quit IRC21:54
*** rlandy has quit IRC21:54
clarkbcorvus: left a comment on that change related to something else21:57
clarkbI haven't fully gotten through it yet but other than that I think it is looking good21:58
corvusclarkb: replied (yeah, i waffled on dropping that but couldn't quite bring myself to do so, mostly so we keep all of those requirements in one place)22:11
openstackgerritJames E. Blair proposed zuul/zuul master: Add "supercedes" pipeline option  https://review.opendev.org/67067022:13
SpamapScorvus: get out of my head.. I was just thinking earlier today I wanted that supercedes option!22:15
corvusSpamapS: you should really clean up in here ;)22:18
clarkbcorvus: ok properly through it now and noticed one other thing (comment inline)22:23
openstackgerritJames E. Blair proposed zuul/zuul master: Add "supercedes" pipeline option  https://review.opendev.org/67067022:24
corvusthat adds more config validation22:24
*** demeg0 has joined #zuul22:30
corvusclarkb: replied with short essay :)22:38
*** armstrongs has joined #zuul22:42
clarkbcorvus: that makes sense (re a third change and diffing against that)22:50
*** michael-beaver has quit IRC22:57
*** mattw4 has quit IRC23:01
*** armstrongs has quit IRC23:15
*** tosky has quit IRC23:20

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