[
https://ovirt-jira.atlassian.net/browse/OVIRT-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28226#comment-28226
]
eyal edri [Administrator] commented on OVIRT-1223:
--------------------------------------------------
I suggested in the past to move the check-merged jobs into an OST suite we can
run nightly / few times a day.
Since check-merged isn't gating now, there is no real value to run it after
each commit.
Once we'll introduce Gating, we can consider to run it pre-merge.
[~bkor...@redhat.com] any thoughts?
> Nightly/bare metal vdsm check-merged jobs
> -----------------------------------------
>
> Key: OVIRT-1223
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1223
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Leon Goldberg
> Assignee: infra
>
> Hey,
> We're trying to come up with a solution to our lengthy check-merged
> jobs, that are about to become even lengthier now when we've
> discovered we're missing a permutation to our network tests.
> check-merged currently takes roughly 50 minutes to run to completion,
> with the network tests taking roughly 30 minutes; with the additional
> permutation check-merged will run for more than an hour.
> We thought of 2 possible solutions:
> 1) Only run the additional permutation once a day (e.g. introduce a
> nightly job).
> 2) Run check-merged on bare metal -- network tests take roughly 1/3 of
> the time on bare metal.
> Somehow closing the gap to bare metal would also of course be nice.
> We'd love your input.
> Thanks,
> Leon
--
This message was sent by Atlassian JIRA
(v1000.789.5#100032)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
