public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/5] xfstests: various fixes
Date: Wed,  1 May 2013 18:31:58 +1000	[thread overview]
Message-ID: <1367397123-2530-1-git-send-email-david@fromorbit.com> (raw)

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.

Cheers,

Dave.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-05-01  8:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01  8:31 Dave Chinner [this message]
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 ` [PATCH 0/5] xfstests: various fixes Dave Chinner
2013-05-03 14:32   ` 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=1367397123-2530-1-git-send-email-david@fromorbit.com \
    --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