All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Whitney <enwlinux@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, guaneryu@gmail.com
Subject: regression in 4.5-rc5 - generic/324 failure
Date: Wed, 9 Mar 2016 17:17:46 -0500	[thread overview]
Message-ID: <20160309221746.GA1763@localhost.localdomain> (raw)

I'm seeing generic/324 fail consistently when run with xfstest-bld's test
appliance in the 1k block size test case on x86_64.  This happened first on my
4.5-rc5 regression run, and it repeated on -rc6 and -rc7.

Reverting a commit introduced in 4.5-rc5 inhibits the failure:
"ext4: don't read blocks from disk after extents being swapped" (bcff24887d00)

And here's the failed test output:

generic/324 15s ...	[22:10:20][    3.304758] run fstests generic/324 at 2016-03-09 22:10:20
 [22:10:21] [failed, exit status 1] - output mismatch (see /results/results-1k/generic/324.out.bad)
    --- tests/generic/324.out	2015-10-25 10:50:34.000000000 +0000
    +++ /results/results-1k/generic/324.out.bad	2016-03-09 22:10:21.753937505 +0000
    @@ -22,2509 +22,5 @@
     XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
     Before: in_range(10, 40)
     After: in_range(1, -1)
    -Defragment file with 250 * 2 fragments
    -wrote 1234/1234 bytes at offset 0
    -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
    -wrote 1234/1234 bytes at offset 123400
    ...
    (Run 'diff -u tests/generic/324.out /results/results-1k/generic/324.out.bad'  to see the entire diff)
diff: standard output: Broken pipe
Ran: generic/324
Failures: generic/324
Failed 1 of 1 tests

Thanks,
Eric

             reply	other threads:[~2016-03-09 22:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 22:17 Eric Whitney [this message]
2016-03-09 23:19 ` regression in 4.5-rc5 - generic/324 failure 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=20160309221746.GA1763@localhost.localdomain \
    --to=enwlinux@gmail.com \
    --cc=guaneryu@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.