zuul/zuul/manager
Clark Boylan 35bc94147c Update following changes logging
A user pointed out that approving a parent change [0] did not enqueue a
child change [1] that had all necessary votes. On inspection of the
logs [2] it isn't clear why this happened as at least one other change
was found.

One thing I noticed is that 'Depends-on' instead of 'Depends-On' was
used but both Gerrit and zuul seem to treat this string case
insensitively so that shouldn't matter.

Update our logging to aid in further debugging should this happen again.
In particular log already known following changes which comes from our
change cache and newly discovered following changes which comes from the
code review system. Hopefully this will help identify where we're not
finding the info we expect. Additionally record the number of possible
depending changes found by Gerrit. This should give us an indication for
whether or not Gerrit returning the information we expect.

[0] https://review.opendev.org/c/openstack/devstack/+/860795
[1] https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/857031
[2] https://paste.opendev.org/show/b6P1Uy2VjAMZOqtBbwyz/

Change-Id: Iad7fbbc3476ef1ddfd366e93b8505ed0fbdc1dc0
2022-11-22 15:22:23 -08:00
..
__init__.py Merge "Parallelize some pipeline refresh ops" 2022-11-10 15:01:09 +00:00
dependent.py Update following changes logging 2022-11-22 15:22:23 -08:00
independent.py Add detail to "depends on a change that failed to merge" 2022-08-11 18:44:07 -07:00
serial.py zuul-web: add pipelines' manager, triggers data in status 2021-10-27 15:13:01 +02:00
shared.py Remove deprecated pipeline queue configuration 2022-09-08 13:32:11 -07:00
supercedent.py Fix mutation while iterating over queues 2021-12-01 16:28:08 -08:00