From: Remi Gacogne Date: Fri, 22 Sep 2023 10:05:17 +0000 (+0200) Subject: Code coverage: Fix a link X-Git-Tag: rec-5.0.0-alpha2~20^2~2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f2e51268c9ed9f04a37e501e25b69b5ae8a5a764;p=thirdparty%2Fpdns.git Code coverage: Fix a link --- diff --git a/CODE_COVERAGE.md b/CODE_COVERAGE.md index 4b1a471f5b..850502e759 100644 --- a/CODE_COVERAGE.md +++ b/CODE_COVERAGE.md @@ -38,7 +38,7 @@ The `.profraw` file(s) can be merged by [`llvm-profdata merge`](https://llvm.org ## Implementation We use `clang++`'s source-based coverage method in our CI, as it allows running our regression tests in parallel with several workers. It is enabled by passing the `--enable-coverage=clang` flag during `configure` for all products. -The code coverage generation is done as part of the (build-and-test-all.yml)[https://github.com/PowerDNS/pdns/blob/master/.github/workflows/build-and-test-all.yml] workflow. +The code coverage generation is done as part of the [build-and-test-all.yml](https://github.com/PowerDNS/pdns/blob/master/.github/workflows/build-and-test-all.yml) workflow. Since we have a `monorepo` for three products which share the same code-base, the process is a bit tricky: