From: kernel test robot <oliver.sang@intel.com>
To: David Sterba <dsterba@suse.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-btrfs@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [kdave-btrfs-devel:fix-6.7-device-scanning] b80f3ec659: xfstests.btrfs.285.fail
Date: Thu, 8 Feb 2024 17:14:20 +0800 [thread overview]
Message-ID: <202402081636.6d71afee-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.btrfs.285.fail" on:
commit: b80f3ec6592c69f88ebc74a4e16676af161e2759 ("the fix")
https://github.com/kdave/btrfs-devel.git fix-6.7-device-scanning
in testcase: xfstests
version: xfstests-x86_64-c46ca4d1-1_20240205
with following parameters:
disk: 6HDD
fs: btrfs
test: btrfs-285
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)
we noticed this patch seems not a formal patch, below detail informations just
FYI.
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/202402081636.6d71afee-oliver.sang@intel.com
2024-02-06 23:45:26 export TEST_DIR=/fs/sda1
2024-02-06 23:45:26 export TEST_DEV=/dev/sda1
2024-02-06 23:45:26 export FSTYP=btrfs
2024-02-06 23:45:26 export SCRATCH_MNT=/fs/scratch
2024-02-06 23:45:26 mkdir /fs/scratch -p
2024-02-06 23:45:26 export SCRATCH_DEV_POOL="/dev/sda2 /dev/sda3 /dev/sda4 /dev/sda5 /dev/sda6"
2024-02-06 23:45:26 echo btrfs/285
2024-02-06 23:45:26 ./check btrfs/285
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 lkp-hsw-d01 6.7.0-00001-gb80f3ec6592c #1 SMP PREEMPT_DYNAMIC Wed Feb 7 07:00:38 CST 2024
MKFS_OPTIONS -- /dev/sda2
MOUNT_OPTIONS -- /dev/sda2 /fs/scratch
btrfs/285 - output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/285.out.bad)
--- tests/btrfs/285.out 2024-02-05 17:37:40.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//btrfs/285.out.bad 2024-02-06 23:45:51.904771890 +0000
@@ -1,2 +1,7 @@
QA output created by 285
+cat: /sys/fs/btrfs/95783542-ca90-43bd-84a1-389add1ee212/allocation/data/size_classes: No such file or directory
+1c1
+<
+---
+> none 0 small 1 medium 1 large 1
Silence is golden
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/285.out /lkp/benchmarks/xfstests/results//btrfs/285.out.bad' to see the entire diff)
Ran: btrfs/285
Failures: btrfs/285
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240208/202402081636.6d71afee-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-08 9:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202402081636.6d71afee-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).