public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: mornfall@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/test t-mirror-basic.sh t-pvmove-basic.sh ... Date: Wed, 07 Apr 2010 16:00:00 -0000 [thread overview] Message-ID: <20100407160020.8285.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: mornfall@sourceware.org 2010-04-07 16:00:19 Modified files: test : t-mirror-basic.sh t-pvmove-basic.sh t-mirror-lvconvert-usage.sh t-mirror-lvconvert.sh t-mirror-names.sh t-mirror-vgreduce-removemissing.sh Log message: Avoid spurious skips in the testsuite due to obsoleted dmsetup_has_dm_devdir_support_. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-mirror-basic.sh.diff?cvsroot=lvm2&r1=1.8&r2=1.9 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-pvmove-basic.sh.diff?cvsroot=lvm2&r1=1.7&r2=1.8 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-mirror-lvconvert-usage.sh.diff?cvsroot=lvm2&r1=1.1&r2=1.2 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-mirror-lvconvert.sh.diff?cvsroot=lvm2&r1=1.22&r2=1.23 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-mirror-names.sh.diff?cvsroot=lvm2&r1=1.5&r2=1.6 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-mirror-vgreduce-removemissing.sh.diff?cvsroot=lvm2&r1=1.8&r2=1.9 --- LVM2/test/t-mirror-basic.sh 2010/04/07 14:46:26 1.8 +++ LVM2/test/t-mirror-basic.sh 2010/04/07 16:00:19 1.9 @@ -14,8 +14,6 @@ . ./test-utils.sh -dmsetup_has_dm_devdir_support_ || exit 200 - # --------------------------------------------------------------------- # Utilities --- LVM2/test/t-pvmove-basic.sh 2010/04/07 14:46:26 1.7 +++ LVM2/test/t-pvmove-basic.sh 2010/04/07 16:00:19 1.8 @@ -14,8 +14,6 @@ . ./test-utils.sh -dmsetup_has_dm_devdir_support_ || exit 200 - # --------------------------------------------------------------------- # Utilities --- LVM2/test/t-mirror-lvconvert-usage.sh 2008/11/11 15:29:24 1.1 +++ LVM2/test/t-mirror-lvconvert-usage.sh 2010/04/07 16:00:19 1.2 @@ -10,11 +10,8 @@ . ./test-utils.sh -dmsetup_has_dm_devdir_support_ || exit 200 - aux prepare_vg 5 - lv_is_on_() { local lv=$1 #allready vg/lv shift 1 --- LVM2/test/t-mirror-lvconvert.sh 2010/04/06 23:04:45 1.22 +++ LVM2/test/t-mirror-lvconvert.sh 2010/04/07 16:00:19 1.23 @@ -11,8 +11,6 @@ . ./test-utils.sh -dmsetup_has_dm_devdir_support_ || exit 200 - mimages_are_redundant_ () { local vg=$1 --- LVM2/test/t-mirror-names.sh 2010/01/22 21:59:42 1.5 +++ LVM2/test/t-mirror-names.sh 2010/04/07 16:00:19 1.6 @@ -14,8 +14,6 @@ . ./test-utils.sh -dmsetup_has_dm_devdir_support_ || exit 200 - # --------------------------------------------------------------------- # Utilities --- LVM2/test/t-mirror-vgreduce-removemissing.sh 2010/03/31 03:56:25 1.8 +++ LVM2/test/t-mirror-vgreduce-removemissing.sh 2010/04/07 16:00:19 1.9 @@ -13,8 +13,6 @@ . ./test-utils.sh -dmsetup_has_dm_devdir_support_ || exit 200 - lv_is_on_ () { local lv=$vg/$1
reply other threads:[~2010-04-07 16:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100407160020.8285.qmail@sourceware.org \ --to=mornfall@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).