Nightly/bare metal vdsm check-merged jobs
Description
Activity
danken April 27, 2017 at 1:06 PM
spoken with Barak. He meant adding a new suit to OST.
danken April 27, 2017 at 12:53 PM
I don't really understand your suggestion. OST is all about system test. vdsm check-merged is about testing vdsm API.
Do you suggest to pull in vdsm-tests onto host0 in OST, and run them there after OST finishes? Or do you suggest a completely new OST suit, dedicated to vdsm functional tests?
Eyal Edri March 20, 2017 at 2:32 PM
As discussed, please add these tests to the OST suite.
If we'll find out that they are taking too long, we'll introduce a nightly OST suite if needed.
Barak Korren March 6, 2017 at 2:14 PM
OST "experimental" is probably the way to go for now because:
It runs on bare-metal
It does not run for every patch but it does run when there are resources available, so it is as close as possible to running on every patch.
Eyal Edri March 6, 2017 at 1:29 PM
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.
@Barak Korren any thoughts?
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