killy971
killy971
Because of the way hpc works, the coverage data generated only covers the modules which were referenced directly (or transitively?) by the test suites that are run. Because of this,...
Add support for custom rules such as the one introduced by #3 to mark otherwise as fully covered.
Example error message: ``` hpc: found 2 instances of Util in ["./.hpc","./dist/hpc/mix/test-two","./dist/hpc/mix/test-one","./dist/hpc/mix/hpc-coveralls-testing-0.1.0.0"] ``` TODO: report this to the GHC development team.
Related to #36 Make sure this can actually work.
Example `.travis.yml`: Relevant part of the `env` section ``` yaml env: - ghc=7.6.3 cabal=1.18 - ghc=7.8.3 cabal=1.18 coverage=1 ``` Revelant part of the `install` section: ``` yaml - cabal configure...
Retrieving the total coverage percentage from the report on coveralls.io is the most correct way to proceed, but it involves an extra curl query and the associated processing of possible...
Not sure if things can be improved, but at least the documentation could suggest some instructions to only run hpc-coveralls when using 7.8.x version of GHC when running matrix builds.
Environment variable reference: https://github.com/codecov/codecov-python/blob/8b9ec3989477c0276158f807a4643d431be288a8/codecov/__init__.py#L82-L148