[
https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-2566:
-------------------------------------
Not for specific patches - but we can enable it for ALL patches.
We can consider allowing some customization of the Zull configuration at project level to
allow running specific suits for specific patches, but this will require some code changes
in several places. We can plan this once we're in production with the current set of
suits.
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-te...
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(a)redhat.com], what should be done to make this happen?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100108)