public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Mark Tinguely <tinguely@sgi.com>
Cc: Brian Foster <bfoster@redhat.com>, xfs@oss.sgi.com
Subject: Re: [PATCH v2] xfsprogs/io: add readdir command
Date: Thu, 08 Aug 2013 15:39:13 -0500	[thread overview]
Message-ID: <520401F1.3010609@sandeen.net> (raw)
In-Reply-To: <5203A5B7.4020102@sgi.com>

On 8/8/13 9:05 AM, Mark Tinguely wrote:

> Could we get a little info for the xfs_io man page?
> 

Yup, otherwise xfs/293 fails :)


# ./check xfs/293
FSTYP         -- xfs (non-debug)
PLATFORM      -- Linux/x86_64 bp-05 3.11.0-rc1+
MKFS_OPTIONS  -- -f -bsize=4096 /dev/sdb2
MOUNT_OPTIONS -- -o context=system_u:object_r:nfs_t:s0 /dev/sdb2 /mnt/scratch

xfs/293 10s ... - output mismatch (see /mnt/test2/git/xfstests/results/xfs/293.out.bad)
    --- tests/xfs/293.out	2013-03-27 12:57:49.318520102 -0500
    +++ /mnt/test2/git/xfstests/results/xfs/293.out.bad	2013-08-08 15:38:30.881221070 -0500
    @@ -1,2 +1,3 @@
     QA output created by 293
     Silence is golden
    +readdir not documented in the xfs_io manpage
     ...
     (Run 'diff -u tests/xfs/293.out /mnt/test2/git/xfstests/results/xfs/293.out.bad' to see the entire diff)
Ran: xfs/293
Failures: xfs/293
Failed 1 of 1 tests


/me pats self on back ;)

-Eric

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

      parent reply	other threads:[~2013-08-08 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 12:44 [PATCH v2] xfsprogs/io: add readdir command Brian Foster
2013-08-08 14:05 ` Mark Tinguely
2013-08-08 17:38   ` Brian Foster
2013-08-08 18:36     ` Mark Tinguely
2013-08-08 20:39   ` Eric Sandeen [this message]

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=520401F1.3010609@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=bfoster@redhat.com \
    --cc=tinguely@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