-
Notifications
You must be signed in to change notification settings - Fork 841
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
Coverage report not picking any tests with ghc-7.10 resolver #785
Comments
Hi! Sorry for not getting back to this sooner. That doesn't sound like a known problem to me. Do you still have the details about how to reproduce the bug? |
Also, this might be relevant: #1009 |
Yes, it's exactly the same error as in #1009. Here it's a way to reproduce it:
That works as expected. But the following gives 100% coverage with 0 tests run:
My stack binary is coming from Arch Linux AUR, this is what
I was about to try with |
I can confirm this also happens with |
Thanks for the repro, it works for me. Very strange! |
@mgsloan what OS are you on? 😕 |
Ubuntu. The repro does work. The very strange thing is the bug. The verbose logs don't show the two builds doing anything very different, and both of the runs generate .tix files. Looking into it |
If I remember correctly with |
Ah, looks like the problem has something to do with the hashed package identifier stuff, I'm ending up with folders like |
Is this related? ttuegel/cabal@1bda428 and haskell/cabal#2457 |
Yup, that's related! The fix was more involved than I'd hoped (parsing Please close the issue if it works for you. Thanks for reporting it! |
Works now for me. Thank you! |
@jdnavarro Turns out my implementation approach was flawed. Asking ghc-pkg for the package key only works if the package version you're testing is the exact one that's installed.. I've just pushed a commit that instead parses the key out of package.conf.inplace. |
I didn't notice the flaw, but may have created some confusion in the future. Thanks for fixing it. |
Welcome! I'm actually back on the case, as the fix caused issues: #1162 |
The tests run properly, but none are shown in the coverage report. This only happens with the ghc-7.10 resolver. The coverage is coming fine when using lts-2.22 resolver or when using a
cabal-install
sandbox with ghc-7.10.1.I can provide more detailed information to reproduce the bug, but wanted to confirm this doesn't sound like a known problem.
The text was updated successfully, but these errors were encountered: