Zuul should remove unmergable changes from queue as soon as possible.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zuul |
Fix Committed
|
Undecided
|
Clark Boylan | ||
Bug Description
When a change in a DependentPipeline cannot merge with the current state of the Pipeline zuul keeps it queued as it is possible that as the Pipeline changes the unmergable change will become mergable. This often limits zuuls ability to test as many changes as possible in parallel. Zuul should check if a currently unmergable change has any chance of merging and remove the change if it does not.
An example of what happens to zuul's queue when things cannot merge:
Project openstack/nova change 21701,2
gate-nova-docs: SUCCESS
gate-nova-pep8: SUCCESS
gate-
gate-
gate-
gate-
gate-
Followed by:
Project openstack/nova change 21592,3
gate-nova-docs: SUCCESS
gate-nova-pep8: SUCCESS
gate-
gate-
gate-
gate-
gate-
Followed by:
Project openstack/nova change 21287,2
gate-
gate-
gate-
gate-
gate-
gate-
gate-
Followed by:
Project openstack/nova change 21568,1
Followed by:
Project openstack/nova change 21414,4
Followed by:
Project openstack/nova change 21695,2
Followed by:
Project openstack/nova change 21101,11
| Changed in zuul: | |
| assignee: | nobody → Clark Boylan (cboylan) |
| status: | New → In Progress |
| OpenStack Infra (hudson-openstack) wrote Fix merged to zuul (master) | #1 |
| Changed in zuul: | |
| status: | In Progress → Fix Committed |
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit 81f0b5763955fcd
Author: Clark Boylan <email address hidden>
Date: Mon Feb 11 17:48:43 2013 -0800
Dequeue changes if they have no hope of merging.
In the DependentPipeline remove changes if they have absolutely no
chance of merging (all possible merge combinations fail). This allows
zuul to remove changes as soon as possible when it is known that they
cannot merge and continue testing the remaining changes.
Fixes bug 1123329
Change-Id: I97af03cca99754