Friday, 2020-01-24

*** tosky has quit IRC00:28
corvusclarkb: nope we already do.00:29
corvusi was surprised myself; our gerrit is already new enough to require that :)00:29
corvusclarkb: er, i stand corrected00:31
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Update sdk to v0.13.0 and install dhall-to-json  https://review.opendev.org/70210300:31
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Setup Prelude and Kubernetes binding  https://review.opendev.org/70210400:31
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Replace existing operator tasks with the new application  https://review.opendev.org/70210600:31
tristanCso, here is the simplified version ^  it's not as complete as the previous one but it seems to work for the simple case00:32
tristanCbasically, the dhall code is now contained in that single file: https://review.opendev.org/#/c/702106/16/conf/zuul/resources.dhall00:33
openstackgerritMerged zuul/nodepool master: Lower min-ready request priority  https://review.opendev.org/70405800:34
tristanCand there are some test files to run the things without kubernetes ( https://review.opendev.org/#/c/702106/15..16/playbooks/files/cr_spec.yaml ) , or without operator ( https://review.opendev.org/#/c/702106/15..16/playbooks/files/local.yaml )00:40
tristanCi'll add the missing attributes and rebase the rest of the changes tomorrow.00:42
*** johanssone_ has quit IRC00:47
*** johanssone has joined #zuul00:52
*** zxiiro has quit IRC01:08
*** andreaf has quit IRC01:37
*** andreaf has joined #zuul01:38
*** zxiiro has joined #zuul01:41
*** swest has quit IRC02:07
*** rf0lc0 has quit IRC02:18
*** swest has joined #zuul02:22
*** bhavikdbavishi has joined #zuul02:55
*** bhavikdbavishi1 has joined #zuul03:02
*** bhavikdbavishi has quit IRC03:04
*** bhavikdbavishi1 is now known as bhavikdbavishi03:04
*** bhavikdbavishi has quit IRC03:24
*** bhavikdbavishi has joined #zuul03:41
*** zxiiro has quit IRC03:49
*** rlandy has quit IRC04:05
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Replace existing operator tasks with the new dhall function  https://review.opendev.org/70210604:50
*** raukadah is now known as chkumar|ruck05:00
*** chkumar|ruck is now known as chkumar|rover05:24
*** swest has quit IRC05:26
*** evrardjp has quit IRC05:34
*** evrardjp has joined #zuul05:34
*** swest has joined #zuul06:10
*** jpena|off is now known as jpena08:00
*** felixedel has joined #zuul08:09
*** at_work has quit IRC08:24
*** notnone has joined #zuul08:29
*** tosky has joined #zuul08:36
openstackgerritMerged zuul/zuul-jobs master: fetch-tox-output: introduce zuul_use_fetch_output  https://review.opendev.org/68186408:36
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Making opensuse-tumbleweed jobs nv  https://review.opendev.org/70269308:39
AJaegerconfig-core, zuul-maint, please review ^ to be able to merge some changes in zuul-jobs08:40
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Making opensuse-tumbleweed jobs nv  https://review.opendev.org/70269308:41
AJaegerargh, needs a rebase ^08:42
*** evrardjp has quit IRC08:54
*** felixedel has quit IRC08:59
fungiAJaeger: i take it there's a problem with opendev's tumbleweed mirror again?09:01
AJaegerfungi: yes ;(09:02
AJaegera file is missing apparently09:03
*** pcaruana has joined #zuul09:14
openstackgerritMerged zuul/zuul-jobs master: Making opensuse-tumbleweed jobs nv  https://review.opendev.org/70269309:31
AJaegertristanC: all your zuul_use_fetchoutput changes are in merge-conflict, please rebase and resolve...09:35
*** bhavikdbavishi has quit IRC09:38
*** bhavikdbavishi has joined #zuul09:39
*** saneax has joined #zuul09:43
*** saneax has quit IRC09:52
openstackgerritUzume proposed zuul/zuul master: Change default Gerrit HTTP auth method  https://review.opendev.org/70406810:00
openstackgerritMerged zuul/zuul-jobs master: Return subunit test report as artifact  https://review.opendev.org/70323510:04
*** bhavikdbavishi has quit IRC10:13
*** bhavikdbavishi has joined #zuul10:14
*** bhavikdbavishi has quit IRC10:18
*** bhavikdbavishi has joined #zuul10:36
*** bhavikdbavishi has quit IRC10:45
*** avass has joined #zuul11:39
*** rf0lc0 has joined #zuul12:14
*** jpena is now known as jpena|lunch12:29
openstackgerritTobias Henkel proposed zuul/zuul master: Handle draft pull requests in canMerge  https://review.opendev.org/70415012:55
tobiashpabelanger: you might be interested in ^ to prevent potential gate loops when working with draft pull requests12:57
openstackgerritTobias Henkel proposed zuul/zuul master: Handle draft pull requests in canMerge  https://review.opendev.org/70415013:04
*** sshnaidm|afk has quit IRC13:11
tristanCtobiash: it seems like the current zuul-executor image on docker hub (31271b82631a  16 hours ago  1.38 GB) is affected by the `ERROR zuul.ansible_manager: Ansible version 2.9 not working` issue again13:15
tristanCAJaeger: thanks, i'll have a look shortly.13:18
*** hashar has joined #zuul13:19
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Generate TLS certificats for the gearman service  https://review.opendev.org/70271613:25
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add OpenShift SCC and functional test  https://review.opendev.org/70275813:25
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Handle service restart when connections are changed  https://review.opendev.org/70362413:25
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add tenant reconfiguration when main.yaml changed  https://review.opendev.org/70363113:25
*** rlandy has joined #zuul13:28
*** rf0lc0 is now known as rfolco|doctor13:33
*** jpena|lunch is now known as jpena13:35
*** jamesmcarthur has joined #zuul13:48
openstackgerritAntoine Musso proposed zuul/zuul master: On CI, use a tmpfs for ZUUL_TEST_ROOT  https://review.opendev.org/70416014:10
*** sshnaidm has joined #zuul14:13
*** sshnaidm has quit IRC14:17
openstackgerritAntoine Musso proposed zuul/zuul master: On CI, use a tmpfs for ZUUL_TEST_ROOT  https://review.opendev.org/70416014:23
*** sshnaidm has joined #zuul14:24
*** zxiiro has joined #zuul14:24
pabelangertobiash: acK!14:25
*** hashar has quit IRC14:29
*** sshnaidm_ has joined #zuul14:31
*** sshnaidm has quit IRC14:31
fungii'm trying to come up with missing terms for our zuul glossary, since it's very sparse at the moment. here's what i've got so far i could add: artifact, connection, job, job variant, node, parent job, pipeline, project, project gating, project template14:40
fungianything else anyone think should be added?14:40
fungioh, tenant should probably be in there too14:40
tristanCthe executor image issue can be observed here: https://zuul.opendev.org/t/zuul/build/e7b91711195d418fb6f3f9d0dc2a2fbf/log/docker/k8s_executor_zuul-executor-0_myproject_2b25e25c-3eb2-11ea-998a-fa163e6bfc57_5.txt#26-4414:41
dmsimardfungi: speculative merging ? gating ? depends-on ?14:44
*** panda is now known as panda|bbl14:45
fungigating could be used instead of project gating, i guess14:45
fungibut we already have gate in there for a related purpose14:45
dmsimardah, yeah, project gating is fine -- had misread14:46
fungidepends-on is a commit message directive not a term, i don't think, but we could maybe have an entry on cross-project dependencies14:46
fungii wonder if speculative execution would be a better term than speculative merging. i'll see if we say either anywhere in the other docs14:47
fungioh, build and buildset should get entries14:48
dmsimardnodeset is also missing15:00
*** hashar has joined #zuul15:03
openstackgerritAntoine Musso proposed zuul/zuul master: On CI, use a tmpfs for ZUUL_TEST_ROOT  https://review.opendev.org/70416015:04
openstackgerritAntoine Musso proposed zuul/zuul master: On CI, use a tmpfs for ZUUL_TEST_ROOT  https://review.opendev.org/70416015:05
*** jamesmcarthur has quit IRC15:08
fungidmsimard: ooh, yep good suggestion15:12
corvusfungi: ++15:12
*** ChrisShort has quit IRC15:18
*** ChrisShort has joined #zuul15:18
*** chkumar|rover is now known as raukadah15:19
*** sshnaidm_ is now known as sshnaidm|off15:25
*** jamesmcarthur has joined #zuul15:28
*** mnasiadka has quit IRC15:31
*** mnasiadka has joined #zuul15:32
hasharhi :)  Iam throwing an idea out of the blue. zuul-build-image  builds the Docker images  and gets paused to keep the docker registry available15:36
hasharwhich would mean that jobs keeps a node busy in Nodepool while other jobs in the build set apparently do not need the registry to be available15:36
corvushashar: it's used by zuul-quick-start15:38
hasharahhh15:38
hasharthat is the dependency I was looking ;]15:38
corvusyeah, i'd like to find a way to speed that up a bit.  it's supposed to get a node for the second job with high priority, but that doesn't happen as quickly as i would like.15:39
hasharthe job is paused for the duration of the whole buildset isn't it?15:39
corvushashar: no, just until its dependencies are done15:39
corvus(but because of the dependency chain, it may be the last to finish)15:39
hasharI just noticed zuul-quick-start has a  "requires: docker-image"    which is I guess how the dependency is defined15:40
hashar thx ;)15:41
corvushashar: no, that's actually artifact transfer from other buildsets; the dependency is set with "dependencies" on the job15:41
corvushashar: https://opendev.org/zuul/zuul/src/branch/master/.zuul.yaml#L227-L22815:41
hasharneat15:42
corvushashar: the "requires" thing means that if there is a change ahead of it in the pipeline that "provides: docker-image", zuul-build-image will wait for that job to complete before it starts15:42
corvus(and it will use the built image from the one ahead)15:43
corvusthis lets us do things like make changes to base images and then use them in child images15:43
corvus(eg, zuul images are "FROM opendev/python-base", so we can make a change to python-base and then see that reflected in zuul's image)15:44
hasharahhhhh15:44
hasharthat might be a little bit too much of advanced use case for me right now ;]15:45
corvusyeah, it's not necessarily for everyone, but like most of zuul, when you need it, you need it.  :)15:45
hasharI am going to dig into ansible, I got to learn it eventually15:46
hasharand as an excuse to learn, I will try to speed up the zuul test suite15:46
*** samccann has quit IRC15:47
*** samccann has joined #zuul15:47
*** panda|bbl is now known as panda16:02
openstackgerritMerged zuul/zuul master: Fix canceling builds in starting phase  https://review.opendev.org/68441416:06
*** tosky has quit IRC16:16
tobiash\o/16:17
*** mauved has quit IRC16:20
*** mauved has joined #zuul16:21
*** hashar has quit IRC16:28
openstackgerritPaul Belanger proposed zuul/zuul master: Update component diagram for GitHub / Web events  https://review.opendev.org/70417216:37
openstackgerritPaul Belanger proposed zuul/zuul master: Update component diagram for GitHub / Web events  https://review.opendev.org/70417216:41
*** rfolco|doctor is now known as rfolco16:45
*** Goneri has joined #zuul16:50
clarkbhashar isn't here anymore but I'm trying to quantify if https://review.opendev.org/704160 is faster right now16:56
corvusclarkb: my recollection is that it didn't seem to make much of a difference on the cloud providers available the last time we tried it several years ago16:58
corvusprobably due to nuances of how storage worked on them16:58
corvusit *certainly* makes a difference for me locally though.  so i'm +2 on the principle of it being a good example to follow and probably not hurting in the gate.16:59
corvus(also, i don't want to wear out my ssd)17:00
clarkbya it doesn't seem to make anything worse at least17:00
*** hashar has joined #zuul17:05
clarkbwith a very low sample count of one before and one after on the same clouds py35 is ~30 seconds quicker and py37 is ~400 seconds quicker17:05
clarkbdepending on the cloud this may actually represent a nice improvement (rax-ord had the big increase, inap-mtl01 the small one)17:06
corvuscool, that sounds promising then17:06
*** hashar has quit IRC17:06
corvushashar: ^ this is re your tmpfs change; you missed a few lines (you can check eavesdrop to catch up but probably not that important :)17:06
openstackgerritMerged zuul/zuul-jobs master: Update roles/prepare-workspace-openshift/README.rst  https://review.opendev.org/70401717:08
clarkbhttps://zuul.opendev.org/t/zuul/build/9e6f918fdc8d49dfa34a3603e1d39553/log/job-output.txt#374 shows it is working too17:08
clarkbwith that I'll approve17:09
*** jpena is now known as jpena|off17:11
corvustobiash: https://review.opendev.org/691715 has been sitting with a +2 for a while if you don't mind taking a look17:11
tobiashcorvus: oops, I've overlooked that one, I'll review in a bit17:30
openstackgerritMerged zuul/zuul master: test: prevent ResourceWarning in test_client  https://review.opendev.org/70378217:32
tobiashcorvus: lgtm17:38
*** rlandy is now known as rlandy|brb17:41
openstackgerritPaul Belanger proposed zuul/zuul master: Add estimated time remaining tooltip to UI  https://review.opendev.org/70389217:42
openstackgerritPaul Belanger proposed zuul/zuul master: WIP: debug estimate_time on job start  https://review.opendev.org/70417917:42
openstackgerritMerged zuul/zuul master: Whitelist debug threads used by visual studio code  https://review.opendev.org/70324817:49
*** jamesmcarthur has quit IRC17:52
openstackgerritTobias Henkel proposed zuul/zuul master: Use apt mirror infrastructure during zuul-quick-start  https://review.opendev.org/64944817:56
tobiashcorvus, tristanC: re manage-ansible. What do you think if we make ansible installation single threaded by default (for the container build) and optionally multi threaded combined with different cache dirs per thread?18:01
tobiashthat way we could combine a reliable installation during the container build and still having faster setup times for the tox runs18:01
clarkbtobiash: different cache dirs should fix the contention problem with the packages and wheels right?18:01
tobiashclarkb: I think so18:01
clarkbI guess if that works in the tox jobs then we can switch the container builds to it?18:02
tobiashat least that's my assumption based on the various errors I've seen there18:02
tobiashclarkb: the container builds need to share a single cache dir because of the build process18:02
clarkboh right18:02
clarkbwe stage the packages to avoid needing buidl deps in the runtime18:03
tobiashyes18:03
tobiashok, we could get around this by manually merging the cache dirs afterwards18:03
tobiashoh actually, we don't need the cache from zuul-manage-ansible at all18:05
tobiashwe just copy the ansible envs into the dest image18:05
tobiashso yes, if it works in tox we could leverage this in the container build as well18:05
tristanCnot sure i understood what is going on, is this a pip issue?18:05
tobiashtristanC: the issue is that multiple pip processes work on the same cache while installing ansible into different venvs18:06
tobiashso the solution to keep multi-process installation would be to tell pip to use individual cache dirs18:07
tristanCtobiash: iiuc, if pip can't run concurrently, then this a pip bug where it should use a lock file to prevent that install failure?18:09
*** rlandy|brb is now known as rlandy18:09
tobiashyes, probably18:09
tristanCit seems already reported https://github.com/pypa/pip/issues/236118:11
tobiashthis one is about concurrently installing packages into the same environment, which is actually harder18:12
tobiashour issue is concurrently installing packages into different environments18:13
tobiashI found this one (which seems to be fixed since ages): https://github.com/pypa/pip/issues/114118:16
tobiashbut maybe the wheel cache isn't thread safe as well18:16
tobiashor it got broken again in the meantime18:18
tobiashnevertheless I think we probably don't want to rely on thread safety of pip so we can either go single threaded or with individual cache dirs or both18:19
openstackgerritPaul Belanger proposed zuul/zuul master: WIP: debug estimate_time on job start  https://review.opendev.org/70417918:20
*** jamesmcarthur has joined #zuul18:24
tobiashpabelanger: did you already try the js tooling for hacking on zuul-web? (asking because of ^)18:25
zbrcan we either merge https://review.opendev.org/#/c/702473/ or increase the timeouout from 3600 to 4000 ?18:25
zbrhttps://zuul.opendev.org/t/zuul/builds?job_name=tox-py35&project=zuul%2Fzuul18:26
tristanCtobiash: if that issue can be solved/mitigated by pip/wheel, it seems safer to go single threaded until it's fixed, otherwise i can't tell what is better (faster but more i/o intensive, or slower but using a single cache...)18:26
tobiashzbr: as there was opposition to 702473 we should increase the timeout, do you want to propose that?18:27
zbrsure, doing it now18:27
tobiashthx :)18:27
tobiashtristanC: well, separated caches are safe as well (we also can have both ways if we want)18:27
tristanCtobiash: fwiw, we have been able to install all the ansible using a single venv, it seems like 2.[6789] works with the same requirements.txt, we only keep the ansible modules and cli separated18:28
tristanCthough we use a special rpm spec script to do that, i don't know if venv can inherit from a non system-wide venv18:29
tristanCtobiash: is there a patch for separated caches? otherwise i can have look now if you want18:30
tobiashtristanC: right now it's just an idea :)18:30
tobiashwe could also just disable the cache instead of putting it into a tmpdir and throwing it away: --no-cache-dir18:31
tobiashpip supports that as well18:31
tobiashif that works, that would be easy18:31
tobiashand I also checked, we don't need that cache in the container builds18:32
zbranyone here against yaml anchors in job files?18:35
clarkbI think we use them for file matchers/excluders18:35
clarkbshould befine18:35
openstackgerritTobias Henkel proposed zuul/zuul master: Disable pip cache when managing ansible  https://review.opendev.org/70418418:35
tobiashtristanC: ^18:35
tristanCwhy would anyone be against yaml anchors? :)18:36
zbrthey are very useful to replicate stuck from check to gate18:37
openstackgerritSorin Sbarnea proposed zuul/zuul master: Increase timeout for tox-py27/36 jobs  https://review.opendev.org/70418518:38
openstackgerritTobias Henkel proposed zuul/zuul master: DNM: Test multi-threaded ansible setup without cache  https://review.opendev.org/70418618:39
clarkbzbr: one small nit on the commit message18:39
openstackgerritSorin Sbarnea proposed zuul/zuul master: Increase timeout for tox-py35/37 jobs  https://review.opendev.org/70418518:41
tobiashzbr: this conflicts with the first change in gate, you might want to rebase ^18:44
tobiash(in around 10min)18:45
openstackgerritPaul Belanger proposed zuul/zuul master: Add estimated time remaining tooltip to UI  https://review.opendev.org/70389218:56
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: DNM: test arbritary uid support for zuul image  https://review.opendev.org/70298018:57
clarkbthinking out loud here about job runtimes and how setup is a significant portion of that runtime. I seem to recall that ansible at some point started forking for every task and that slowed ansible down quite a bit18:58
clarkbdo any of the ansible folks know if there are any plans to go back to the old pre forking behavior?18:59
openstackgerritMerged zuul/zuul master: On CI, use a tmpfs for ZUUL_TEST_ROOT  https://review.opendev.org/70416019:01
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add zuul-operator-promote-image job  https://review.opendev.org/70418719:04
tristanCtobiash: perhaps the image is correct, it seems like for some reason, it's only the ansible-2.9 venv that failed to be validated when running in openshift... e.g. https://review.opendev.org/#/c/703631/3 and it's git-parent . Maybe https://review.opendev.org/#/c/702980/ will fix that issue19:06
tristanCtobiash: note that i'm not using the privileged scc, so the pod are still running with the AnyUid policy19:08
pabelangertristanC: clarkb: fungi: https://review.opendev.org/703892 should address comments from yesterday now19:08
clarkbpabelanger: cool, its the null check that we needed?19:08
pabelangeryah19:08
clarkbI'll verify it against the preview site and vote after19:08
pabelangerwe sould also say, job preparing to run on null19:09
pabelangerbut this works19:09
tristanCpabelanger: nice, thanks! i'll check the '' title doesn't yield a empty tooltip, otherwise lgtm19:11
openstackgerritMerged zuul/zuul master: Don't add implicit role if plugin found  https://review.opendev.org/69171519:11
pabelangertristanC: ++ I didn't see it in chrome19:12
pabelangeralso, happy to update logic with assistance19:12
pabelangerI wish it said 2 hours and 15 mins, but meh, this is better then nothing19:12
clarkbcould you do hours:minutes:seconds remaining?19:13
clarkbits a bit of math but not too bad19:14
pabelangeryes, but I think if time was great then 24 hours, it would become 0 hours19:14
clarkbwell you could do days too19:15
pabelangerhttps://stackoverflow.com/a/4145392219:15
tristanCpabelanger: aren't those estimate anyway?19:16
clarkboh I was thinking of doing the math directly19:16
pabelangertristanC: yup, estimate but sometime good to know if closer to 2 hours then 3 hours :)19:17
pabelanger1 hour window is better then nothing right now19:17
clarkbMINUTE=60 ; HOUR=MINUTE*60; DAY=24*HOUR; days=time/DAY ; remainer=time%DAY ; hours=remainder/HOUR ; remainder=remainder%HOUR; minutes=remainder/MINUTE ; seconds=remainder%MINUTE19:18
clarkbpabelanger: ^ that is the math19:19
clarkbassuming time is whole seconds19:19
openstackgerritTobias Henkel proposed zuul/zuul master: Increase timeout for tox-py35/37 jobs  https://review.opendev.org/70418519:19
clarkbpabelanger: you could also simplify it and calculate days first then feed the remainder into your format function19:19
pabelangeragree, maybe for next friday :)19:20
*** jamesmcarthur has quit IRC19:23
openstackgerritMerged zuul/zuul master: Update component diagram for GitHub / Web events  https://review.opendev.org/70417219:48
openstackgerritClark Boylan proposed zuul/zuul master: Be more specific with remaining time  https://review.opendev.org/70419119:55
clarkbpabelanger: ^ thats a follow on with the above formula19:55
clarkbit may need tweaking to get right (I am not 100% sure about js maths)19:55
openstackgerritTristan Cacqueray proposed zuul/zuul master: Dockerfile: add support for arbritary uid  https://review.opendev.org/65024619:56
tristanCzuul-maint : could you please review https://review.opendev.org/#/c/650246/6 , it already has a +2 and I added links to a job being fixed by the change in the review comment20:00
openstackgerritMerged zuul/zuul master: Increase timeout for tox-py35/37 jobs  https://review.opendev.org/70418520:16
openstackgerritTristan Cacqueray proposed zuul/nodepool master: kubernetes: add release note about service account token issue  https://review.opendev.org/70386920:20
*** hashar has joined #zuul20:30
*** hashar has quit IRC20:41
openstackgerritClark Boylan proposed zuul/zuul master: Be more specific with remaining time  https://review.opendev.org/70419120:55
*** hashar has joined #zuul20:58
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: fetch-subunit-output: introduce zuul_use_fetch_output  https://review.opendev.org/68188221:05
openstackgerritAntoine Musso proposed zuul/zuul master: Add client_id to RPC client  https://review.opendev.org/70420121:07
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: fetch-subunit-output: introduce zuul_use_fetch_output  https://review.opendev.org/68188221:08
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: DNM: test tox-py36 on openshift node  https://review.opendev.org/68204921:08
*** avass has quit IRC21:15
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: fetch-javascript-tarball: introduce zuul_use_fetch_output  https://review.opendev.org/68160321:15
openstackgerritClark Boylan proposed zuul/zuul master: Be more specific with remaining time  https://review.opendev.org/70419121:18
*** zxiiro has quit IRC21:23
*** rlandy has quit IRC21:44
pabelangerFriday afternoon questions. By using https://zuul-ci.org/docs/zuul/reference/jobs.html#pausing-the-job and starting child jobs, we might have a want to unpause the parent before the child finished. Mostly because child jobs take upwards of 2.5 hours, and we only need the parent for first 15mins of the job21:54
*** rfolco has quit IRC22:00
*** armstrongs has joined #zuul22:15
*** jamesmcarthur has joined #zuul22:21
*** armstrongs has quit IRC22:24
*** hashar has quit IRC22:49
*** jamesmcarthur has quit IRC22:57
clarkbpabelanger: I think the trick would be formalizing the signal that all children that want to access those resources are finished with them23:00
fungido we have a mechanism for a build to communicate any status change back to the scheduler before completion?23:08
clarkbfungi: zuul_return is per playbook I think so could probably be mangled to do this23:09
clarkbbut not 100% sure on that23:09
fungiwe did at one point talk about making it possible for a build to inform the scheduler early when it knows it's going to fail, so that pipeline changes can take effect sooner23:10
fungimaybe this falls into a similar category23:13
*** jamesmcarthur has joined #zuul23:14
*** jamesmcarthur has quit IRC23:23
openstackgerritClark Boylan proposed zuul/zuul master: Be more specific with remaining time  https://review.opendev.org/70419123:32
*** jamesmcarthur has joined #zuul23:40
clarkbhrm seems like zuul-tox-remote might be flaky23:50
clarkbtests.remote.test_remote_zuul_stream.TestZuulStream29.test_command is timing out?23:51
clarkbhttps://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_ac4/703892/7/gate/zuul-tox-remote/ac40b75/job-output.txt is an example23:51
pabelangerclarkb: fungi: yah, I was thinking each child job would use zuul_return to signal back some how to unpause, then once all child have done so the parent would resume and clean up23:57
clarkbpabelanger: but not all children may need the parent23:58
clarkbI guess it should't parent in that case23:58
clarkbso ya that could be the implication23:58
pabelangeryah23:59

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