[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39121#comment-39121 ] Dafna Ron commented on OVIRT-2566: ---------------------------------- its basic and upgrade suites that run. the basic suite covers multiple projects and should continue running. I think that we should not add any specific components suites for 3 reasons: 1. Basic suites tests basic tests on all components, testing your specific area would not give the coverage we would like as sometimes the code change would effect multiple components and we are likely to miss serious regressions. 2. if we start adding more and more suites to CQ we would end up testing like QE and we are not providing those sort of tests 3. if we add the network suite we will have to add storage, virt, sla atc and we do not have resources to run every suite on every change. I think that the basic and upgrade suite provide the coverage we need for CQ and other suites are running in check-patch. If you believe that the basic suite is not stable or lacking, please contribute to stabilizing and adding to it.

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)