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

relude-0.6.0.0 fails its test suite #241

Closed
peti opened this issue Jan 31, 2020 · 2 comments
Closed

relude-0.6.0.0 fails its test suite #241

peti opened this issue Jan 31, 2020 · 2 comments
Labels
question Further information is requested tests

Comments

@peti
Copy link

peti commented Jan 31, 2020

Building on Linux with ghc-8.8.1 I got:

Running 2 test suites...
Test suite relude-doctest: RUNNING...
src/Relude/DeepSeq.hs:36: failure in expression `:sprint list'
expected: list = _
 but got: list = [2,1,3]

src/Relude/DeepSeq.hs:50: failure in expression `:sprint list'
expected: list = _
 but got: list = [2,1,3]

src/Relude/DeepSeq.hs:65: failure in expression `:sprint list'
expected: list = _
 but got: list = [2,1,3]

src/Relude/DeepSeq.hs:81: failure in expression `:sprint list'
expected: list = _
 but got: list = [2,1,3]

Examples: 445  Tried: 437  Errors: 0  Failures: 4
Test suite relude-doctest: FAIL
Test suite logged to: dist/test/relude-0.6.0.0-relude-doctest.log
Test suite relude-test: RUNNING...
Test suite relude-test: PASS
Test suite logged to: dist/test/relude-0.6.0.0-relude-test.log
1 of 2 test suites (1 of 2 test cases) passed.
@chshersh chshersh added question Further information is requested tests labels Feb 3, 2020
@chshersh
Copy link
Contributor

chshersh commented Feb 3, 2020

@peti thanks for reporting the issue. This is a known problem and is caused by changes in GHC; I opened the following ticket there a while ago:

The fix for tests is already implemented in the following commit:

Unfortunately, it didn't get into 0.6.0.0 release despite thorough checks on CI for multiple GHC versions. However, if you build from master, you shouldn't get this error.

@chshersh chshersh added this to the v0.7.0.0: Refiner refinement milestone Feb 25, 2020
@vrom911
Copy link
Member

vrom911 commented Mar 25, 2020

Unfortunately, we can't do anything to 0.6.0.0, but this is already fixed in master, so it is going to be in the 0.7.0.0 release 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested tests
Projects
None yet
Development

No branches or pull requests

3 participants