From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfstests xfs/293 failure with current xfstests
Date: Fri, 29 Jan 2016 12:37:40 -0800 [thread overview]
Message-ID: <20160129203740.GG20038@birch.djwong.org> (raw)
In-Reply-To: <20160129192145.GC5224@linux.intel.com>
On Fri, Jan 29, 2016 at 12:21:45PM -0700, Ross Zwisler wrote:
> It looks like the current version of xfsprogs (v4.3.0) has an inconsistency
> between its documentation and implementation that is making the xfstest
> xfs/293 fail:
>
> ./check xfs/293
> FSTYP -- xfs (debug)
> PLATFORM -- Linux/x86_64 lorwyn 4.5.0-rc1
> MKFS_OPTIONS -- -f -bsize=4096 /dev/pmem0p2
> MOUNT_OPTIONS -- -o dax -o context=system_u:object_r:nfs_t:s0 /dev/pmem0p2 /mnt/xfstests_scratch
>
> xfs/293 - output mismatch (see /root/xfstests/results//xfs/293.out.bad)
> --- tests/xfs/293.out 2015-10-02 10:19:36.836796097 -0600
> +++ /root/xfstests/results//xfs/293.out.bad 2016-01-29 10:41:25.530512911 -0700
> @@ -1,2 +1,4 @@
> QA output created by 293
> Silence is golden
> +help not documented in the xfs_io manpage
> +zero not documented in the xfs_io manpage
> ...
> (Run 'diff -u tests/xfs/293.out /root/xfstests/results//xfs/293.out.bad' to see the entire diff)
> Ran: xfs/293
> Failures: xfs/293
> Failed 1 of 1 tests
>
> "help" and "zero" are indeed options in xfs_io, but aren't listed in the man
> page.
Commit 270dae6c0b41d855729fec73f94f33665bd36349 in xfsprogs for-next fixes
this.
--D
>
> Thanks,
> - Ross
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-01-29 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 19:21 xfstests xfs/293 failure with current xfstests Ross Zwisler
2016-01-29 20:37 ` Darrick J. Wong [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=20160129203740.GG20038@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=ross.zwisler@linux.intel.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