[ https://ovirt-jira.atlassian.net/browse/OVIRT-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38649#comment-38649 ] Barak Korren commented on OVIRT-2633: ------------------------------------- I've created OVIRT-1852 in the past to try and optimize the CQ algorithm for the case mentioned here. We could also consider allowing manual removal of changes in case we are certain we don't want to test them - but allowing that may be risky.

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 Components: Change Queue 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)