Skip to content
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

Update changelog for per-component with coverage #9464 #9542

Merged
merged 1 commit into from
Jan 5, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
22 changes: 22 additions & 0 deletions changelog.d/pr-9464
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
synopsis: Support per-component builds when coverage is enabled
packages: Cabal cabal-install
prs: #9464
issues: #4798 #5213 #6440 #6397
significance: significant

description: {

Cabal now supports per-component builds when coverage is enabled. This enables
coverage for packages with internal libraries (#6440), and enables coverage for
packages that use backpack (#6397), even though we do not get coverage for
instantiations of an indefinite module (it is not clear what it means for HPC
to support backpack, regardless of Cabal).

To achieve this, hpc information (`.mix` files) from a library is now written
into the package database of a library under `extraCompilationArtifacts`.

Cabal configure (via the Setup interface) now accepts --coverage-for=<unit-id>,
a flag which specifies which libraries should be included in the coverage
report for some testsuite.

}