[ https://ovirt-jira.atlassian.net/browse/OVIRT-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38648#comment-38648 ] Barak Korren commented on OVIRT-2633: ------------------------------------- Not needed - this request is based on an incorrect assumption that the change queue is testing changes one-by-one serially. In the case mentioned above, if we suppose we already reported P1 as failed, and P10 has been merged, and lets realistically assume it was not merged before the next CQ test started, so what will happen is that P2-P9 will be tested together and fail, and from then it will take Log(2)(8) = 3 cycles to detect and throw away P2. If P10 is merged in the meantime - the next test will test P3-P10 and succeed, passing all changes assuming there are no further regressions.

Add posibility to remove changes from change queue before change, which actually fixes the issue ------------------------------------------------------------------------------------------------

Key: OVIRT-2633 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2633 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Martin Perina Assignee: infra

Let's have a patch P1, which created an issue and failed verification in change queue. Until a fix is prepared and merged as P10, there were merged other patches P2 - P9. Because P10 is merged as last, it contains all previous changes. And because we already know that P2 - P9 will fail, there is no reason to verify those changes and there should be a way how to remove them from the change queue, so P10 can be verified as soon as possible. Otherwise we are wasting valuable recources.

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)