Uri Lublin wrote:
supriya kannery wrote:
A patch for iterating over VM reboot
I think adding iterations capability belongs to the infrastructure,
not the test itself. Implement it once in the infrastructure, instead
of once per test.
Also I think autotest has such a capability (adding iteration=n to
job.run_test parameters).
In the older version of kvm_runtest (kvm_runtest_old), the iteration
parameter can be added to the corresponding job.runtest() of each test
type (boot, reboot, migration).Different Class and execute function are
defined for each test type in old runtest infrastructure which gives the
flexibility of providing independent iteration values. But in the
current infrastructure, I am not sure how we can apply that way to
iterate each test type. My guess is, defining an iteration parameter
under corresponding test type variant in the kvm_test.cfg file is one
of the ways. Pls let me know if I overlooked anything here.
Thanks, Supriya
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
