public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	kdevops@lists.linux.dev, dave@stgolabs.net, jack@suse.cz
Subject: Re: ext4 v6.15-rc2 baseline
Date: Wed, 16 Apr 2025 18:34:15 -0500	[thread overview]
Message-ID: <20250416233415.GA3779528@mit.edu> (raw)
In-Reply-To: <Z__vQcCF9xovbwtT@bombadil.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]

On Wed, Apr 16, 2025 at 10:56:17AM -0700, Luis Chamberlain wrote:
> ext4 developers,
> 
> kdevops has run fstests on v6.15-rc2 across the different ext4 profiles
> it currently defines, and the results are below.

Hmm, there are quite a lot of failures that aren't in my baseline.  In
particular, I work very hard to make sure the 4k profile is clean, and
as you can see in the attached file, it is.  But here's a short
summary (for the full set, including the versions used for the full
test run, see the attached file.)

ext4/4k: 587 tests, 55 skipped, 5340 seconds
ext4/1k: 581 tests, 59 skipped, 5700 seconds
ext4/ext3: 579 tests, 1 failures, 149 skipped, 4715 seconds
  Failures: ext4/028
ext4/encrypt: 562 tests, 175 skipped, 2982 seconds
ext4/nojournal: 579 tests, 127 skipped, 3955 seconds
   ...

I'll have to take a look at your test results tarball (I assume it
includes the NNN.out.bad and NNN.full files, right) to see what's
going on.

There are some exclude files[1][2] which I use to reduce noise, but
that doesn't seem to explain many of your failures that you have reported.

[1] https://github.com/tytso/xfstests-bld/blob/master/test-appliance/files/root/fs/global_exclude
[2] https://github.com/tytso/xfstests-bld/blob/master/test-appliance/files/root/fs/ext4/exclude

>  - Is this useful information?

Maybe; the question is why are your results so different from my results.

       	   	       	       	    	    - Ted

[-- Attachment #2: ext4-baseline-6.15-rc2 --]
[-- Type: text/plain, Size: 2101 bytes --]

TESTRUNID: ltm-20250414133140
KERNEL:    kernel 6.15.0-rc2-xfstests #22 SMP PREEMPT_DYNAMIC Mon Apr 14 12:18:46 EDT 2025 x86_64
CMDLINE:   --kernel gs://gce-xfstests/kernel.deb -c ext4/all -g auto
CPUS:      2
MEM:       7680

ext4/4k: 587 tests, 55 skipped, 5340 seconds
ext4/1k: 581 tests, 59 skipped, 5700 seconds
ext4/ext3: 579 tests, 1 failures, 149 skipped, 4715 seconds
  Failures: ext4/028
ext4/encrypt: 562 tests, 175 skipped, 2982 seconds
ext4/nojournal: 579 tests, 127 skipped, 3955 seconds
ext4/ext3conv: 584 tests, 57 skipped, 5164 seconds
ext4/adv: 580 tests, 2 failures, 63 skipped, 4873 seconds
  Failures: generic/757 generic/764
ext4/dioread_nolock: 585 tests, 55 skipped, 5538 seconds
ext4/data_journal: 592 tests, 8 failures, 1 errors, 135 skipped, 4464 seconds
  Failures: generic/127
  Flaky: generic/032: 20% (1/5)   generic/475: 40% (2/5)
  Errors: generic/475
ext4/bigalloc_4k: 558 tests, 1 failures, 58 skipped, 5128 seconds
  Flaky: generic/234: 20% (1/5)
ext4/bigalloc_1k: 559 tests, 69 skipped, 4965 seconds
ext4/dax: 571 tests, 2 failures, 160 skipped, 3111 seconds
  Failures: generic/344 generic/363
Totals: 6941 tests, 1162 skipped, 34 failures, 1 errors, 52426s

FSTESTIMG: gce-xfstests/xfstests-amd64-202504110828
FSTESTPRJ: gce-xfstests
FSTESTVER: blktests 236edfd (Tue, 18 Mar 2025 12:56:26 +0900)
FSTESTVER: fio  fio-3.39 (Tue, 18 Feb 2025 08:36:57 -0700)
FSTESTVER: fsverity v1.6-2-gee7d74d (Mon, 17 Feb 2025 11:41:58 -0800)
FSTESTVER: ima-evm-utils v1.5 (Mon, 6 Mar 2023 07:40:07 -0500)
FSTESTVER: libaio   libaio-0.3.108-82-gb8eadc9 (Thu, 2 Jun 2022 13:33:11 +0200)
FSTESTVER: ltp  20250130-195-ge2bbba0c1 (Fri, 11 Apr 2025 18:06:15 +0800)
FSTESTVER: quota  v4.05-69-g68952f1 (Mon, 7 Oct 2024 15:45:56 -0400)
FSTESTVER: util-linux v2.41 (Tue, 18 Mar 2025 13:50:51 +0100)
FSTESTVER: xfsprogs v6.13.0-2-gf0d16c9e (Tue, 1 Apr 2025 20:23:42 -0400)
FSTESTVER: xfstests-bld 42bcd9aa (Wed, 9 Apr 2025 07:51:57 -0400)
FSTESTVER: xfstests v2025.03.30-11-g344015670 (Mon, 31 Mar 2025 13:50:06 -0400)
FSTESTVER: zz_build-distro bookworm
FSTESTSET: -g auto
FSTESTOPT: aex

  reply	other threads:[~2025-04-16 23:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 17:56 ext4 v6.15-rc2 baseline Luis Chamberlain
2025-04-16 23:34 ` Theodore Ts'o [this message]
2025-04-17 16:38   ` Darrick J. Wong
2025-04-17 18:37     ` Theodore Ts'o
2025-04-17 20:56       ` Luis Chamberlain
2025-04-19 18:22         ` Theodore Ts'o
2025-04-21 15:54           ` Darrick J. Wong
2025-04-21 16:29             ` Theodore Ts'o
2025-04-21 16:47               ` Darrick J. Wong
2025-04-17 16:49   ` Theodore Ts'o
2025-04-17 20:35     ` Luis Chamberlain
2025-04-18  1:42       ` Luis Chamberlain
2025-04-18  3:56         ` Theodore Ts'o
2025-04-18 19:08           ` Luis Chamberlain
2025-04-19 18:36             ` Theodore Ts'o
2025-04-20  3:39               ` Theodore Ts'o

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=20250416233415.GA3779528@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=dave@stgolabs.net \
    --cc=jack@suse.cz \
    --cc=kdevops@lists.linux.dev \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mcgrof@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