Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50735A0D.5000005@gentoo.org>
Date: Mon, 08 Oct 2012 18:56:13 -0400
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@...too.org>
To: john-users@...ts.openwall.com
Subject: Re: john --test failures

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/08/2012 04:42 PM, Solar Designer wrote:
> 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!
My fault
> 
>> 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.
> 
A working test is month of work? ouch.

> I suggest that you only disable the tests in GPU builds.  When you do
> CPU builds, running "make check" right after build is appropriate.

I'm working on implementing this now, thanks for the suggestion.  Given
that opencl stuff doesn't work for the test yet, I'd like to prep for
when it does work.  Right now when built for opencl/cuda I get the
following error:

OpenCL error (UNKNOWN ERROR :() in file (common-opencl.c) at line (321)
- - (Error querying for platforms)

Is this caused by my build user not having access to the device or
something else?

thanks,
Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQc1oNAAoJEKXdFCfdEflK6DgP/iEpSndBhHqwm2hXDq1agjjw
3Ayn2rZtBb3iwL0jVG3WgpowKH7Xa/oi/kQtPdBXRo0DteHItaNgHJtQPawCIu8G
3SY5qPnje2Fna6mkbjqeN0gQfCZEMOT6/VY6yGyQnJOU2+vg9B8CITecHhNr8yJi
TxOApkVs3EEFdajp3B3mMpNA0S8PDzkmlv8yvAu1V91UUzhGqd7CwBE/phaAhjqV
TUqMvPn46oPPmqHrlmoWPEgGQTnOSQ31emq2Mt9ICC4BzwpLrUwzCaiI6H024wwD
EHT9sSoGtjz3dyAa07n5z0DjLZz1LpceEfco9TajcJgMC4PqBBKDdU8T543m894q
GnL4/wU42g4wPkB03zTS4XDBdW07El7chaSjYvOxfntTDB4z2BHcGsWoLHNk50JH
eO/j9Dlpkxw4EmVuaucooj1OkYK+0IrP+XnC5+/7u+1f729FzRC25D5uIgocBX5U
JZtA5e2a1eqOIrS2+GH8IIXNRfFHsB7T+N/Wny0fZnA1JqJLcxLCBzaRbd8rtyhA
XAMDP2U3vqpLSYXaLOR2gQfKcpra6wJD523OjfbHr9qIstToqSSyglaNGL2ECcBG
Fh2MftN6DfbAPECyPbTa0KzMPCb1QopgXXjWdv3Q4UD5jrYE3w84GvRWrcWcmn3o
5JCHeJ6Lf7Xw5TtHwtnI
=blrz
-----END PGP SIGNATURE-----

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.