From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH 0/5] xfstests: various fixes
Date: Wed, 1 May 2013 19:31:39 +1000 [thread overview]
Message-ID: <20130501093139.GN10481@dastard> (raw)
In-Reply-To: <1367397123-2530-1-git-send-email-david@fromorbit.com>
On Wed, May 01, 2013 at 06:31:58PM +1000, Dave Chinner wrote:
> Hi folks,
>
> These are various fixes for xfstests.
>
> The first patch is an infrastructure regression fix, resulting from
> the patchset that split up the tests into subdirectories. It also
> moves all the check.* output files to the result directory rather
> than leaving them in the root directory of xfstests.
>
> The second is a bunch of changes to generic/310 that should have
> been done in the review cycle. It now works reliably for me.
>
> The last 3 patches fix bugs in tests that result in files being left
> in the root directory of xfstests.
FWIW, with the V2 xfsprogs kernel sync tarball I've posted and these
fixes to xfstests, I'm down to only 3 failures in xfstests for 4k
block size filesystem tests:
Failures: generic/233 shared/298 xfs/296
generic/233 appears to be a small quota accounting mismatch,
probably related to speculative preallocation. Not a major issue.
shared/298 is failing due to the ENOSPC problem Eric posted patches
to fix. Test bug.
xfs/296 is failing due to an unresolved xfsdump issue w.r.t
restoring security attributes. Unresolved.
So, I'm much happier now about the state of xfsprogs and xfstests
than I was this morning. I'll be happier still when I fix the fsx
failures on 512 byte block size filesystems, because that will bring
my 512 byte block size filesystem tests to close to the same level.
That's for tomorrow, though.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-01 9:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 8:31 [PATCH 0/5] xfstests: various fixes Dave Chinner
2013-05-01 8:31 ` [PATCH 1/5] xfstests: fix last test runtime output Dave Chinner
2013-05-03 14:24 ` Rich Johnston
2013-05-01 8:32 ` [PATCH 2/5] xfstests: 310 fails with existing directory error Dave Chinner
2013-05-03 14:25 ` Rich Johnston
2013-05-01 8:32 ` [PATCH 3/5] xfstests: filter EA paths used by dump Dave Chinner
2013-05-03 14:25 ` Rich Johnston
2013-05-01 8:32 ` [PATCH 4/5] xfstests: fix incorrect redirect in generic/232 Dave Chinner
2013-05-03 14:26 ` Rich Johnston
2013-05-01 8:32 ` [PATCH 5/5] xfstests: fix broken redirects in generic/131 Dave Chinner
2013-05-03 14:26 ` Rich Johnston
2013-05-01 9:31 ` Dave Chinner [this message]
2013-05-03 14:32 ` [PATCH 0/5] xfstests: various fixes 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=20130501093139.GN10481@dastard \
--to=david@fromorbit.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