From: Christoph Hellwig <hch@infradead.org>
To: Timothy Shimmin <tes@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: review: xfstests/016 change
Date: Mon, 5 May 2008 01:54:46 -0400 [thread overview]
Message-ID: <20080505055446.GB15609@infradead.org> (raw)
In-Reply-To: <481E7F17.5090601@sgi.com>
On Mon, May 05, 2008 at 01:29:27PM +1000, Timothy Shimmin wrote:
> Hi there,
>
> xfstests/016 has been failing for a while in many cases.
> It was relying on the log traffic for create/rm to be unaltered
> in XFS over the life of XFS.
> Its initial purpose was to test out the writing of the log around
> wrapping and checking that as we wrapped we didn't corrupt any data
> after the end of the log.
>
> The patch is to modify xfstest, 016, to take a sampling of the log traffic
> to guestimate how many ops are needed to get to the end of the log,
> instead of hard-coding in how many ops are expected to get there.
I get four rejects out of four hunk when trying to apply this patch,
looks like whitespace-damage.
next prev parent reply other threads:[~2008-05-05 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 3:29 review: xfstests/016 change Timothy Shimmin
2008-05-05 5:54 ` Christoph Hellwig [this message]
2008-05-05 6:19 ` Timothy Shimmin
2008-05-05 18:31 ` Christoph Hellwig
2008-05-06 1:29 ` Timothy Shimmin
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=20080505055446.GB15609@infradead.org \
--to=hch@infradead.org \
--cc=tes@sgi.com \
--cc=xfs-dev@sgi.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