public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	Miklos Szeredi <mszeredi@redhat.com>, Jan Kara <jack@suse.cz>,
	<linux-fsdevel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [fs]  75ead69a71: kernel-selftests.filesystems/statmount.statmount_test.fail
Date: Mon, 30 Dec 2024 14:35:49 +0800	[thread overview]
Message-ID: <202412301338.77cc6482-lkp@intel.com> (raw)



Hello,

kernel test robot noticed "kernel-selftests.filesystems/statmount.statmount_test.fail" on:

commit: 75ead69a717332efa70303fba85e1876793c74a9 ("fs: don't let statmount return empty strings")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

[test failed on linus/master      8379578b11d5e073792b5db2690faa12effce8e0]
[test failed on linux-next/master 8155b4ef3466f0e289e8fcc9e6e62f3f4dceeac2]

in testcase: kernel-selftests
version: kernel-selftests-x86_64-7503345ac5f5-1_20241208
with following parameters:

	group: filesystems



config: x86_64-dcg_x86_64_defconfig-kselftests
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (Cascade Lake) with 32G 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/202412301338.77cc6482-lkp@intel.com


TAP version 13
1..2
# timeout set to 300
# selftests: filesystems/statmount: statmount_test
# TAP version 13
# 1..15
# ok 1 listmount empty root
# ok 2 statmount zero mask
# ok 3 statmount mnt basic
# ok 4 statmount sb basic
# ok 5 statmount mount root
# ok 6 statmount mount point
# ok 7 statmount fs type
# not ok 8 unexpected mount options: 'tmpfs' != ''
# ok 9 statmount string mount root
# ok 10 statmount string mount point
# ok 11 statmount string fs type
# ok 12 statmount string mount root & all
# ok 13 statmount string mount point & all
# ok 14 statmount string fs type & all
# ok 15 listmount tree
# # Totals: pass:14 fail:1 xfail:0 xpass:0 skip:0 error:0
not ok 1 selftests: filesystems/statmount: statmount_test # exit=1



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241230/202412301338.77cc6482-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2024-12-30  6:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30  6:35 kernel test robot [this message]
2025-01-04  9:05 ` [linus:master] [fs] 75ead69a71: kernel-selftests.filesystems/statmount.statmount_test.fail Christian Brauner

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=202412301338.77cc6482-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mszeredi@redhat.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