All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org
Subject: Re: [Autotest] [KVM-AUTOTEST PATCH 4/4] kvm_tests.cfg.sample: add 'keep_screendump_history = yes' to step file tests
Date: Thu, 18 Jun 2009 11:31:34 -0300	[thread overview]
Message-ID: <1245335494.16589.9.camel@freedom> (raw)
In-Reply-To: <9eb8a47b6d4ebe8abd004db0600a2a716e9ff461.1245094830.git.mgoldish@redhat.com>

On Mon, 2009-06-15 at 22:45 +0300, Michael Goldish wrote:
> 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 <mgoldish@redhat.com>
> ---
>  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

Excellent feature indeed.

-- 
Lucas Meneghel Rodrigues
Software Engineer (QE)
Red Hat - Emerging Technologies


  reply	other threads:[~2009-06-18 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 19:45 [KVM-AUTOTEST PATCH 0/4] Step file tests: introducing a new feature and some small changes Michael Goldish
2009-06-15 19:45 ` [KVM-AUTOTEST PATCH 1/4] kvm_guest_wizard: rename output_dir to debug_dir in barrier_2() Michael Goldish
2009-06-15 19:45   ` [KVM-AUTOTEST PATCH 2/4] kvm_guest_wizard: pass 'params' directly to barrier_2() Michael Goldish
2009-06-16 14:57     ` Uri Lublin
2009-06-15 19:45   ` [KVM-AUTOTEST PATCH 3/4] kvm_guest_wizard: allow keeping screendump history for debugging purposes Michael Goldish
2009-06-18 14:30     ` [Autotest] " Lucas Meneghel Rodrigues
2009-06-18 15:30       ` Michael Goldish
2009-06-15 19:45   ` [KVM-AUTOTEST PATCH 4/4] kvm_tests.cfg.sample: add 'keep_screendump_history = yes' to step file tests Michael Goldish
2009-06-18 14:31     ` Lucas Meneghel Rodrigues [this message]
2009-06-18 14:40 ` [KVM-AUTOTEST PATCH 0/4] Step file tests: introducing a new feature and some small changes Lucas Meneghel Rodrigues

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1245335494.16589.9.camel@freedom \
    --to=lmr@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mgoldish@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.