From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: fix topology test to work again
Date: Tue, 20 Apr 2010 10:36:23 -0400 [thread overview]
Message-ID: <20100420143623.GC7538@redhat.com> (raw)
In-Reply-To: <87sk6qz65k.fsf@twilight.int.mornfall.net.>
On Tue, Apr 20 2010 at 7:59am -0400,
Petr Rockai <prockai@redhat.com> wrote:
> Hi,
>
> Mike Snitzer <snitzer@redhat.com> writes:
> > Reintroduce teardown_() because t-topology-support.sh only needs a
> > subset of the full teardown() between each iteration of the topology
> > tests -- in particular the $TESTDIR must not get removed between each
> > topology test iteration.
>
> I would prefer to have prepare_scsi_debug_dev changed to drop the
> devices and re-create them when invoked for the second time than to bend
> the teardown mechanism for something it is not intended for.
I can't say I agree with you here. The previous split of teardown and
teardown_ made it possible to do what was done for the topology tests
(using a minimalist teardown to cleanup the device). I made use of the
previous teardown split to add more functionality; no different than how
any code evolves. Once code evolves we cannot just break that new
functionality when making new changes.
So I'd like to restore the topology test with the minimalist amount of
change. Once it is back to working I can look at your suggestion of how
to change prepare_scsi_debug_dev, etc.
> Also,
> teardown/teardown_ is a poor distinction and does not say much about
> intended usage. You can of course re-use parts of teardown in your
> implementation, but please name the new function(s) appropriately in
> that case.
I'll rename teardown_
Thanks,
Mike
prev parent reply other threads:[~2010-04-20 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 22:53 [PATCH] fix topology test to work again Mike Snitzer
2010-04-20 11:59 ` Petr Rockai
2010-04-20 14:36 ` Mike Snitzer [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=20100420143623.GC7538@redhat.com \
--to=snitzer@redhat.com \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.