Simon Westphahl 201082dc2a Cancel jobs of abandoned circular dep. change ... When a change that is part of a circular dependency is abandoned we'd set the item status to dequeued needing change. This will set all builds as skipped, overwriting exiting builds. This means that when the item was removed, we did not cancel any of the builds. For normal builds this mainly waste resources, but if there are paused builds, those will be leaked and continue running until the executor is force-restarted. The fix here is to cancel the jobs before setting it as dequeued needing change. Change-Id: If111fe1a21a1c944abcf460a6601293c255376d6		2024-04-11 10:05:47 +02:00
..
playbooks	Cancel jobs of abandoned circular dep. change	2024-04-11 10:05:47 +02:00
zuul.yaml	Cancel jobs of abandoned circular dep. change	2024-04-11 10:05:47 +02:00