From: Andreas Dilger <adilger@sun.com>
To: Nick Dokos <nicholas.dokos@hp.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsprogs w/64-bit patches: make check gets one failure
Date: Wed, 11 Mar 2009 22:02:10 -0600 [thread overview]
Message-ID: <20090312040210.GQ3199@webber.adilger.int> (raw)
In-Reply-To: <12304.1236797612@alphaville.usa.hp.com>
On Mar 11, 2009 14:53 -0400, Nick Dokos wrote:
> I followed the workflow that Ted described in the following message:
>
> http://marc.info/?l=linux-ext4&m=123367642710241&w=2
>
> with the patch series from git://github.com/tytso/e2fsprogs-64bit.git
>
> With all the patches in the series file applied, make check gives
> me the following error:
>
> ...
> f_h_reindex: reindex HTREE Directory with different hash seed: failed
> ...
> 100 tests succeeded 1 tests failed
> make[1]: *** [check] Error 1
> make[1]: Leaving directory `/home/nick/src/e2fsprogs/standard/build/tests'
> make: *** [check-recursive] Error 1
Including the content of the tests/f_h_reindex.failed file might make
the problem obvious. Possibly it is just some change in the output
format that is causing expect to fail.
> I bisected the series and found that the culprit seems to be
>
> 0024-Miscellaneous-e2fsck-related-64-bit-fixes.patch
>
> Unfortunately, a bunch of later patches don't apply cleanly without
> this one, so the most complete series file that does not get the
> error is the following - uncommenting 0024 gives the error:
Well, "make check" should pass after every patch in the series, so the
fact that later ones do not pass is irrelevant.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-03-12 4:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 18:53 e2fsprogs w/64-bit patches: make check gets one failure Nick Dokos
2009-03-12 4:02 ` Andreas Dilger [this message]
[not found] ` <12502.1236867091@gamaville.dokosmarshall.org>
2009-03-12 20:36 ` Andreas Dilger
2009-03-12 21:42 ` Nick Dokos
2009-03-13 22:38 ` Andreas Dilger
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=20090312040210.GQ3199@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=nicholas.dokos@hp.com \
/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).