On 10/25/2012 06:06 AM, Lucas Meneghel Rodrigues wrote:
On 10/25/2012 07:38 AM, Plamen Dimitrov wrote:
Although this seems reasonable, I encountered further problems.
They follow from the fact that a virtual test uses "env",
"test.bindir" and
other parameters which are prepared by and for the "virt" main test
and then
passed to it as an argument. Turning any virtual test into a utility then
requires to somehow reuse those outside of the "virt" test, perform
similar
"env" processing, and even conflict with its original "env"
preparation. Can we
then handle vm objects outside of a virt test? If not is there any
other way
to make a virtual test be repeated as many times as needed?
lmr,
This is also a problem with env, IIRC the version number doesn't
automatically get incremented when you run tests from the command-line.
Cartesian alone can't fix this IMHO. The previous env file (and other
files like /tmp/address_pool) will always be used even if they have
"bad" info in them.
Personally I wouldn't mind seeing 'make_clean' automatically run before
tests, unless some magic command-line option is provided. This would
probably require adjusting the server code to specify this magic option,
for when env should be preserved.
Just a thought.
--
Chris Evich, RHCA, RHCE, RHCDS, RHCSS
Quality Assurance Engineer
e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
