On Sun, Mar 17, 2013 at 07:58:56PM -0400, Cole Robinson wrote: > On 03/17/2013 11:25 AM, Gleb Natapov wrote: > > On Fri, Mar 15, 2013 at 08:09:09PM -0400, Cole Robinson wrote: > >> Some tests want extra arguments as enumerated in unittests.cfg, > >> use them. > >> > >> unittests.cfg also has a few sections about invoking certains tests > >> with different combinations of options, but x86-run doesn't do > >> anything with that. > > With this it will not be possible to use x86-run outside of autotest, > > no? > > > > Not true, x86-run is still meant to be the standalone helper script for > running unittests. autotest doesn't care about x86-run, and ConfigParser is a > standard python module. > > x86/unittests.cfg already exists in the kvm-unit-tests repo, I assumed it was > encoding required test options but maybe I'm wrong about that. It's still > useful to build off of if there's value in running some tests with different > combinations of parameters. I fail to see what is the point here. unittests.cfg has been originally (and continues to be, AFAIK), intended for autotest: http://kerneltrap.org/mailarchive/linux-kvm/2010/6/24/6264146 Please don't remove manual execution from README. -- 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
