From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org
Subject: Re: [KVM-AUTOTEST PATCH 0/4] KVM test: replace 'env' dict with an Env object
Date: Tue, 28 Dec 2010 13:49:30 -0200 [thread overview]
Message-ID: <1293551370.2486.11.camel@freedom> (raw)
In-Reply-To: <1293550990-10669-1-git-send-email-mgoldish@redhat.com>
On Tue, 2010-12-28 at 17:43 +0200, Michael Goldish wrote:
> This is a respin of Eduardo's patchset with small modifications.
>
> Differences from Eduardo's patches:
> - These patches don't change the module structure of the KVM test (no kvm
> package is created). We can still do that in the future if we choose to.
> - The class is named Env instead of KvmEnv.
> - It's defined in kvm_utils.py instead of a module of its own.
> - No unittests for Env. I personally don't think they're necessary, nor do I
> think anyone will bother to use them, but let me know if you disagree.
> - The __init__() method takes care of the loading if a filename is provided.
> - save() can do what _dump() did, so _dump() is unnecessary.
> - The series is a lot shorter and will hopefully be easier to review.
Hi Michael, thanks! The only thing I do not agree is with the unittest,
it's useful, specially for me when I am applying and checking the
patches, so I ask you to send the unittest Eduardo created on a future
patch. Other than that, great work!
> Michael Goldish (4):
> KVM test: introduce the Env class
> KVM test: use kvm_utils.Env wherever appropriate
> KVM test: use the new Env methods instead of the old env_* functions
> KVM test: get rid of the kvm_utils.env_* functions
>
> client/tests/kvm/kvm.py | 12 +-
> client/tests/kvm/kvm_preprocessing.py | 12 +-
> client/tests/kvm/kvm_scheduler.py | 4 +-
> client/tests/kvm/kvm_test_utils.py | 4 +-
> client/tests/kvm/kvm_utils.py | 165 +++++++++++++++--------------
> client/tests/kvm/tests/ksm_overcommit.py | 4 +-
> client/tests/kvm/tests/qemu_img.py | 6 +-
> client/tests/kvm/tests/stepmaker.py | 2 +-
> client/tests/kvm/tests/steps.py | 2 +-
> client/tests/kvm/tests/stress_boot.py | 2 +-
> client/tests/kvm/tests/unittest.py | 2 +-
> client/tests/kvm/tests/virtio_console.py | 2 +-
> 12 files changed, 111 insertions(+), 106 deletions(-)
>
prev parent reply other threads:[~2010-12-28 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 15:43 [KVM-AUTOTEST PATCH 0/4] KVM test: replace 'env' dict with an Env object Michael Goldish
2010-12-28 15:43 ` [KVM-AUTOTEST PATCH 1/4] KVM test: introduce the Env class Michael Goldish
2010-12-28 15:43 ` [KVM-AUTOTEST PATCH 2/4] KVM test: use kvm_utils.Env wherever appropriate Michael Goldish
2010-12-28 15:43 ` [KVM-AUTOTEST PATCH 3/4] KVM test: use the new Env methods instead of the old env_* functions Michael Goldish
2010-12-28 15:43 ` [KVM-AUTOTEST PATCH 4/4] KVM test: get rid of the kvm_utils.env_* functions Michael Goldish
2010-12-28 15:49 ` Lucas Meneghel Rodrigues [this message]
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=1293551370.2486.11.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox