From: Ruediger Meier <sweet_f_a@gmx.de>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: "Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: cancelling the tests says that they all passed
Date: Thu, 17 Mar 2016 11:35:19 +0100 [thread overview]
Message-ID: <201603171135.19679.sweet_f_a@gmx.de> (raw)
In-Reply-To: <1458207847.751745.551787010.6EE6554F@webmail.messagingengine.com>
On Thursday 17 March 2016, Benno Schulenberg wrote:
> When one hits ^C when the compilation phase of 'make check'
> finishes and the first tests start executing, the script prints
I don't manage to reproduce that. How do you run make exactly (-j)?
If I hit ctrl-C during compilation then the test script does not start
at all. Maybe there is a dependency problem and your tests start before
compilation is finished?
> All 177 tests PASSED
This is because the test script actually means this
"None of 177 available tests failed"
It does not count the executed tests but failures only.
> before aborting. That... doesn't seem quite right.
I've had already planned to improve/refactor the failure/success
counting and also the handling of broken/aborted scripts. Probably this
would also improve such cosmetical issues.
But this is something for the next release. Would be too risky to change
something just a few days before releasing 2.28.
> When I leave the tests to run to completion, it says:
>
> 4 tests of 177 FAILED
>
> The failed ones are these:
>
> ipcs: mk-rm-shm ...
> FAILED (ipcs/mk-rm-shm) misc: fallocate
> ... FAILED (misc/fallocate) misc: swaplabel
> ... FAILED (misc/swaplabel) misc: ul
> ... FAILED (misc/ul)
>
Could you show us the test diffs?
$ find tests/diff/ -type f | xargs -r cat
Maybe also warnings durning the test run (if any).
cu,
Rudi
next prev parent reply other threads:[~2016-03-17 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 9:44 cancelling the tests says that they all passed Benno Schulenberg
2016-03-17 10:35 ` Ruediger Meier [this message]
2016-03-17 11:53 ` Benno Schulenberg
2016-03-17 12:50 ` Ruediger Meier
2016-03-17 16:49 ` Benno Schulenberg
2016-03-17 17:18 ` Ruediger Meier
2016-03-17 18:23 ` Benno Schulenberg
2016-03-17 19:48 ` Ruediger Meier
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=201603171135.19679.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=bensberg@justemail.net \
--cc=util-linux@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