From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: e2fsprogs-1.43 make check failures
Date: Sat, 28 May 2016 18:54:12 -0500 [thread overview]
Message-ID: <574A2FA4.3050106@gmail.com> (raw)
In-Reply-To: <511107d2-9b17-e5ab-c900-3ccfadb724f9@gmail.com>
Xose Vazquez Perez wrote:
> Bruce Dubbs wrote:
>
>> When building e2fsprogs we normally ask users to run 'make check'. For
>> e2fsprogs-1.42.13 we had '153 tests succeeded, 0 tests failed', but for
>> version 1.43, we have '62 tests succeeded, 265 tests failed'.
>
> Documented in: http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.43
>
> ----
> E2fsprogs 1.43 (May 17, 2016)
>
> KNOWN BUG: "make check" will have many spurious failures in the tests directory.
> The fix can be found at: https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/commit/?id=e7d848266a224cc1ed3c74c6746b5c779a5f55ce
> ----
Missed that entry. Thank you.
-- Bruce
next prev parent reply other threads:[~2016-05-28 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 22:45 e2fsprogs-1.43 make check failures Xose Vazquez Perez
2016-05-28 23:54 ` Bruce Dubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-28 21:36 Bruce Dubbs
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=574A2FA4.3050106@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=xose.vazquez@gmail.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).