public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Huff <dhuff@redhat.com>
To: Uri Lublin <uril@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm_autotest: dynamically load tests
Date: Wed, 27 May 2009 08:14:08 -0400	[thread overview]
Message-ID: <4A1D2E90.4030602@redhat.com> (raw)
In-Reply-To: <4A1D281A.7040401@redhat.com>

Uri Lublin wrote:
> Hi David,
> 
> I'm not sure this patch-set makes development much easier, as it only
> saves adding one line (entry) in test_routines table, but is less
> flexible (e.g. force file-name and function-name of test routines).
> 
> Moving the test to a separate kvm_tests directory can be done without
> dynamic load of the tests.
> 
> I don't have strong feelings about it though.
> 
> What others think ?
> 
> Thanks,
>     Uri.


Uri,

Thanks for the feedback, Lucas and I had a brief discussion about this
last week so I just wanted to repost what I already had just as a
starting point for a discussion on this topic, I know my patches are rough.

Our thinking is that it would be nice to be able to drop new tests in to
a kvm_test dir, modify the config file, and not have to "update" the
kvm_auottest or autotest binarys.

However I would also like to hear others opinions on this...

-D

  reply	other threads:[~2009-05-27 12:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 21:48 kvm_autotest: dynamically load tests David Huff
2009-04-28 21:48 ` [PATCH] Modified kvm_runtest_2.py to look for tests in kvm_tests/ David Huff
2009-05-27 11:58   ` Uri Lublin
2009-04-28 21:48 ` [PATCH] Added "stock" or existing test to ./kvm_tests/ David Huff
2009-04-28 21:48 ` [PATCH] removed old kvm_test.py, tests now in seprate subdir David Huff
2009-05-27 11:46 ` kvm_autotest: dynamically load tests Uri Lublin
2009-05-27 12:14   ` David Huff [this message]
2009-05-27 17:00     ` sudhir kumar

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=4A1D2E90.4030602@redhat.com \
    --to=dhuff@redhat.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