| opendevreview | Radosław Piliszek proposed openstack/project-config master: Add nebulous/asyncapi https://review.opendev.org/c/openstack/project-config/+/886615 | 08:26 |
|---|---|---|
| opendevreview | Merged openstack/project-config master: Add nebulous/asyncapi https://review.opendev.org/c/openstack/project-config/+/886615 | 10:23 |
| *** benj_1 is now known as benj_ | 14:12 | |
| JayF | I'm observing what appears, at least to me, to be weird scheduling behavior from zuul | 22:04 |
| JayF | e.g.: for 886865,2 it's already run (and failed) the openstack-tox-py310 job, but its parent, 886871,5 is still queued for openstack-tox-py310 | 22:05 |
| JayF | I'm seeing simliarly long queue times for 887008,1 as well, with openstack-tox-py38 (it literally finally popped the queue while I was typing this in) | 22:05 |
| JayF | I assume this might just be me noticing the status quo because I'm watching more closely troubleshooting this issue; but thought I'd call it out in case it actually is anomolous | 22:06 |
| clarkb | the requests are made in order but then the processing of them is at the mercy of cloud scheduling. It isn't abnormal to have child jobs run first as a result | 23:20 |
| clarkb | it should trend towards earlier requests being fulfilled first but if one cloud takes much longer to boot a node or if we end up retrying the alloted three times in one cloud while succeeding immediately in another you can see these behaviors | 23:20 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!