public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: fstests@vger.kernel.org
Subject: Re: [ANNOUNCE] fstests: master branch updated to 948b1881f6ee
Date: Mon, 4 Sep 2017 16:07:36 +0800	[thread overview]
Message-ID: <20170904080736.GX27835@eguan.usersys.redhat.com> (raw)
In-Reply-To: <59ac1041.1389620a.c9918.3905@mx.google.com>

On Sun, Sep 03, 2017 at 10:22:52PM +0800, 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. Notably, fsx was fixed so that random seed could do its
> work, previously all tests ran fsx were running the same operation sequences.
> And fsstress was fixed so that it could run direct I/O on non-XFS filesystems.
> These two widely used test programs are changing there behaviors, so there're
> changes new bugs can be found, though I didn't see any in my release testing.
> Other commits are normal new tests, bug fixes and improvements.
> 
> It was a busy week last week, many patches were posted for review, 20 of them
> are reviewed & accepted in this update. Thanks a lot to who have contributed
> patches and/or helped review patches. But there're still some outstanding
> patches waiting for review, especially patches from Amir/Josef that add power
> failure test frame work using dm-log-write target. Hopefully I'll get them
> reviewed in the comming week.
> 
> Though there're many updates, I didn't see any new failures in auto group when
> running tests with 4.13-rc7 kernel and for-next branch of upstream xfsprogs. If

Sorry, this is wrong. generic/451 may fail on XFS and extN filesystems,
the fix is already reviewed in fsdevel list. And generic/452 fails with
dax mounted extN filesystems (driven by ext4 driver).

I updated my test description file but forgot to point the jobs to fetch
from the test branch of my internal fstests git repo, so I tested
against master branch which didn't contain the new commits.. I've fixed
up my test description file now.

Thanks,
Eryu

      reply	other threads:[~2017-09-04  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 14:22 [ANNOUNCE] fstests: master branch updated to 948b1881f6ee Eryu Guan
2017-09-04  8:07 ` Eryu Guan [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=20170904080736.GX27835@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    /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