From: Christoph Hellwig <hch@infradead.org>
To: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: new xfs/103 failure
Date: Sat, 12 Nov 2016 08:32:48 -0800 [thread overview]
Message-ID: <20161112163248.GA24737@infradead.org> (raw)
After recently upgrading the xfs and xfsprogs trees I get reproducible
xfs/103 failures because the n flags is not reported. Does anyone else
see this?
root@testvm:~/xfstests# diff -u tests/xfs/103.out
/root/xfstests/results//xfs/103
--- tests/xfs/103.outs# 2016-03-29 13:59:30.451720622
+0000stests/results//xfs/10
+++ /root/xfstests/results//xfs/103.out.bad 2016-11-12
16:30:37.032780388 +0000
@@ -3,7 +3,7 @@
*** mount
*** testing nosymlinks directories
*** setting nosymlinks bit
---n-- SCRATCH_MNT/nosymlink
+----- SCRATCH_MNT/nosymlink
ln: creating symbolic link 'SCRATCH_MNT/nosymlink/target': Operation not permitted
*** 1st listing...
SCRATCH_MNT
next reply other threads:[~2016-11-12 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 16:32 Christoph Hellwig [this message]
2016-11-12 17:00 ` new xfs/103 failure Darrick J. Wong
2016-11-12 18:31 ` Eryu Guan
2016-11-13 12:12 ` Christoph Hellwig
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=20161112163248.GA24737@infradead.org \
--to=hch@infradead.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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