On Mon, Nov 5, 2018 at 8:59 AM danken (oVirt JIRA) < jira@ovirt-jira.atlassian.net> wrote:
danken created OVIRT-2566: -----------------------------
Summary: 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".
I'm ok with this only if it will gate *only* vdsm-network package, and it will run in parallel, so it does not slow down OST run. For basic suite, we have too many random failures, so I don't think it is useful, and we should make it optional. Nir
[~gbenhaim@redhat.com], what should be done to make this happen?
-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095) _______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/VFQ776FLS2QBAT...