[
https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir...
]
Eyal Edri commented on OVIRT-2566:
----------------------------------
We still need to allocate bare metal to run it on each CQ run, and I'm not
sure we have available resources for it, pretty sure we don't have since
KubeVirt took half of the hosts.
On Mon, Mar 4, 2019 at 2:09 PM danken (oVirt JIRA) <
--
Eyal edri
MANAGER
RHV/CNV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <
https://www.redhat.com/>
<
https://red.ht/sig> TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
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#100098)