From: David Sterba <dsterba@suse.cz>
To: kernel test robot <oliver.sang@intel.com>
Cc: Josef Bacik <josef@toxicpanda.com>,
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
Subject: Re: [linux-next:master] [btrfs] 7d59ee54f0: xfstests.btrfs.220.fail
Date: Tue, 5 Dec 2023 16:55:47 +0100 [thread overview]
Message-ID: <20231205155546.GH2751@twin.jikos.cz> (raw)
In-Reply-To: <202312051101.f6be0b61-oliver.sang@intel.com>
On Tue, Dec 05, 2023 at 02:44:29PM +0800, kernel test robot wrote:
> 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
> 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
We need an update to fstests, there are tests using the 'norecovery'
option and 'nologreplay' should be switched to 'rescue=nologreplay' too.
prev parent reply other threads:[~2023-12-05 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 6:44 [linux-next:master] [btrfs] 7d59ee54f0: xfstests.btrfs.220.fail kernel test robot
2023-12-05 15:55 ` David Sterba [this message]
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=20231205155546.GH2751@twin.jikos.cz \
--to=dsterba@suse.cz \
--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 \
--cc=oliver.sang@intel.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