From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eryu Guan <eguan@linux.alibaba.com>
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>,
Eryu Guan <guaneryu@gmail.com>,
fstests@vger.kernel.org
Subject: Re: [ANNOUNCE] fstests: master branch updated to 0ad1c034838d
Date: Mon, 4 Jan 2021 14:20:35 -0800 [thread overview]
Message-ID: <20210104222035.GC6919@magnolia> (raw)
In-Reply-To: <20201221030702.GS80581@e18g06458.et15sqa>
On Mon, Dec 21, 2020 at 11:07:02AM +0800, Eryu Guan wrote:
> On Mon, Dec 21, 2020 at 09:02:02AM +0800, Xiao Yang wrote:
> > On 2020/12/21 0:55, Eryu Guan wrote:
> > > Hi all,
> > >
> > > The master branch of the xfstests repository at:
> > >
> > > git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
> > >
> > > have just been updated. As usual, this update contains some new tests and
> > > various bug fixes and improvements.
> > >
> > > New btrfs tests btrfs/154 and btrfs/227 all currently fail with latest kernel.
> > > And xfs/513 has been updated to catch a xfs bug, but it should pass with latest
> > > kenrel.
> > >
> > > Also, unionmount tests has been improved to run with custom overlay mount
> > > options by assigning $OVERLAY_MOUNT_OPTIONS to UNIONMOUNT_MNTOPTIONS. You need
> > > to update your local unionmount tests to latest to contain commit 95be14e
> > > ("Allow user provided options with or without -o")
> > >
> > > Thanks,
> > > Eryu
> > >
> > > The new head of the master branch is commit:
> > >
> > > 0ad1c034838d overlay: run unionmount tests with custom overlay mount options
> > >
> > > New commits:
> > >
> > > Amir Goldstein (1):
> > > [0ad1c034838d] overlay: run unionmount tests with custom overlay mount options
> > >
> > > Brian Foster (1):
> > > [62cf7ce77f4f] generic/563: use a loop device to avoid partition incompatibility
> > >
> > > Eric Biggers (1):
> > > [a225507009a3] generic: test for creating duplicate filenames in encrypted dir
> > >
> > > Feiyu Zhu (1):
> > > [0c5013c565b7] src/t_enospc.c: Fix an error for the loop initialization declaration
> > >
> > > Filipe Manana (1):
> > > [eabfcdfe9084] btrfs: test incremental send after removing a directory and all its files
> > >
> > > Kaixu Xia (1):
> > > [c2dd12732f31] xfs/513: fix the regression caused by mount option uqnoenforce
> > >
> > > Nikolay Borisov (1):
> > > [2a7406efecc2] btrfs: Update btrfs/215
> > >
> > > Ritesh Harjani (1):
> > > [72dc169b442e] generic: Add test to check for mounting a huge sparse dm device
> > >
> > > Su Yue (1):
> > > [a633d252e3c4] shared/032: add options for jffs2
> > >
> > > Xiao Yang (1):
> > > [90d76997831e] src/multi_open_unlink: Stop using attr_set
> > Hi Eryu,
> >
> > Only applying above patch broke the building of xfstests. :-)
> > See my explanation on the original patch set.
>
> Thanks for the heads-up! That's weird, I didn't see compile error in my
> testing.. Will look into that.
Yes, this seems to have regressed in the last update in exactly the way
that Xiao Yang said in
https://lore.kernel.org/fstests/5FDFF2A4.6080909@cn.fujitsu.com/T/#m10968fc738f98815692bad1dee269071654255a0
Applying the dmiperf removal is definitely one way to fix it.
--D
> Thanks,
> Eryu
prev parent reply other threads:[~2021-01-04 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 16:55 [ANNOUNCE] fstests: master branch updated to 0ad1c034838d Eryu Guan
2020-12-21 1:02 ` Xiao Yang
2020-12-21 3:07 ` Eryu Guan
2021-01-04 22:20 ` Darrick J. Wong [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=20210104222035.GC6919@magnolia \
--to=darrick.wong@oracle.com \
--cc=eguan@linux.alibaba.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=yangx.jy@cn.fujitsu.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