tests are too slow

[jfischoff]

No description provided.

[ericpashman]

Have you run the tests to completion to verify that they actually pass? If not, I have them running now and will let them keep going. ...

I know test-framework supports running tests in parallel, by the way, but I don't know how to run them through Cabal. It might be as easy as using the -j flag.

[jfischoff]

Have you run the tests to completion to verify that they actually pass? If not, I have them running now and will let them keep going. ...

No I haven't. I also should add a note that the approx comparison delta is really large and doing this approx comparison is probably not the right way to deal with Doubles, but I don't know any alternative ATM.

I know test-framework supports running tests in parallel, by the way, but I don't know how to run them through Cabal. It might be as easy as using the -j flag.

Interesting. I don't really care if we use the cabal test stuff. It might be better to have a separate cabal file in the test directory that makes an executable. Then we could definitely run them in parallel. Also we should use tasty.

[ericpashman]

I'd prefer to use tasty too.

[jfischoff]

I'd prefer to use tasty too.

Added here: #6

[ericpashman]

Just FYI, I let the tests run to completion and everything passed:

cabal test -j4
Test suite tests: PASS
Test suite logged to: dist/test/maxent-0.7-tests.log
1 of 1 test suites (1 of 1 test cases) passed.

So the tests in the harness check out anyway.

[jfischoff]

Nice

On Fri, Oct 10, 2014 at 12:44 PM, Eric Pashman [email protected]
wrote:

Just FYI, I let the tests run to completion and everything passed:

cabal test -j4
Test suite tests: PASS
Test suite logged to: dist/test/maxent-0.7-tests.log
1 of 1 test suites (1 of 1 test cases) passed.

So the tests in the harness check out anyway.

—
Reply to this email directly or view it on GitHub
#3 (comment).