From: kernel test robot <oliver.sang@intel.com>
To: Boris Burkov <boris@bur.io>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
David Sterba <dsterba@suse.com>, Qu Wenruo <wqu@suse.com>,
<linux-btrfs@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [kdave-btrfs-devel:dev/fixinclude-to-send] [btrfs] a9e57fc34c: xfstests.btrfs.303.fail
Date: Thu, 8 Feb 2024 16:32:13 +0800 [thread overview]
Message-ID: <202402081613.c4636ea9-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.btrfs.303.fail" on:
commit: a9e57fc34cc3c8a898d742086a94a0f66c683bee ("btrfs: forbid creating subvol qgroups")
https://github.com/kdave/btrfs-devel.git dev/fixinclude-to-send
in testcase: xfstests
version: xfstests-x86_64-c46ca4d1-1_20240205
with following parameters:
disk: 6HDD
fs: btrfs
test: btrfs-group-30
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/202402081613.c4636ea9-oliver.sang@intel.com
2024-02-06 17:08:46 export TEST_DIR=/fs/sdb1
2024-02-06 17:08:46 export TEST_DEV=/dev/sdb1
2024-02-06 17:08:46 export FSTYP=btrfs
2024-02-06 17:08:46 export SCRATCH_MNT=/fs/scratch
2024-02-06 17:08:46 mkdir /fs/scratch -p
2024-02-06 17:08:46 export SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4 /dev/sdb5 /dev/sdb6"
2024-02-06 17:08:46 sed "s:^:btrfs/:" //lkp/benchmarks/xfstests/tests/btrfs-group-30
2024-02-06 17:08:46 ./check btrfs/300 btrfs/301 btrfs/302 btrfs/303 btrfs/304 btrfs/305 btrfs/306 btrfs/307 btrfs/308 btrfs/309
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 lkp-hsw-d01 6.8.0-rc2-00014-ga9e57fc34cc3 #1 SMP PREEMPT_DYNAMIC Tue Feb 6 21:49:37 CST 2024
MKFS_OPTIONS -- /dev/sdb2
MOUNT_OPTIONS -- /dev/sdb2 /fs/scratch
btrfs/300 [not run] unshare --keep-caps --map-auto --map-root-user: command not found, should be in util-linux
btrfs/301 [not run] simple quotas not available
btrfs/302 13s
btrfs/303 - output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/303.out.bad)
--- tests/btrfs/303.out 2024-02-05 17:37:40.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//btrfs/303.out.bad 2024-02-06 17:09:21.788971907 +0000
@@ -1,2 +1,3 @@
QA output created by 303
+ERROR: unable to create quota group: Invalid argument
Silence is golden
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/303.out /lkp/benchmarks/xfstests/results//btrfs/303.out.bad' to see the entire diff)
...
Failures: btrfs/303
Failed 1 of 10 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240208/202402081613.c4636ea9-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-02-08 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 8:32 kernel test robot [this message]
2024-02-08 9:32 ` [kdave-btrfs-devel:dev/fixinclude-to-send] [btrfs] a9e57fc34c: xfstests.btrfs.303.fail Qu Wenruo
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=202402081613.c4636ea9-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=boris@bur.io \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=wqu@suse.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).