Ollie Charles authored 4 years ago and Ollie Charles committed 3 years ago

Currently, if you have multiple packages in a project and try and run
the test suite of a single package with --enable-coverage, hpc will fail
to run. The problem is that _all_ dependencies of the package are built
with `-fhpc`, but when we run `hpc markup`, we are only passing the
`.mix` directory of the package being tested. Because we built all
dependencies with `-fhpc` and we haven't excluded them from the report,
we need to supply their `.mix` directories too.

The above suggests one fix - compute the transitive closure of all
`.mix` directories. However, there is another solution - change from
using an exclude-list to using an include-list. This is the approach
used in this commit.

Explicitly enumerating all modules to _include_ in the report is simpler
to code, but is also more likely to be what the user is interested in.
Generally, when one generates a coverage report from a test-suite, they
want to understand the coverage of the unit being tested. Having
coverage information from dependencies is usually not relevant. This is
also the behavior from old-style Cabal builds, where there wasn't even
a notion of a Cabal project.

Fixes #5433.

--only-download flag

--dry-run
--only-dependencies
--only-configure
--only-download

Allow bytestring-0.11 + tree-diff-0.2

Bump Win32 upper bound

Actually propagate base16-bytestring 1.0 to all cabal files

Suggest command on spelling mistakes

I want to use stack diffs (https://github.com/ezyang/ghstack/

) to
submit PRs to Cabal.  Stack diffs, simply by virtue of what they
are, are PRs that are targeted to branches that are not master (they
target an appropriate base that lets GitHub render only the change
in question, even if there are other changes below it.)  However,
I don't get CI jobs on those stack diffs because the current
pull_request branch selector is too restrictive.  This PR makes
it less restrictive.

This PR is submitted using ghstack to validate that this indeed
works.

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

ghstack-source-id: b135ea67848f873fc6b50b950405859587ae8d89
Pull Request resolved: https://github.com/haskell/cabal/pull/7308

Assume list-bin target selectors are for executables

Add ghc 9.0 to ci

Allow base16-bytestring 1.0 and newer

Bump Win32 bound

To accomodate 2.12.0.0. No changes necessary

This reverts commit 981f6d9d.

Upstream looks unmaintained, and we only use a single function anyway.
The package did not build with ghc 9, so we include a fixed version of
that function.

Read file contents strictly to avoid resource exhaustion

Fix containerless CI jobs by upgrading to ghc 8.10

8.6 was no longer included in the image

Clarify cabal.project documentation

Bump upper bound on bytestring