[
https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38314#comment-38314
]
danken commented on OVIRT-2566:
-------------------------------
https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/buildTimeTrend
shows that it runs for 44-48 minutes.
https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/buildTimeTrend
runs slightly quicker (41-45 minutes)
To save time I prefer the network suite to run in parallel to 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_network-suite-4.2/
> 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".
> [[email protected]], what should be done to make this happen?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/VQXDSAGMNLA3UC4ESAUOYJDUATKZYL2W/
