[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121008204210.GA10656@openwall.com>
Date: Tue, 9 Oct 2012 00:42:10 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: john --test failures
On Mon, Oct 08, 2012 at 04:22:50PM -0400, Rick Zero_Chaos Farina wrote:
> It was a plain --test. I reported either the same or an extremely
> similar bug for the last jumbo patch, and yes, I know it's a known issue.
When you remind us of known issues, please word your messages
accordingly. Thanks!
> Gentoo users expect tests to pass. Not just in that "it's cool to watch
> the numbers scroll by" way, when the package is compiled it is tested
> before installed. The obvious choice of a test for jtr to ensure all
> functionality is working as expected would be "./john --test". The fact
> that --test failed means that all of my users cannot install jtr, or I
> must forcibly disable the tests. For now, I have obviously disabled the
> tests since I know they are unreliable, but my point is this is
> important enough to merit a fix.
Of course. For us, it was a choice between not releasing the GPU
support for some months more or releasing with the --test bug.
I suggest that you only disable the tests in GPU builds. When you do
CPU builds, running "make check" right after build is appropriate.
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
