We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The dhall:doctest suite doesn't finish anymore since we've switched from GHC 8.6.5 to 8.10.4.
dhall:doctest
For example in https://github.com/dhall-lang/dhall-haskell/pull/2239/checks?check_run_id=3008625914#step:6:1500 you can see that doctest prints the final summary, but stack fails to report success as usual with
stack
dhall> Test suite doctest passed
We've only observed this issue in GitHub Actions and on AppVeyor so far, but you should be able to reproduce this locally on a Windows machine with:
git clone https://github.com/dhall-lang/dhall-haskell cd dhall-haskell git checkout c23e4d55691bbec2cae6f809dece357de3153382 stack test dhall:doctest
The text was updated successfully, but these errors were encountered:
Note that the doctest suites of the dhall-docs and dhall-lsp-server packages in the same project pass and finish as expected.
doctest
dhall-docs
dhall-lsp-server
Sorry, something went wrong.
Any ideas what might be wrong?
Is it reasonable to assume that the actual test cases are passing (and not e.g. hanging), given the final summary
Examples: 252 Tried: 252 Errors: 0 Failures: 0
?
No branches or pull requests
The
dhall:doctest
suite doesn't finish anymore since we've switched from GHC 8.6.5 to 8.10.4.For example in https://github.com/dhall-lang/dhall-haskell/pull/2239/checks?check_run_id=3008625914#step:6:1500 you can see that doctest prints the final summary, but
stack
fails to report success as usual withWe've only observed this issue in GitHub Actions and on AppVeyor so far, but you should be able to reproduce this locally on a Windows machine with:
The text was updated successfully, but these errors were encountered: