The DeviceData order should now match the order in the XMLs produced by the DTM studio, which should make it easier to look at diffs (for debugging) between the XMLs produced by the automation program and the those produced by the DTM studio
Signed-off-by: Michael Goldish <[email protected]> --- client/tests/kvm/tests_base.cfg.sample | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/client/tests/kvm/tests_base.cfg.sample b/client/tests/kvm/tests_base.cfg.sample index 97b626f..f5ff5e9 100644 --- a/client/tests/kvm/tests_base.cfg.sample +++ b/client/tests/kvm/tests_base.cfg.sample @@ -390,7 +390,7 @@ variants: restart_vm = yes cdroms = test_timeout = 3600 - device_data = cat0 cat1 cat2 cat3 logoarch logoos whqlos whqlqual prog desc filter virt + device_data = cat0 cat1 cat2 cat3 prog desc virt filter logoarch logoos whqlos whqlqual descriptors = desc1 desc2 desc3 # DeviceData names dd_name_cat0 = Category -- 1.7.3.3 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
