public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/test t-mdata-strings.sh Date: Sun, 23 Oct 2011 15:39:00 -0000 [thread overview] Message-ID: <20111023153908.22826.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-10-23 15:39:08 Modified files: test : t-mdata-strings.sh Log message: Expect failure with real /dev dir As udev is for now incapable to create such devices turn this test error into warning. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-mdata-strings.sh.diff?cvsroot=lvm2&r1=1.6&r2=1.7 --- LVM2/test/t-mdata-strings.sh 2011/01/05 00:16:20 1.6 +++ LVM2/test/t-mdata-strings.sh 2011/10/23 15:39:08 1.7 @@ -1,5 +1,5 @@ #!/bin/sh -# Copyright (C) 2008 Red Hat, Inc. All rights reserved. +# Copyright (C) 2008-2011 Red Hat, Inc. All rights reserved. # # This copyrighted material is made available to anyone wishing to use, # modify, copy, or redistribute it subject to the terms and conditions @@ -13,8 +13,9 @@ . lib/test -aux prepare_devs 1 +aux prepare_devs 2 +# for udev impossible to create pv_ugly="__\"!@#\$%^&*,()|@||'\\\"__pv1" # 'set up temp files, loopback devices' @@ -23,9 +24,11 @@ dev1=$(dirname "$dev1")/$PREFIX$pv_ugly # 'pvcreate, vgcreate on filename with backslashed chars' -pvcreate "$dev1" -vgcreate $vg "$dev1" - +created=$dev1 +# when used with real udev without fallback, it will fail here +pvcreate "$dev1" || created=$dev2 +pvs | should grep $dev1 +vgcreate $vg "$created" # 'no parse errors and VG really exists' vgs 2>err not grep "Parse error" err;
next reply other threads:[~2011-10-23 15:39 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-23 15:39 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-10-23 21:24 zkabelac 2009-04-03 14:23 wysochanski 2009-03-31 17:30 mbroz 2008-03-12 17:34 mbroz
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=20111023153908.22826.qmail@sourceware.org \ --to=zkabelac@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).