On 02/03/2014 10:21 AM, Paolo Bonzini wrote:
I'm using the test runner to quickly start tests from a configuration file. I absolutely do not want _anything_ to get in the way of the configuration file. However, since I last updated my git checkout I see that roughly the opposite is happening and, from a first look at the code, it seems hard to fix.For example, even though keep_image_between_test is just a synonym for restore_image=yes: def _process_restore_image_between_tests(self): if not self.options.keep_image_between_tests: self.cartesian_parser.assign("restore_image", "yes") The test runner is hard-coding the reference to the command-line option instead: if not options.keep_image_between_tests: logging.debug("Creating first backup of guest image") qemu_img = storage.QemuImg(d, data_dir.get_data_dir(), "image") qemu_img.backup_image(d, data_dir.get_data_dir(), 'backup', True) logging.debug("") and there is no way to disable this first backup either. The JeOS download is insanely slow (1.5 hours) and I'm not sure why it should even be attempted if I'm running tests on other OSes or specifying my own configuration file. I'm worried of this kind of assumptions being made by standalone_test.py. Should I just write my own test runner?
I'm sorry, I completely forgot to disable such inappropriate behavior when using -c. I'll fix that and make things saner.
Lucas _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
