From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: Refreshed rootfs.img for kvm-xfstests
Date: Sun, 25 Oct 2015 17:26:46 -0400 [thread overview]
Message-ID: <20151025212646.GA25680@thunk.org> (raw)
Hi, I've uploaded an updated rootfs.img at:
https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests
It includes the xfstests-dev upstream version 0e6ead559169 (Updated
from Oct. 14th) and some configuration changes to minimize some test
failure noise. The config files are commented with the known
failures, for example:
https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/tree/kvm-xfstests/test-appliance/files/root/conf/encrypt.exclude
https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/tree/kvm-xfstests/test-appliance/files/root/conf/data_journal_noleak
I am currently getting the following results:
BEGIN TEST 4k: Ext4 4k block Sun Oct 25 07:29:52 EDT 2015
Failures: ext4/304
BEGIN TEST 1k: Ext4 1k block Sun Oct 25 08:12:58 EDT 2015
Failures: ext4/304 generic/018
BEGIN TEST ext3: Ext4 4k block emulating ext3 Sun Oct 25 09:01:21 EDT 2015
Failures: ext4/301 ext4/302 ext4/303 ext4/304 generic/018
BEGIN TEST encrypt: Ext4 encryption Sun Oct 25 09:44:13 EDT 2015
Failures: ext4/301 ext4/303 ext4/304
BEGIN TEST nojournal: Ext4 4k block w/ no journal Sun Oct 25 10:20:57 EDT 2015
Failures: ext4/301 ext4/304
BEGIN TEST ext3conv: Ext4 4k block w/nodelalloc and no flex_bg Sun Oct 25 11:01:06 EDT 2015
Failures: ext4/304
BEGIN TEST dioread_nolock: Ext4 4k block w/dioread_nolock Sun Oct 25 11:41:36 EDT 2015
Failures: ext4/001 ext4/304 ext4/308 generic/324
BEGIN TEST data_journal_noleak: Ext4 4k block w/data=journal Sun Oct 25 12:24:57 EDT 2015
Failures: ext4/271 ext4/301 ext4/302 ext4/303 ext4/304 ext4/308 generic/018
BEGIN TEST inline: Ext4 4k block w/inline Sun Oct 25 13:16:58 EDT 2015
Failures: ext4/304
BEGIN TEST bigalloc: Ext4 4k block w/bigalloc Sun Oct 25 14:00:23 EDT 2015
Failures: ext4/004 generic/018 generic/204 generic/219 generic/235 generic/273
BEGIN TEST bigalloc_1k: Ext4 1k block w/bigalloc Sun Oct 25 14:46:29 EDT 2015
Failures: ext4/004 generic/018 generic/204 generic/235
(The ext4/30[1234] failures we only recently added back the these
tests that had been previously marked as dangerous and not in the auto
group. ext4/304 is pretty clearly a buggy test as near as I can tell.
I haven't had a chance to rule out the others. generic/018 is an
expected failures due to how we handle defrag; I should just add that
to all.exclude. I need to take a closer look at some of the other
failures to understand what is going on.)
- Ted
next reply other threads:[~2015-10-25 21:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 21:26 Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-04 6:13 Refreshed rootfs.img for kvm-xfstests Theodore Ts'o
2016-06-30 15:28 Theodore Ts'o
2016-07-01 15:54 ` Theodore Ts'o
2016-07-17 14:05 Theodore Ts'o
2016-07-21 20:22 ` Eric Whitney
2016-07-23 15:10 ` Theodore Ts'o
2016-07-23 23:06 ` Eric Whitney
2016-07-24 8:18 ` Theodore Ts'o
2017-01-09 23:14 Theodore Ts'o
2017-01-10 3:38 ` Theodore Ts'o
2017-01-10 12:48 ` Roman Penyaev
2017-01-10 15:07 ` Roman Penyaev
2017-01-11 3:05 ` Theodore Ts'o
2017-01-10 18:50 ` Eric Biggers
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=20151025212646.GA25680@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).