This should be rather harmless because the history does not take up much space, and is only kept for the failed barriers in failed tests, by default. It should significantly ease debugging of failed step file tests.
Signed-off-by: Michael Goldish <[email protected]> --- client/tests/kvm/kvm_tests.cfg.sample | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/client/tests/kvm/kvm_tests.cfg.sample b/client/tests/kvm/kvm_tests.cfg.sample index c73da7c..54c9975 100644 --- a/client/tests/kvm/kvm_tests.cfg.sample +++ b/client/tests/kvm/kvm_tests.cfg.sample @@ -30,6 +30,7 @@ variants: type = steps fail_if_stuck_for = 300 stuck_detection_history = 2 + keep_screendump_history = yes force_create_image = yes kill_vm = yes kill_vm_timeout = 60 @@ -39,6 +40,7 @@ variants: type = steps fail_if_stuck_for = 300 stuck_detection_history = 2 + keep_screendump_history = yes - boot: install setup type = boot -- 1.5.4.1 -- 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
