Jenkins jobs are always running for abandoned patches

[wingwj]

Jenkins met some problems about abandoned patches.
The Jenkins-jobs are always running even if the jobs were successful or failed..

I've checked some patches[1][2][3] suit the issue.
It look like if you add comments to an abandoned patch, the Jenkins will start check jobs again and again..

[1] https://review.openstack.org/#/c/75802/
[2] https://review.openstack.org/#/c/74917/
[3] https://review.openstack.org/#/c/91606/

[Antoine "hashar" Musso (hashar)]

Another example: https://review.openstack.org/#/c/82627/

That change got abandoned with Jenkins V+1 and a CR-1. Joshua commented on it and that triggered a loop of 'check' jobs.

[Jeremy Stanley (fungi)]

The fix for this is already pending at https://review.openstack.org/91911 but until it's approved and zuul restarted, you can work around the behavior by restoring (un-abandoning) the change long enough for zuul to successfully land a vote on it, then abandoning it again.

[Jeremy Stanley (fungi)]

https://review.openstack.org/91911 merged 05-05 23:31 UTC.