From: kernel test robot <oliver.sang@intel.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
David Sterba <dsterba@suse.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Christian Brauner <brauner@kernel.org>,
<linux-btrfs@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [btrfs] 7d59ee54f0: xfstests.btrfs.220.fail
Date: Tue, 5 Dec 2023 14:44:29 +0800 [thread overview]
Message-ID: <202312051101.f6be0b61-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.btrfs.220.fail" on:
commit: 7d59ee54f0ef2b1bc3eece201e580b70d1bba4cb ("btrfs: remove code for inode_cache and recovery mount options")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 629a3b49f3f957e975253c54846090b8d5ed2e9b]
in testcase: xfstests
version: xfstests-x86_64-11914614-1_20231122
with following parameters:
disk: 6HDD
fs: btrfs
test: btrfs-220
compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 8G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202312051101.f6be0b61-oliver.sang@intel.com
2023-12-04 03:56:44 export TEST_DIR=/fs/sdb1
2023-12-04 03:56:44 export TEST_DEV=/dev/sdb1
2023-12-04 03:56:44 export FSTYP=btrfs
2023-12-04 03:56:44 export SCRATCH_MNT=/fs/scratch
2023-12-04 03:56:44 mkdir /fs/scratch -p
2023-12-04 03:56:44 export SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4 /dev/sdb5 /dev/sdb6"
2023-12-04 03:56:44 echo btrfs/220
2023-12-04 03:56:44 ./check btrfs/220
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 lkp-hsw-d01 6.7.0-rc3-00074-g7d59ee54f0ef #1 SMP PREEMPT_DYNAMIC Mon Dec 4 01:30:48 CST 2023
MKFS_OPTIONS -- /dev/sdb2
MOUNT_OPTIONS -- /dev/sdb2 /fs/scratch
btrfs/220 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/220.out.bad)
--- tests/btrfs/220.out 2023-11-22 02:47:17.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//btrfs/220.out.bad 2023-12-04 03:57:08.228523511 +0000
@@ -1,2 +1,4 @@
QA output created by 220
-Silence is golden
+mount: /fs/scratch: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error.
+mount -o norecovery,ro /dev/sdb2 /fs/scratch failed
+(see /lkp/benchmarks/xfstests/results//btrfs/220.full for details)
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/220.out /lkp/benchmarks/xfstests/results//btrfs/220.out.bad' to see the entire diff)
Ran: btrfs/220
Failures: btrfs/220
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231205/202312051101.f6be0b61-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-12-05 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 6:44 kernel test robot [this message]
2023-12-05 15:55 ` [linux-next:master] [btrfs] 7d59ee54f0: xfstests.btrfs.220.fail 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=202312051101.f6be0b61-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=dsterba@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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