search

tel / saltine

Cryptography that's easy to digest (NaCl/libsodium bindings)
https://github.com/tel/saltine
MIT License
61 stars 29 forks source link

MacOS: Tests fail #47

Closed mouse07410 closed 5 years ago

mouse07410 commented 6 years ago

MacOS 10.13.4, Xcode-9.3, GHC-8.2.2, current stack and cabal.

$ cabal test --show-details=always
Preprocessing library for saltine-0.1.0.1..
Building library for saltine-0.1.0.1..
Preprocessing test suite 'tests' for saltine-0.1.0.1..
Building test suite 'tests' for saltine-0.1.0.1..
Running 1 test suites...
Test suite tests: RUNNING...
Test suite tests: FAIL
Test suite logged to: dist/test/saltine-0.1.0.1-tests.log
0 of 1 test suites (0 of 1 test cases) passed.
$ cat dist/test/saltine-0.1.0.1.log
PackageLog {package = PackageIdentifier {pkgName = PackageName "saltine", pkgVersion = mkVersion [0,1,0,1]}, compiler = CompilerId GHC (mkVersion [8,2,2]), platform = Platform X86_64 OSX, testSuites = [TestSuiteLog {testSuiteName = UnqualComponentName "tests", testLogs = TestLog {testName = "tests", testOptionsReturned = [], testResult = Fail "exit code: -11"}, logFile = "dist/test/saltine-0.1.0.1-tests.log"}]}
$ cat dist/test/saltine-0.1.0.1-tests.log
Test suite tests: RUNNING...
Test suite tests: FAIL
Test suite logged to: dist/test/saltine-0.1.0.1-tests.log
$

Here's the complete console output:
saltine-test-out.txt

Is there any way to get some meaningful error message from the tests? The log as-is is practically useless - it does not tell what tests ran, what tests failed, and more importantly - failed how/on what...

Help is appreciated.

linearray commented 5 years ago

I just tried cabal test and cabal new-test (cabal/cabal-install 2.2.0.0) and while it takes some time, all tests finish successfully.

Please reopen if this issue persists.