From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [kdave-btrfs-devel:dev/guilherme/temp-fsid-v4] [btrfs] 479361d32b: xfstests.btrfs.185.fail
Date: Tue, 31 Oct 2023 12:22:34 +0100 [thread overview]
Message-ID: <20231031112234.GA11264@suse.cz> (raw)
In-Reply-To: <f291309a-71d3-484b-a876-99382a61363d@oracle.com>
On Tue, Oct 31, 2023 at 05:23:18PM +0800, Anand Jain wrote:
> Thanks for the report.
>
> > +cloned device scan should fail
>
> Your fstests is missing the following commit:
> 1348ed0e256a ("fstests: btrfs/185 update for single device pseudo
> device-scan")
> Pls upgrade.
Yes for the fstests upgrade, but the tested branch is some old snapshot
of the temp_fsid feature, I don't even have the branch anywhere.
prev parent reply other threads:[~2023-10-31 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 7:46 [kdave-btrfs-devel:dev/guilherme/temp-fsid-v4] [btrfs] 479361d32b: xfstests.btrfs.185.fail kernel test robot
2023-10-31 9:23 ` Anand Jain
2023-10-31 11:22 ` 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=20231031112234.GA11264@suse.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.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