-
Notifications
You must be signed in to change notification settings - Fork 20
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 on TravisCI #158
Comments
I didn't do a very good job following our git workflow this time... Nor last time now that I think of it. I rewrote the history (if you cloned this in the last few days, sorry!) to put master and stable back into their pre-1.1.2 state, and I'm now doing this properly on the release-1.1.2 branch. |
So I can see in the output that the doctest tests pass and that it's the "Test suite reference" part which fails, but if I comment out the doctests and leave only the test suite reference, it passes. There an interaction between my tests? |
I remember that doctest tests can interact with each other because ghci's state is kept between tests, and I've had to reorder some of the tests over the years to avoid mysterious deadlocks. I don't understand how doctest could have an impact on non-doctest tests. |
Great, now TravisCI refuses to run our tests, I guess we have to upgrade the format of our
|
See here for example, and the many failures before it. I've managed to reproduce the problem using the following Dockerfile:
The text was updated successfully, but these errors were encountered: