On Wed, Aug 17, 2016 at 04:48:54PM +1000, Suraj Jitindar Singh wrote: > Invoking run_tests.sh without the -g parameter will by default run all of > the tests for a given architecture. This patch series will add a test which > has the ability to bring down the host and thus it might be nice if we > double check that the user actually wants to run that test instead of > them unknowingly bringing down a machine they might not want to. > > In order to do this add the option for a tests' group parameter in > unittests.cfg to include "nodefault" on order to indicate that it shouldn't > be run be default. > > When tests are invoked via run_tests.sh those with the nodefault group > parameter will be skipped unless explicitly specified by the "-g" command > line option. When tests with the nodefault group parameter are built and > run standalone the user will be prompted on invocation to confirm that > they actually want to run the test. > > This allows a developer to mark a test as having potentially adverse > effects and thus requires an extra level of confirmation from the user > before they are invoked. Existing functionality will be preserved and new > tests can choose any group other than "nodefault" if they want to be run > by default. > > Signed-off-by: Suraj Jitindar Singh <sjitindarsingh@xxxxxxxxx> > --- > > Change Log: > > V2 -> V3: > - Move checking on standalone invokation into a function > "skip_nodefault" in scripts/runtime.bash > V3 -> V4: > - Remove superfluous "STANDALONE=yes" > --- > arm/unittests.cfg | 3 +++ > powerpc/unittests.cfg | 3 +++ > scripts/runtime.bash | 27 ++++++++++++++++++++++++++- > x86/unittests.cfg | 3 +++ > 4 files changed, 35 insertions(+), 1 deletion(-) Reviewed-by: Andrew Jones <drjones@xxxxxxxxxx> -- 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
