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
0.4 test failure: Ambiguous module name ‘Data.HashSet’ #15
Comments
|
I am not sure why this happens, given that Should we use |
You are correct in that you shouldn't need PackageImports, strange error. I also queued swagger2 at http://matrix.hackage.haskell.org/package/swagger2 |
Sorry I missed that this was the test-suite, so matrix won't help. But it did uncover other build errors |
@bergmark I am sorry, but where can I find the error? I see no logs there. |
The GHC 7.10 build error is weird because it refers to @bergmark how can I improve my Travis builds to catch this kind of errors before the release? |
I use https://github.com/hvr/multi-ghc-travis to test multiple GHC versions. Matrix essentially just does |
I hoped for a Okay, will switch back to |
@bergmark what should I do about tests failure? |
Yes that seems correct. From the little I know about doctest it sounds plausible that it doesn't use packages dependencies properly and instead uses the whole packagedb. If so, a PackageImport would solve this. But it may be wise to ask the doctest developers as well. |
PackageImports extension fixes conflicts with hashset package which should not arise since swagger2 does not have hashset in its dependencies. But since doctest uses the whole packagedb, this seems to be the best way of dealing with it for now. See #15 for more details.
The GHC 7.10 build failure in matrix is due to I have added an upper version bound for |
Closing this issue since both build problems should be fixed in v0.4.1. |
Thanks! |
See commercialhaskell/stackage#1010
Test failed in the Stackage Nightly for swagger2-0.4
The text was updated successfully, but these errors were encountered: