From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Yolkfull Chow <yzhou@redhat.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org,
Lawrence Lim <llim@redhat.com>,
Michael Goldish <mgoldish@redhat.com>
Subject: Re: [Autotest] [Autotest PATCH] KVM-test: Add a subtest image_copy
Date: Wed, 27 Jan 2010 09:11:56 -0200 [thread overview]
Message-ID: <1264590716.2621.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20100127034308.GA2301@aFu.nay.redhat.com>
On Wed, 2010-01-27 at 11:43 +0800, Yolkfull Chow wrote:
> On Tue, Jan 26, 2010 at 02:04:09PM -0200, Lucas Meneghel Rodrigues wrote:
> > Yolkfull, I am copying Michael and Lawrence on the e-mail so they can
> > comment on the points I am going to present.
>
> Lucas, firstly thank you very much for addressing your viewpoints and the
> coding/logical suggestions. Most of them are reasonable and appreciated
> except that I also have an improvidence about point 3):
>
> Your idea on executing image_copy as a backup of unattended_install is good.
> But I think we could also seperate 'unattended_install' from test set of
> "functional testing" and encapsulate it into "Installation testing" set.
> In this way the following functional test cases will not be affected by
> failed installation tests.
>
> What do you think about this?
I believe this could be implemented by simply removing the dependency.
However, if *no* install test succeed whatsoever, then we don't have any
way to perform the subsequent tests. So I don't know how to implement
this idea.
Please explain me how that encapsulation would work.
next prev parent reply other threads:[~2010-01-27 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 3:32 [Autotest PATCH] KVM-test: Add a subtest image_copy Yolkfull Chow
2010-01-26 16:04 ` Lucas Meneghel Rodrigues
2010-01-27 3:43 ` Yolkfull Chow
2010-01-27 11:11 ` Lucas Meneghel Rodrigues [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-04 9:30 Yolkfull Chow
2010-01-04 14:52 ` [Autotest] " Amos Kong
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=1264590716.2621.2.camel@localhost.localdomain \
--to=lmr@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=llim@redhat.com \
--cc=mgoldish@redhat.com \
--cc=yzhou@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