Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests fail #40

Open
ZeroChaos- opened this issue Apr 28, 2013 · 6 comments
Open

tests fail #40

ZeroChaos- opened this issue Apr 28, 2013 · 6 comments

Comments

@ZeroChaos-
Copy link

When compiling for cpu only (can't build ati or nvidia successfully yet) all the tests fail.

I run "cd tests; ./test.sh" and get this:

Performing tests...

Testing bforce desunix multi FAILURE!
Testing bforce desunix single FAILURE!
Testing bforce ipb single FAILURE!
Testing bforce nsldap single FAILURE!
Testing bforce nsldap multi FAILURE!
Testing bforce nsldaps single FAILURE!
Testing bforce lm single FAILURE!
Testing bforce lm multi FAILURE!
Testing bforce md4 single FAILURE!
Testing bforce md4 multi FAILURE!
Testing bforce md5 single FAILURE!
Testing bforce md5 multi FAILURE!
Testing bforce md5md5 single FAILURE!
Testing bforce md5md5 multi FAILURE!
Testing bforce oscommerce single FAILURE!
Testing bforce joomla single FAILURE!
Testing bforce mscash single FAILURE!
Testing bforce mssql-2000 single FAILURE!
Testing bforce mssql-2005 single FAILURE!
Testing bforce mssql-2012 single FAILURE!
Testing bforce mysql5 single FAILURE!
Testing bforce mysql5 multi FAILURE!
Testing bforce ntlm single FAILURE!
Testing bforce ntlm multi FAILURE!
Testing bforce oracle-old single FAILURE!
Testing bforce oracle11g single FAILURE!
Testing bforce osxlion single FAILURE!
Testing bforce osx-old single FAILURE!
Testing bforce o5logon single FAILURE!
Testing bforce pixmd5 multi FAILURE!
Testing bforce pixmd5 single FAILURE!
Testing bforce sha1 multi FAILURE!
Testing bforce sha1 single FAILURE!
Testing bforce sha256 multi FAILURE!
Testing bforce sha256 single FAILURE!
Testing bforce sha512 multi FAILURE!
Testing bforce sha512 single FAILURE!
Testing bforce smf single FAILURE!
Testing bforce zip (old) single FAILURE!
Testing rule desunix single FAILURE!
Testing rule desunix multi FAILURE!
Testing rule apr1 single FAILURE!
Testing rule apr1 multi FAILURE!
Testing rule bfunix single FAILURE!
Testing rule bfunix multi FAILURE!
Testing rule django256 FAILURE!
Testing rule drupal7 FAILURE!
Testing rule dmg FAILURE!
Testing rule ipb single FAILURE!
Testing rule ipb multi FAILURE!
Testing rule nsldap single FAILURE!
Testing rule nsldap multi FAILURE!
Testing rule nsldaps single FAILURE!
Testing rule nsldaps multi FAILURE!
Testing rule lm single FAILURE!
Testing rule lm(>8) single FAILURE!
Testing rule lm multi FAILURE!
Testing rule md4 single FAILURE!
Testing rule md4 multi FAILURE!
Testing rule md5 single FAILURE!
Testing rule md5 multi FAILURE!
Testing rule md5md5 single FAILURE!
Testing rule md5md5 multi FAILURE!
Testing rule joomla single FAILURE!
Testing rule o5logon single FAILURE!
Testing rule oscommerce single FAILURE!
Testing rule md5unix single(1) FAILURE!
Testing rule md5unix single(2) FAILURE!
Testing rule md5unix single(3) FAILURE!
Testing rule md5unix single(4) FAILURE!
Testing rule md5unix single(5) FAILURE!
Testing rule md5unix single(6) FAILURE!
Testing rule md5unix single(7) FAILURE!
Testing rule md5unix single(8) FAILURE!
Testing rule md5unix single(9) FAILURE!
Testing rule md5unix single(10) FAILURE!
Testing rule md5unix single(11) FAILURE!
Testing rule md5unix single(12) FAILURE!
Testing rule md5unix single(13) FAILURE!
Testing rule md5unix single(14) FAILURE!
Testing rule md5unix single(15) FAILURE!
Testing rule mscash single FAILURE!
Testing rule mscash2 single FAILURE!
Testing rule mssql-2000 single FAILURE!
Testing rule mssql-2005 single FAILURE!
Testing rule mssql-2012 single FAILURE!
Testing rule mysql5 single FAILURE!
Testing rule mysql5 multi FAILURE!
Testing rule ntlm single FAILURE!
Testing rule ntlm multi FAILURE!
Testing rule oracle11g single FAILURE!
Testing rule oracle-old single FAILURE!
Testing rule osxlion single FAILURE!
Testing rule osx-old single FAILURE!
Testing rule phpbb3 single FAILURE!
Testing rule pixmd5 single FAILURE!
Testing rule pixmd5 multi FAILURE!
Testing rule rar(8) single FAILURE!
Testing rule sha1 single FAILURE!
Testing rule sha1 multi FAILURE!
Testing rule sha256 single FAILURE!
Testing rule sha256 multi FAILURE!
Testing rule sha256unix single FAILURE!
Testing rule sha512 single FAILURE!
Testing rule sha512 multi FAILURE!
Testing rule sha512unix single(8) FAILURE!
Testing rule smf single FAILURE!
Testing rule vbulletin single FAILURE!
Testing rule wordpress single FAILURE!
Testing rule wpa (WPA) single FAILURE!
Testing rule wpa (WPA2) single FAILURE!
Testing rule zip (old) single FAILURE!
Testing rule zip (AES128) single FAILURE!
Testing rule zip (AES256) single FAILURE!
Testing rule privkey (CPU only!) FAILURE!
Testing rule sapg (CPU only!) FAILURE!
Testing rule sha1sha1 (CPU only!) FAILURE!
Testing rule mediawiki (CPU only!) FAILURE!
Testing rule ripemd160 (CPU only!) FAILURE!
Testing rule msoffice (2007) FAILURE!
Testing rule msoffice (2010) FAILURE!
Testing rule msoffice (2013) FAILURE!
Testing rule luks (256) FAILURE!
Testing rule luks (128) FAILURE!

124 tests performed, 124 errors found.

Am I doing it wrong? Is this not ready for use yet? Does hashkill require one of the OpenCL supports enabled? I had no build errors, everything seemed fine, but all tests fail.

Also if you are bored (which given the tickets I've been filing I doubt) it would be cool to make the tests run with "make test" (which currently does nothing) or "make check" (which looks like it starts to do something then errors).

@gat3way
Copy link
Owner

gat3way commented Apr 28, 2013

There should be a file named "output" in the test directory which contains the output from the last test performed. Could you please paste its contents?

@ZeroChaos-
Copy link
Author

Nu hashkill # cat /var/tmp/portage/app-crypt/hashkill-9999/work/hashkill-9999/tests/output
./test.sh: line 13: /dev/console: Permission denied

that's.... odd. why is it trying to directly write to console?

@ZeroChaos-
Copy link
Author

tests look a lot better if I allow that access, but honestly that's pretty ugly. any chance of writing this a bit more sanely and not directly interacting with /dev/console like that?

@ZeroChaos-
Copy link
Author

Also, would it be possible to add "return $ERRORS" at the end of the script? that way if it doesn't error it will return 0 and otherwise it will return an error state equal to the number of errors.

@gat3way
Copy link
Owner

gat3way commented May 1, 2013

Working on that.

@gat3way
Copy link
Owner

gat3way commented May 3, 2013

Should be OK with the latest commit. Could you test?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants