Tuesday, 2017-05-30

*** jkilpatr has joined #zuul00:08
*** jkilpatr has quit IRC00:45
*** jkilpatr has joined #zuul00:57
tristanCmordred: pabelanger: re-using min-ready and max-concurrency, the static node driver may be able to provide concurrent job execution on the same system04:00
tristanCmordred: about the oci driver, it is indeed re-using host fs so that containers are easy to manage and as light as possible04:02
tristanCand it seems like simple label such as 'oci-centos-7' should be enough, and easier to implement compared to 'oci:centos-7'04:05
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Implement a static driver for Nodepool  https://review.openstack.org/46862404:06
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Extend Nodepool configuration syntax to support multiple drivers  https://review.openstack.org/46875104:06
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Collect request handling implementation in an OpenStack driver  https://review.openstack.org/46875004:06
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Abstract Nodepool provider management code  https://review.openstack.org/46874904:06
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Add support for custom ssh port  https://review.openstack.org/46875204:07
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Implement an OpenContainer driver  https://review.openstack.org/46875304:07
*** hashar has joined #zuul07:02
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Implement a static driver for Nodepool  https://review.openstack.org/46862407:20
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Extend Nodepool configuration syntax to support multiple drivers  https://review.openstack.org/46875107:20
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Collect request handling implementation in an OpenStack driver  https://review.openstack.org/46875007:20
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Abstract Nodepool provider management code  https://review.openstack.org/46874907:20
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Add support for custom ssh port  https://review.openstack.org/46875207:20
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Implement an OpenContainer driver  https://review.openstack.org/46875307:20
*** openstackgerrit has quit IRC08:18
*** fbouliane has quit IRC09:27
*** Shrews has quit IRC09:27
*** SpamapS has quit IRC09:27
*** rcarrillocruz has quit IRC09:27
*** jlk has quit IRC09:27
*** rbergeron has quit IRC09:27
*** fbouliane has joined #zuul09:49
*** Shrews has joined #zuul09:49
*** SpamapS has joined #zuul09:49
mordredtristanC: nod10:06
*** rcarrillocruz has joined #zuul10:13
*** jlk has joined #zuul10:13
*** rbergeron has joined #zuul10:13
*** jkilpatr has quit IRC10:40
*** jkilpatr has joined #zuul10:56
*** dkranz has joined #zuul13:21
tobiashhi13:23
tobiashis it possible to specify the location of the playbooks in the according zuul.yaml?13:23
tobiash(or .zuul.yaml)13:23
tobiashmaybe some projects don't want to have a folder playbooks in the repo root but maybe in ci/playbooks13:24
mordredtobiash: yes, I believe so - although scanning the code it's not immediately clear how we exposed that13:27
mordredtobiash: nope. I'm lying - playbooks seems to be hardcoded right now13:29
mordredtobiash: I think it is the intent that it be configurable though13:29
tobiashmordred: ah, just thought I'm blind ;)13:29
mordred:)13:29
tobiashbut good to know that that's something that will be configurable at some point in time13:31
tobiashmaybe I have time for this topic after my vacation in a few weeks13:31
*** morgan has quit IRC13:37
tobiashyay, another decoding issue: http://paste.openstack.org/show/610971/13:45
pabelangertobiash: Yes, I've been meaning to submit a patch. I use the test folder currently in ansible roles for testing, would love to update .zuul.layout to account for that13:53
tobiashpabelanger: ok, cool13:57
* mordred has a feeling humans are going to have strong opinions as to where they keep their playbooks14:17
pabelangerhttps://review.openstack.org/#/c/468942/ easy fix is people would like to review nodepool. Currently console-log is broken syntax for nodepool14:34
tobiashhow does console streaming (and saving to the console.log) work with multi-node tests?15:54
clarkbin a v2.5 world just the primary node gets console streamed. In v3 I believe each host gets its own console stream15:55
tobiashjust tried this out and it generated one console.log with the console content of one node15:55
tobiash(in zuulv3)15:55
clarkbor rather its all run through central ansible (the executor) so all the console streaming from each host ends up back at the executor15:56
clarkbso its aggregated rather than single point15:56
tobiashI'll check how your base jobs work15:56
*** hashar is now known as hasharAway15:57
*** morgan has joined #zuul15:58
tobiashso I'm doing the same like the first two steps here:15:58
tobiashhttps://review.openstack.org/gitweb?p=openstack-infra/openstack-zuul-roles.git;a=blob;f=roles/prepare-workspace/tasks/main.yaml;h=4d42b2dff3ab9e72e3618271615177437cd32aa8;hb=HEAD15:58
jlko/16:00
tobiashah, I think I know my error16:00
tobiashhttp://paste.openstack.org/show/610995/16:00
tobiashlog collection only leaves one console.log alive...16:00
*** openstackgerrit has joined #zuul16:10
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Add console-log to config-validate  https://review.openstack.org/46894216:10
jlkSpamapS: I added a number of tasks to this story, did I do it right? https://storyboard.openstack.org/?#!/story/200077416:18
SpamapSjlk: aye, looks good16:30
SpamapSjlk: thanks!16:31
tobiashdo we still have races in zuul tests?16:37
tobiashjust had a failure of tests.unit.test_zuultrigger.TestZuulTriggerParentChangeEnqueued.test_zuul_trigger_parent_change_enqueued16:37
tobiash(locally)16:38
jlkIf we do, they're somewhat deterministic races16:38
tobiashrerun of the test was successful16:38
SpamapSThere are a few that are performance related.16:42
SpamapSlike, internal stuff times out.16:42
tobiashrerun the whole suite was green the second time16:43
SpamapSI have seen a couple flakes in the gate/check tests too though, so it's likely there are a few races hiding in the weeds.16:43
SpamapSnothing that is well known and common16:43
SpamapSwe should maybe dig around in kibana a little to see if there are any obvious patterns16:44
SpamapSbut I think the rate still low, might not have enough data and _a lot_ has changed recently16:44
tobiashprobably16:44
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Decode the console log stream  https://review.openstack.org/46918116:49
tobiashAnother py3 decoding fix ^^^16:49
pabelangertobiash: your running ansible under python35?16:52
tobiashpabelanger: yes16:57
tobiash:)16:57
pabelangertobiash: nice16:57
tobiashmy zuulv3 test setup is py3 only currently ;)16:57
pabelangerYa, I'd love for us to do that too16:58
pabelangersoon(tm)16:58
tobiashand it runs some simple jobs already...16:58
tobiashbut it crashes every now and then with some py3 encoding issue16:58
tobiash(but all in zuul so far)16:59
tobiashand with fixes in review16:59
tobiashor merged16:59
*** bhavik has joined #zuul17:11
*** harlowja has joined #zuul17:14
SpamapSpabelanger: weren't there some tests in the review queue for that particular code path?17:16
SpamapShttp://zuulv3-dev.openstack.org/logs/1ed5cccc9371461c963e7808004e6370/tox/py35-1.log.txt17:17
SpamapSCould not determine repository location of /home/zuul/src/git.openstack.org/openstack-infra/zuul17:17
tobiashSpamapS: is that a deterministic failure?17:21
tobiashdidn't see this error yet17:22
pabelangerSpamapS: I'd have to check again, but don't think so17:23
SpamapSpabelanger: ^ that tox fail seems to happen periodically. Any idea?17:25
tobiashhas the url_pattern been removed from the zuul config?17:30
pabelangerchecking zuulv3-dev to see17:30
tobiashdon't find any real occurrence in the code17:31
tobiashbut it is still in some fixtures17:31
tobiashon post playbook failure the job defined failure url is not used for gerrit reporting17:34
pabelangernot sure, don't see anything obvious17:35
pabelangerdoes autohold work for zuulv3?17:35
pabelangerI know we changed it17:35
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Use util functions to make lists of things  https://review.openstack.org/46919217:39
jlkSpamapS: do commit hints referring to story/tasks on storyboard cause some automatic task manipulation, or do I have to follow that up manually to twiddle the status bit?17:40
jlkoh cool, automatically happens.17:42
SpamapSjlk: if you have a Story: and Task: yes, it's fully automated.17:42
jlk:thumbsup:17:42
SpamapSStory: will just put it in the info log of the story, but having both fully automates, which is nice.17:42
SpamapSjlk: also note that there's a "boardtty" for when you get tired of storyboard's somewhat sluggish JS UI ;)17:43
SpamapSthough boardtty needs some work.. the "assign to" dropdown is unusable.17:43
SpamapSsorry, 'boartty'17:43
SpamapSI started working on that but got lost in some needed model changes :-P17:44
jlkBoarttyMcBoarttyface.17:44
SpamapSYeah we never should have had that poll... ;)17:45
jeblairtobiash: in v3, we shouldn't copy console.log anymore; instead the console logs for all of the nodes (in a multinode job) get streamed and interleaved into ansible_log.txt on the executor, and that should generally be considered "the log" for a build.  there is a bug with that right now that mordred is looking into -- we only get output from the first command task.18:05
tobiashjeblair: ok, good to know18:05
tobiashthanks18:05
jeblairtobiash: seccuss-url is a job attribute in v3, so right now, the strategy for log links is to set that (in the base job) to the same location where ansible would put the logs (probably also in the base job).  unfortunately that means duplicating the value in two different places/systems (zuul config + ansible).18:07
jeblairtobiash: i'd like to move to a system where we have the executor read data back from ansible runs (maybe it just loads a json file from a known location) so that it can learn the log url from the job content itself.  then we can remove that configuration from success-url.  it just reports whatever ansible said it should for the logs.18:08
tobiashjeblair: I noticed that the failure-url is not taken into account if the job result is POST_FAILURE18:08
jeblairtobiash: that might be an oversight18:08
tobiashjeblair: so one of the post playbooks (probably the last one) should push the logs somewhere and leave a json file behind with the url?18:12
jeblairtobiash: yeah, that's what i'm thinking.  we can use the mechanism to provide any data back to zuul in the future.  we can start with log links (and maybe result comments), but it could eventually also be the way we get jobs to leave line comments as well.18:14
tobiashthat would be cool :)18:14
*** bhavik has quit IRC18:15
tobiashjeblair: currently in the process of enhancing the test_playbook test with a check for success and failure urls18:18
tobiashhttp://paste.openstack.org/show/611005/18:18
tobiashthat's the current behavior18:19
tobiashjeblair: does it make sense to fix that or better wait for the new solution?18:20
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Add boot-from-volume support for nodes  https://review.openstack.org/46428318:23
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: WIP: Add web-based console log streaming  https://review.openstack.org/46335318:28
Shrewsjeblair: ^^^ using a thread now, as you asked. Had to do some finagling of the event loop to get that to work18:29
Shrewsnow gotta figure out how to test it  :/18:38
Shrewsbut first... tea18:38
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Fix and test report urls for post fail and timeout  https://review.openstack.org/46921418:44
*** bhavik has joined #zuul18:47
jeblairtobiash: it probably makes sense to fix now; any unknown non-success result should probably use the failure pattern18:59
jeblairShrews: w00t!  hopefully with it running in a thread it should be easier to get it up and running in tests like we do with most of the other daemons (merger, etc)18:59
tobiashjeblair: ok, so just replace with else here https://review.openstack.org/#/c/469214/1/zuul/model.py19:00
jeblairtobiash: yeah, i think so19:01
tobiashwill update the patch in a minute19:01
*** bhavik has quit IRC19:04
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Fix and test report urls for unknown failures  https://review.openstack.org/46921419:05
jlkjeblair: we talked last week about oddness with requiring change like things (votes, etc..) on push like events. I've tested, and confirmed that it causes a traceback in the github code. I'm looking at gerrit now, and just confirmed that gerrit driver will traceback too on checking for say 'current_patchset' on a ref-updated event.19:08
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Add config option for executor process user  https://review.openstack.org/46067119:08
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Allow for using build UUID as temp job dir name  https://review.openstack.org/45668519:08
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Add a finger protocol log streamer  https://review.openstack.org/45672119:08
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Allow for specifying root job directory  https://review.openstack.org/45669119:08
*** ianw has joined #zuul19:20
jlkjeblair: do you think it makes sense, in the context of a push / ref-update event, that current_patchset should always equate to true, or should it do something to look at the ref that is updated, and see if the sha of the update is still the latest sha on the ref?19:23
jeblairjlk: maybe always be true?19:45
jlkI'm drafting a mail for the list, to get some discussion on it, or at least dump my brain out somewhere other than IRC :D19:46
jeblairjlk: (it doesn't really make sense; i almost think that always returning true or always returning false are almost equally valid)19:46
rbergeronjlk: i dunno if you saw this or if it's old news, but github is moving from rest api to graphsomethingsomething20:16
rbergeronhttps://developer.github.com/v4/20:16
rbergeron"Github is moving from a REST API to one based on GraphQL. Single request => several actions."20:16
rbergerondunno if that... affects anything or is useful in the context of the mail you just sent, but: i merely bringeth possibly useful information,20:16
mordredyah. just in time for us to have finished the rest port :)20:16
rbergeronand hope that others can make use of things20:16
rbergeronand now i really go to do the errands20:17
jeblairjlk: question on https://review.openstack.org/46342020:22
mordredjeblair: oh - so we want an "app" not an "integratoin" now?20:23
jeblairmordred: apparently?  it looks like they've been updating their docs (which mostly say "app" in the title and "integration" buried deep in the text)20:24
mordredglorious20:24
mordredto be fair - "app" makes a bit more sense than "integration"20:24
jeblairmordred: you can buy apps for your projects too.20:25
mordredjeblair: what about for my tenants?20:25
jeblairmordred: i'm imagining in-app purchases.  you could sell positive CI results.20:25
jeblairalso, if we could somehow do gold farming that would be just great.20:26
SpamapSso, I finally got time to show Zuul to the Kubernetes sig-testing group20:40
SpamapSIt went well, lots of good questions from people who have basically been going through some of the same growing pains as OpenSack.20:41
*** jkilpatr has quit IRC20:44
jeblairSpamapS: oh good!20:47
pabelangerSpamapS: great talk, was able to watch20:47
dmsimardpabelanger: I'm seeing that happen pretty often recently, does that ring you a bell ?20:51
dmsimardOpenStackCloudException: Tried to delete floating ip 38.145.33.45 associated with server 97f2998d-5103-4ee0-b114-fdc2563316fd but there was an error deleting it. Not deleting server20:51
dmsimardOn the cloud, the VM no longer has a floating IP attached20:52
dmsimardand in the meantime the floating IP has been re-associated with another server20:52
pabelangerdmsimard: might be work posting the debug.log to pastebin and have mordred peak too20:52
pabelangerI'd have to check and see if that happens for tripleo-test-cloud-rh120:53
dmsimardthis is against rdo cloud20:53
pabelangerright, but nodepool.o.o might see it with tripleo since it also is using FIP20:54
dmsimardah20:54
dmsimardpabelanger: but.. basically: http://paste.openstack.org/raw/611023/20:54
mordredSpamapS: yay!20:55
pabelangerdmsimard: that debug log will have more logging for shade20:55
pabelangerwhich we'd need to see20:55
pabelangerdmsimard: is this nodepool?20:55
pabelangeror manually running commands20:56
mordreddmsimard, pabelanger: hrm. why did shade think that server had 38.145.33.45 associated with it in the first place20:56
dmsimardpabelanger: nodepool is leaving VMs running due to that floating IP error so I look manually.20:56
pabelangerdmsimard: ya, nodepool logs will be helpful20:56
dmsimardI'll increase verbosity, not seeing much right now20:57
jlkrbergeron: I saw that and it's an open tab for me to start reading.21:08
mordreddmsimard: I will be interested in what you learn21:09
dmsimardmordred: getting sidetracked right now, our nodepool's logging.conf is pretty darn messy too21:10
dmsimardlet you know when I find something21:10
mordreddmsimard: kk. thanks21:11
jlkjeblair: ugh, yeah I didn't see they already deprecated "integration_id". I'll rebase.21:12
clarkbpabelanger: dmsimard fwiw the reason we don't delete the server if the floating ip fails to delete is that only good way of knowing if the fip is in use is via the server record so idea is they have to be deleted together21:13
dmsimardclarkb: makes sense, something is off though -- it's like there's a race condition where the floating ip is unbound first, allocated to another server and then it tries to delete the original server and fails21:17
*** jkilpatr has joined #zuul21:21
jeblairomg jlk! i have reviewed your entire github stack.  the integration/apps thing was the only non +2.  cc mordred21:26
jlkhells yeah!21:26
jlkjeblair: in that case, should I wait for mordred 's +2/W and just do a follow up patch to s/integration_id/app_id/ ?21:27
jlkinstead ore rebasing 10~ patches?21:27
jeblairjlk: if it's all the same to you, i'd say fix+rebase now; i'll re-add any +2s of mine that get dropped and mordred or i can +w the stack21:31
jlkalrighty21:31
mordredjlk: I agree with all of the things21:32
mordredjeblair: yay!21:32
mordredjeblair, jlk: I'll go do the followup review pass as soon as the rebase hits21:32
*** jkilpatr has quit IRC21:45
*** jkilpatr has joined #zuul21:45
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Include exc_info in reporter failure  https://review.openstack.org/46076521:46
mordredjlk, jeblair: wow. no kidding. the rest of that stack looks great21:46
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add cachecontrol to requests to github  https://review.openstack.org/46158721:47
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Implement github trigger requirement status  https://review.openstack.org/46338621:47
jlkincoming.....21:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Use util functions to make lists of things  https://review.openstack.org/46919221:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Include tenant name in github context  https://review.openstack.org/46387121:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement github pipeline req of current-patchset  https://review.openstack.org/46858921:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement github pipepline req of open  https://review.openstack.org/46821321:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Save installation ids to a cache and fetch them per project  https://review.openstack.org/46342421:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Catch integration key file not found in zuul  https://review.openstack.org/46342521:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Create github client each time it's called.  https://review.openstack.org/46342121:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Use app_id with github  https://review.openstack.org/46342021:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Refactor integration key loading to always load  https://review.openstack.org/46342321:54
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Decode JSON body once for requests  https://review.openstack.org/46342221:54
*** dougbtv has quit IRC22:07
pabelangerconfirmed locally nodepool-builder was running under python3.5 :)22:09
pabelangerI know we test it with nodepool-dsvm, but still cool having it work locally22:09
*** hasharAway has quit IRC22:17
jeblairmordred: i just saw https://review.openstack.org/465718 and realized i duped some (but not all) of that.  sorry.22:20
mordredjeblair: no worries at all!22:20
mordredjlk, jeblair: BOOM. just +A'd the stack22:28
* jlk dances22:29
jeblairjlk, jesusaur: just reviewed https://review.openstack.org/449794 which depends on an abandoned change22:31
* jeblair decommissions "Github Zuul v3" dashboard and restarts gertty22:32
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Use app_id with github  https://review.openstack.org/46342022:33
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Create github client each time it's called.  https://review.openstack.org/46342122:33
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Decode JSON body once for requests  https://review.openstack.org/46342222:34
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Refactor integration key loading to always load  https://review.openstack.org/46342322:34
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Save installation ids to a cache and fetch them per project  https://review.openstack.org/46342422:34
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Catch integration key file not found in zuul  https://review.openstack.org/46342522:34
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Include tenant name in github context  https://review.openstack.org/46387122:34
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Implement github pipepline req of open  https://review.openstack.org/46821322:35
jesusaurwhoo, the github stack is merging22:35
*** Zara has quit IRC22:35
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Convert some leftover changeish mentions to ref  https://review.openstack.org/46571822:35
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Implement github pipeline req of current-patchset  https://review.openstack.org/46858922:36
*** SotK has quit IRC22:36
jeblairmordred: +2 thx!22:36
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Use util functions to make lists of things  https://review.openstack.org/46919222:37
jeblairjlk: ^ that's the tail!22:37
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Log and collect stats for events consistently  https://review.openstack.org/46866422:40
jlkwe'll have to re-deploy and see where it falls over. But jamielennox|away is gone all week22:41
jeblairjlk, mordred: well, it might be about time for us to point zuulv3-dev at github too, so you might have some compatriots there :)22:42
mordredindeed!22:42
mordredI can think of two different jobs I'd like to run just off the top of my head22:43
jeblairnote that i still don't consider zuulv3 secure or correct yet, so baby steps are warranted.22:43
jlkWe also don't have depends-on yet, so things will be a bit difficult for cross-repo type workflows22:45
mordredjlk: they will - but "does this PR to ansible break zuul" would be a good start even without depends-on22:46
jeblairyeah, and that's something we need to pull up into the driver interface.  i don't think it'll be too hard.  we should look at tobiash's dependency-cycle-detection-in-pipeline change first; it may help and affect how we implement that.22:47
mordredjeblair: speaking of tobiash... I just respun https://review.openstack.org/468664 - but tobiash has a comment on PS1 that is potentially worth not missing22:48
jeblairmordred: yeah, i agree, and https://review.openstack.org/468554 is partly based on his suggestions22:50
mordredjeblair: ah neat!22:51
jeblairmaybe that's the start of a pattern?  i dunno, it's new to me.  :)22:54
jeblairseemed to work pretty well in that case.22:55
jeblairwill probably work well in the other distributed workers too (merger, etc).22:55
jeblairthe scheduler / pipeline managers may need a slightly different approach (since they are single threaded)22:55
mordredjeblair: btw - jesusaur left a comment on https://review.openstack.org/#/c/46117623:01
*** SotK has joined #zuul23:03
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Store initial repo state in the merger  https://review.openstack.org/46117623:10
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Use previously stored repo state on executor  https://review.openstack.org/46117723:11
jeblairmordred, jesusaur: oops, too late for my -1 on my own change23:11
jeblairjesusaur: your question led me to find an error :)23:11
mordredjeblair: yay!23:11
jeblairi think we can just fix with a followup; it's not a regression23:12
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add default-branch property to projects  https://review.openstack.org/46733423:12
mordredjeblair: cool23:12
jeblairi'm looking into the failures of the last 3 changes in that stack (which seem legit)23:13
*** dougbtv has joined #zuul23:14
jesusaurjeblair: yay, i'm helping!23:14
*** dkranz has quit IRC23:19
jlkthe "my changes" screen in gertty is so so much smaller now!23:35
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Remove pipeline argument from various report fncts  https://review.openstack.org/46425223:41

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