From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: e2fsprogs-1.43 make check failures
Date: Sat, 28 May 2016 16:36:50 -0500 [thread overview]
Message-ID: <574A0F72.6020609@gmail.com> (raw)
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'.
Many of the failures look like:
$ cat f_lpffile.failed
--- ../../tests/f_lpffile/expect.1 2009-08-13 01:39:58.000000000 +0000
+++ f_lpffile.1.log 2016-05-28 19:40:20.364025801 +0000
@@ -1,3 +1,4 @@
+e2fsck 1.43 (17-May-2016)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
--- ../../tests/f_lpffile/expect.2 2009-08-13 01:39:58.000000000 +0000
+++ f_lpffile.2.log 2016-05-28 19:40:20.367025703 +0000
@@ -1,3 +1,4 @@
+e2fsck 1.43 (17-May-2016)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
In fact running:
[ /sources/e2fsprogs-1.43/build/tests ]$ grep ^+ *.failed|grep -v
1.43|grep -v @@|grep -v +++
gives no output. My conclusion is that all the tests actually pass, but
the expected results need to be updated in the release tarball.
-- Bruce Dubbs
linuxfromscratch.org
next reply other threads:[~2016-05-28 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 21:36 Bruce Dubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-28 22:45 e2fsprogs-1.43 make check failures Xose Vazquez Perez
2016-05-28 23:54 ` 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=574A0F72.6020609@gmail.com \
--to=bruce.dubbs@gmail.com \
--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).