From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 80ec2dd71ceb
Date: Sun, 19 Nov 2017 19:27:54 +0800 [thread overview]
Message-ID: <5a116ac0.0b40650a.d1424.32e9@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2706 bytes --]
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. This is a normal "new test and random fixes &
improvements" update. The new tests are two for generic and one for btrfs, and
one notable change is that _check_dmesg starts to fail if UBSAN complains.
New failures I've noticed in this update:
- generic/468 fails on ext4, I think that's an ext4 bug and sent a patch for it
- generic/469 fails on XFS if you're using v4.14 kernel, latest kernel passes
- btrfs/154 fails on btrfs with latest upstream kernel
Thanks,
Eryu
The new head of the master branch is commit:
80ec2dd71ceb generic: test zero page cache beyond new EOF on truncate down
New commits:
Anand Jain (1):
[742facac0d33] btrfs: test for device dynamic rescan
Chandan Rajendra (1):
[9edb6cd35d13] src/t_dir_type.c: Use strtoul() instead of atoll()
Chao Yu (1):
[eb48c305021f] generic: add testcase to test fallocate & f{data,}sync
Darrick J. Wong (5):
[01140c76e485] common/fuzzy: if the fuzz verb is random, keep fuzzing until we get a new value
[90eaf3d7447c] generic/45[34]: add emoji to the unusual fs naming test
[b5b3e2220ace] aio-dio-append-write-read-race: abort if we encounter syscall errors
[dca116873788] common/rc: check dmesg for UBSAN errors
[6ee333cec470] xfs/122: don't check xfs_iext_cursor
Eryu Guan (1):
[80ec2dd71ceb] generic: test zero page cache beyond new EOF on truncate down
Liu Bo (1):
[53803e93a00c] btrfs/143: make test case more reliable
Code Diffstat:
common/fuzzy | 11 +-
common/rc | 1 +
.../aio-dio-append-write-read-race.c | 44 +++--
src/t_dir_type.c | 2 +-
tests/btrfs/143 | 20 +--
tests/btrfs/154 | 185 +++++++++++++++++++++
tests/btrfs/154.out | 10 ++
tests/btrfs/group | 1 +
tests/generic/453 | 5 +
tests/generic/454 | 5 +
tests/generic/468 | 124 ++++++++++++++
tests/generic/468.out | 13 ++
tests/generic/469 | 135 +++++++++++++++
tests/generic/469.out | 9 +
tests/generic/group | 2 +
tests/xfs/122 | 1 +
16 files changed, 531 insertions(+), 37 deletions(-)
--
Eryu Guan
eguan@redhat.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
reply other threads:[~2017-11-19 11:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5a116ac0.0b40650a.d1424.32e9@mx.google.com \
--to=guaneryu@gmail.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