From: Ryan Harper <ryanh@us.ibm.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
kvm@vger.kernel.org, uril@redhat.com, autotest@test.kernel.org
Subject: Re: [PATCH] [RFC] KVM test: Major control file cleanup
Date: Wed, 28 Oct 2009 13:18:50 -0500 [thread overview]
Message-ID: <20091028181850.GU13808@us.ibm.com> (raw)
In-Reply-To: <382425334.1152431256744581206.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
* Michael Goldish <mgoldish@redhat.com> [2009-10-28 10:43]:
>
> ----- "Lucas Meneghel Rodrigues" <lmr@redhat.com> wrote:
>
> > One thing that just occurred to me is, if we have a test config
> > "library" as you said, it's perfectly possible to put the actual test
> > set definitions and other config files inside the control file as
> > strings. This way one can control configuration inside the control
> > file,
> > making it more convenient for usage, let's say, inside the autotest
> > web
> > interface. Since the control file would be reduced in size, the
> > configuration snippets being in the control file would not be a huge
> > problem, while keeping the original autotest philosophy of keeping
> > stuff inside the control file... What do you think?
>
> Sounds great, except it won't allow you to debug your configuration
> using kvm_config.py. So the question now is what's more important --
> the ability to debug or ease of use when running from the server.
+1 debug
When creating new test scenarios I make *heavy* use of kvm_config.py;
I'd be lost without being able to debug test configuration files.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
next prev parent reply other threads:[~2009-10-28 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <393106486.1126051256722865111.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-10-28 9:48 ` [PATCH] [RFC] KVM test: Major control file cleanup Michael Goldish
2009-10-28 11:14 ` Lucas Meneghel Rodrigues
2009-10-28 15:43 ` Michael Goldish
2009-10-28 15:58 ` [Autotest] " Lucas Meneghel Rodrigues
2009-10-28 18:18 ` Ryan Harper [this message]
2009-10-28 19:47 ` Lucas Meneghel Rodrigues
2009-10-28 20:48 ` Michael Goldish
2009-10-30 13:54 ` Ryan Harper
2009-10-30 14:36 ` Lucas Meneghel Rodrigues
2009-10-28 15:57 ` Michael Goldish
2009-10-28 15:59 ` [Autotest] " Lucas Meneghel Rodrigues
2009-10-27 18:59 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=20091028181850.GU13808@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=mgoldish@redhat.com \
--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