From: David Sterba <dsterba@suse.cz>
To: kernel test robot <oliver.sang@intel.com>
Cc: Arthur Williams <taaparthur@gmail.com>,
0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: [fs] 87f196bed3: xfstests.generic.157.fail
Date: Thu, 1 Jul 2021 11:48:13 +0200 [thread overview]
Message-ID: <20210701094813.GV2610@twin.jikos.cz> (raw)
In-Reply-To: <20210701021928.GB21279@xsang-OptiPlex-9020>
On Thu, Jul 01, 2021 at 10:19:28AM +0800, kernel test robot wrote:
> generic/156 [not run] xfs_io funshare failed (old kernel/wrong fs?)
> generic/157 - output mismatch (see /lkp/benchmarks/xfstests/results//generic/157.out.bad)
> --- tests/generic/157.out 2021-06-28 16:41:45.000000000 +0000
> +++ /lkp/benchmarks/xfstests/results//generic/157.out.bad 2021-12-01 20:44:35.949001218 +0000
> @@ -14,7 +14,7 @@
> Try to reflink a device
> XFS_IOC_CLONE_RANGE: Invalid argument
> Try to reflink to a dir
> -TEST_DIR/test-157/dir1: Is a directory
> +XFS_IOC_CLONE_RANGE: Is a directory
The sense of the error hasn't changed but the output is different so
it needs some filter again.
> Try to reflink to a device
> XFS_IOC_CLONE_RANGE: Invalid argument
> ...
> (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/157.out /lkp/benchmarks/xfstests/results//generic/157.out.bad' to see the entire diff)
> generic/158 - output mismatch (see /lkp/benchmarks/xfstests/results//generic/158.out.bad)
> --- tests/generic/158.out 2021-06-28 16:41:45.000000000 +0000
> +++ /lkp/benchmarks/xfstests/results//generic/158.out.bad 2021-12-01 20:44:37.783001265 +0000
> @@ -18,7 +18,7 @@
> Try to dedupe a device
> XFS_IOC_FILE_EXTENT_SAME: Invalid argument
> Try to dedupe to a dir
> -TEST_DIR/test-158/dir1: Is a directory
> +XFS_IOC_FILE_EXTENT_SAME: Is a directory
Same.
> Try to dedupe to a device
> XFS_IOC_FILE_EXTENT_SAME: Invalid argument
> ...
> (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/158.out /lkp/benchmarks/xfstests/results//generic/158.out.bad' to see the entire diff)
WARNING: multiple messages have this Message-ID (diff)
From: David Sterba <dsterba@suse.cz>
To: lkp@lists.01.org
Subject: Re: [fs] 87f196bed3: xfstests.generic.157.fail
Date: Thu, 01 Jul 2021 11:48:13 +0200 [thread overview]
Message-ID: <20210701094813.GV2610@twin.jikos.cz> (raw)
In-Reply-To: <20210701021928.GB21279@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]
On Thu, Jul 01, 2021 at 10:19:28AM +0800, kernel test robot wrote:
> generic/156 [not run] xfs_io funshare failed (old kernel/wrong fs?)
> generic/157 - output mismatch (see /lkp/benchmarks/xfstests/results//generic/157.out.bad)
> --- tests/generic/157.out 2021-06-28 16:41:45.000000000 +0000
> +++ /lkp/benchmarks/xfstests/results//generic/157.out.bad 2021-12-01 20:44:35.949001218 +0000
> @@ -14,7 +14,7 @@
> Try to reflink a device
> XFS_IOC_CLONE_RANGE: Invalid argument
> Try to reflink to a dir
> -TEST_DIR/test-157/dir1: Is a directory
> +XFS_IOC_CLONE_RANGE: Is a directory
The sense of the error hasn't changed but the output is different so
it needs some filter again.
> Try to reflink to a device
> XFS_IOC_CLONE_RANGE: Invalid argument
> ...
> (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/157.out /lkp/benchmarks/xfstests/results//generic/157.out.bad' to see the entire diff)
> generic/158 - output mismatch (see /lkp/benchmarks/xfstests/results//generic/158.out.bad)
> --- tests/generic/158.out 2021-06-28 16:41:45.000000000 +0000
> +++ /lkp/benchmarks/xfstests/results//generic/158.out.bad 2021-12-01 20:44:37.783001265 +0000
> @@ -18,7 +18,7 @@
> Try to dedupe a device
> XFS_IOC_FILE_EXTENT_SAME: Invalid argument
> Try to dedupe to a dir
> -TEST_DIR/test-158/dir1: Is a directory
> +XFS_IOC_FILE_EXTENT_SAME: Is a directory
Same.
> Try to dedupe to a device
> XFS_IOC_FILE_EXTENT_SAME: Invalid argument
> ...
> (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/158.out /lkp/benchmarks/xfstests/results//generic/158.out.bad' to see the entire diff)
next prev parent reply other threads:[~2021-07-01 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 11:01 [PATCH] fs: Allow open with O_CREAT to succeed if existing dir is specified Arthur Williams
2021-06-19 12:42 ` Al Viro
2021-06-19 14:27 ` Matthew Wilcox
[not found] ` <CAJ6D+Z96OWwZMzickLP3PtUnsJhSfZqTnLrmk4-t5iNUid=N=Q@mail.gmail.com>
2021-06-19 15:09 ` Al Viro
2021-07-01 2:19 ` [fs] 87f196bed3: xfstests.generic.157.fail kernel test robot
2021-07-01 2:19 ` kernel test robot
2021-07-01 9:48 ` David Sterba [this message]
2021-07-01 9:48 ` David Sterba
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=20210701094813.GV2610@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=taaparthur@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.