From: Koen De Wit <koen.de.wit@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
xfs@oss.sgi.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] xfstests: btrfs/316: cross-subvolume sparse copy
Date: Tue, 02 Jul 2013 16:27:07 +0200 [thread overview]
Message-ID: <51D2E33B.1080402@oracle.com> (raw)
In-Reply-To: <20130702101539.GC14996@dastard>
Dave,
Thanks for the review. I will clean up the commit message and do a full mail-to-myself-and-test-patch round trip to avoid errors like the wrong test numbers in the golden output. I'm sorry for this.
About cutting out file names from the output. I did this in the first version of the patch:
md5sum $TESTDIR1/$F | $AWK_PROG 'END {print $1}'
but Eric Sandeen suggested to include them in order to provide more context in the output. (See http://oss.sgi.com/archives/xfs/2013-03/msg00231.html and http://oss.sgi.com/archives/xfs/2013-03/msg00220.html) That sounds like a good idea to me, it makes debugging failures easier. Whose opinion should I follow?
Koen.
On 07/02/2013 12:15 PM, Dave Chinner wrote:
> On Tue, Jul 02, 2013 at 11:27:51AM +0200, Koen De Wit wrote:
>> This testscript creates reflinks to files on different subvolumes, overwrites the original files and reflinks, and moves reflinked files between subvolumes.
>>
>> Originally submitted as testcase 302, changes are made based on comments from Eric: http://oss.sgi.com/archives/xfs/2013-03/msg00231.html
>> Two new common/rc functions used in this script (_require_cp_reflink and _verify_reflink) have been submitted recently: http://oss.sgi.com/archives/xfs/2013-05/msg00745.html
>> Thanks to Eric Sandeen and Dave Chinner for the reviews.
>>
>> Version 3: fixing wrapped patch.
>
> Needs a proper commit message - wrap it at 72 columns, change log
> should be placed below the --- devider, not be part of hte commit
> message.
>
> Test numbers do not need to be unique across all test directories,
> just unique within the tests/btrfs directory.
>
>> +
>> +_checksum_files() {
>> + for F in file1 file2 file3
>> + do
>> + for D in $TESTDIR1 $SCRATCH_MNT $SUBVOL2
>> + do
>> + md5sum $D/$F | _filter_test_dir | _filter_scratch
>
> Just cut the file name out. No need for filtering at that point...
>
>> + done
>> + done
>> +}
>> +
>> +TESTDIR1=$TEST_DIR/test-$seq-1
>> +TESTDIR2=$TEST_DIR/test-$seq-2
>> +SUBVOL1=$TEST_DIR/subvol-$seq-1
>> +SUBVOL2=$TEST_DIR/subvol-$seq-2
>
> ....-316-.....
>
>> +Verify the file contents:
>> +e09c80c42fda55f9d992e59ca6b3307d TEST_DIR/test-302-1/file1
>
> which means the golden output is broken, despite the filtering
>
> You should test your patches before posting ;)
>
> FWIW, this is why you should simply cut the filename completely out
> like we do elsewhere....
>
> Cheers,
>
> Dave.
next prev parent reply other threads:[~2013-07-02 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 9:27 [PATCH v3] xfstests: btrfs/316: cross-subvolume sparse copy Koen De Wit
2013-07-02 10:15 ` Dave Chinner
2013-07-02 14:27 ` Koen De Wit [this message]
2013-07-02 15:51 ` Eric Sandeen
2013-07-03 6:37 ` Dave Chinner
2013-07-03 10:02 ` Koen De Wit
2013-07-03 10:17 ` Dave Chinner
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=51D2E33B.1080402@oracle.com \
--to=koen.de.wit@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).