[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39120#comment-39120 ] danken commented on OVIRT-2566: ------------------------------- Nir, in change-queue context, "gating" has a clear meaning: if you do not pass the suite, your package does not get to "tested". There is no meaning to "gate only vdsm-network". Currently, only basic-suite-* is gating. this means that someone can post an engine patch which breaks the network suite inadvertently. That's what I would like to prevent. You are right that this can be costly. We need to measure what is the time and resources to enable this gate, vs. our gain. Currently we do not know the price. The network suite is currently shorter in tests and more stable the then the basic suite.
make network suite blocking ---------------------------
Key: OVIRT-2566 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: danken Assignee: infra Priority: High
The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests... I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". [~gbenhaim@redhat.com], what should be done to make this happen?
-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)