From: Eric Sandeen <sandeen@sandeen.net>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: Josef Bacik <jbacik@fusionio.com>,
linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: add regression test for kernel bz 60673 V2
Date: Tue, 20 Aug 2013 08:46:23 -0500 [thread overview]
Message-ID: <5213732F.4010900@sandeen.net> (raw)
In-Reply-To: <5213338D.3000205@giantdisaster.de>
On 8/20/13 4:14 AM, Stefan Behrens wrote:
> On Mon, 19 Aug 2013 16:53:17 -0400, Josef Bacik wrote:
>> There was a problem with send trying to overwrite a file that wasn't actually
>> the same. This is a test to check this particular case where receive fails when
>> it should succeed properly. I tested this to verify it fails without my fix and
>> passes with my fix. Thanks,
>
> I tested this xfstest but for me it passes with and without the fix
> ("Btrfs: check our parent dir when doing a compare send").
is there any interesting fail-ish output in $seqres.full?
I wonder if it squawked about errors but exited w/ success.
>> $NOT_STDOUT 2>&1 can be dangerous ...
-Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: linux-btrfs@vger.kernel.org, Josef Bacik <jbacik@fusionio.com>,
xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: add regression test for kernel bz 60673 V2
Date: Tue, 20 Aug 2013 08:46:23 -0500 [thread overview]
Message-ID: <5213732F.4010900@sandeen.net> (raw)
In-Reply-To: <5213338D.3000205@giantdisaster.de>
On 8/20/13 4:14 AM, Stefan Behrens wrote:
> On Mon, 19 Aug 2013 16:53:17 -0400, Josef Bacik wrote:
>> There was a problem with send trying to overwrite a file that wasn't actually
>> the same. This is a test to check this particular case where receive fails when
>> it should succeed properly. I tested this to verify it fails without my fix and
>> passes with my fix. Thanks,
>
> I tested this xfstest but for me it passes with and without the fix
> ("Btrfs: check our parent dir when doing a compare send").
is there any interesting fail-ish output in $seqres.full?
I wonder if it squawked about errors but exited w/ success.
>> $NOT_STDOUT 2>&1 can be dangerous ...
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-20 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 20:53 [PATCH] xfstests: add regression test for kernel bz 60673 V2 Josef Bacik
2013-08-19 20:53 ` Josef Bacik
2013-08-20 9:14 ` Stefan Behrens
2013-08-20 9:14 ` Stefan Behrens
2013-08-20 13:46 ` Eric Sandeen [this message]
2013-08-20 13:46 ` Eric Sandeen
2013-08-20 13:50 ` Josef Bacik
2013-08-20 13:50 ` Josef Bacik
-- strict thread matches above, loose matches on Subject: below --
2013-10-21 17:52 Josef Bacik
2013-10-21 17:52 ` Josef Bacik
2013-10-21 17:55 ` Eric Sandeen
2013-10-21 17:55 ` Eric Sandeen
2013-10-22 21:30 ` Rich Johnston
2013-10-22 21:30 ` Rich Johnston
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=5213732F.4010900@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
--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 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.