public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: supriya kannery <supriyak@in.ibm.com>
To: Uri Lublin <uril@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [KVM-AUTOTEST] [PATCH] Iterate over reboot
Date: Fri, 01 May 2009 14:48:02 +0530	[thread overview]
Message-ID: <49FABE4A.3000900@in.ibm.com> (raw)
In-Reply-To: <49EF2DE6.5060006@redhat.com>

Uri Lublin wrote:
> supriya kannery wrote:
>> A patch for iterating over VM reboot
>>
>
> I think adding iterations capability belongs to the infrastructure, 
> not the test itself. Implement it once in the infrastructure, instead 
> of once per test.
> Also I think autotest has such a capability (adding iteration=n to 
> job.run_test parameters).
>
In the older version of kvm_runtest (kvm_runtest_old), the iteration 
parameter can be added to the corresponding job.runtest() of each test 
type (boot, reboot, migration).Different Class and execute function are 
defined for each test type in old runtest infrastructure which gives the 
flexibility of providing independent iteration values. But in the 
current infrastructure, I am not sure how we can apply that way to 
iterate each test type. My guess is, defining an iteration parameter 
under corresponding test type variant in the  kvm_test.cfg file  is one 
of the ways.  Pls let me know if I overlooked anything here.  

Thanks, Supriya

  reply	other threads:[~2009-05-01  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 18:39 [KVM-AUTOTEST] [PATCH] Iterate over reboot supriya kannery
2009-04-20 19:38 ` Ryan Harper
2009-04-22  7:54   ` supriya kannery
2009-04-22 14:47 ` Uri Lublin
2009-05-01  9:18   ` supriya kannery [this message]
     [not found] <670003666.547921241172530227.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-01 10:13 ` Michael Goldish
2009-05-04 12:08   ` supriya kannery
2009-05-25 11:21     ` Uri Lublin

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=49FABE4A.3000900@in.ibm.com \
    --to=supriyak@in.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=uril@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox