Skip to content

Bump score_coverage to 0.2.0 - #589

Merged
4og merged 1 commit into
mainfrom
dcalavrezo_score_coverage_020
Sep 16, 2026
Merged

4og merged 1 commit into
mainfrom
dcalavrezo_score_coverage_020

Conversation

@dcalavrezo-qorix

Copy link
Copy Markdown
Contributor

What

Bumps score_coverage 0.1.0 -> 0.2.0 (registry release of
https://github.com/eclipse-score/coverage_tool) and refreshes MODULE.bazel.lock.
No other change; the scope, reporter wrapper and justification file from #584
stay as they are.

Why

The first reports produced by #584 with 0.1.0 showed four problems in the tool
(reported in #558 comments and eclipse-score/coverage_tool#5). 0.2.0 fixes them:

Problem seen on baselibs 0.1.0 0.2.0
OpenSSL headers counted as baselibs code (the third_party/openssl wrapper forwards the library's CcInfo) 72 rows at 0 % 0
Index links to pages that were never generated (bazel-out/.../_virtual_includes/..., external/...) 94 dead links 0
futurecpp headers compiled through futurecpp_internal not attributed to the library 0 headers in the report 109 headers with data
Libraries with a placeholder .cpp next to real sources lost their 0 % baseline (llvm-cov rejects the whole archive) 431 files with baseline 446

File names are now source paths: the vendored flatbuffers headers appear as
external/flatbuffers+/include/flatbuffers/*.h instead of the generated
_virtual_includes/ path.

New in 0.2.0: unmapped_files.txt in the coverage artifact and a section in
the job summary list the in-scope files for which no coverage data exists
anywhere, categorised (no-data findings; declaration-only headers;
placeholder sources compiled-without-code). On the whole tree baselibs has
134 no-data files, 65 of them futurecpp templates no test instantiates,
buffer_ref.h among them. Release notes:
https://eclipse-score.github.io/coverage_tool/main/release/release_notes.html

Verification

Whole tree with the 0.2.0 code, bazel coverage --config=llvm_cov --build_tests_only -- //score/...
with the CI exclusions, 300 tests: 640 files in the report, every index link
opens, 0 external/openssl+ rows, 0 machine or configuration paths, raw line
coverage 87.76 %.

Against the registry release exactly as pinned here (no local override,
--lockfile_mode=error) on //score/hash/... //score/flatbuffers/... //score/language/futurecpp/...,
88 tests: 554 index links, all open; 15 flatbuffers and 109 futurecpp headers
with data; unmapped_files.txt present with the three categories.

0.2.0 carries the fixes found on this repository's first reports
(eclipse-score/coverage_tool#5):

- headers of the forwarded OpenSSL library no longer count as baselibs
  code (72 external/openssl+ rows gone);
- every row of the HTML report opens; files are named by their source
  path, the flatbuffers headers as external/flatbuffers+/include/...;
- headers the futurecpp tests compile through futurecpp_internal are
  attributed to the library's declared headers (109 headers recovered);
- library archives with a placeholder object no longer lose the 0 %
  baseline of their other files (15 files recovered);
- in-scope files without any coverage data are listed in
  unmapped_files.txt and the job summary, categorised.

Lockfile refreshed with bazel mod deps --lockfile_mode=update.

Signed-off-by: Dan Calavrezo <195309321+dcalavrezo-qorix@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-589: https://eclipse-score.github.io/baselibs/pr-589/

@github-project-automation github-project-automation Bot moved this from In Progress to On Hold in BAS - Baselibs FT Sep 16, 2026
@4og
4og added this pull request to the merge queue Sep 16, 2026
Merged via the queue into main with commit e3354f5 Sep 16, 2026
27 checks passed
@4og
4og deleted the dcalavrezo_score_coverage_020 branch September 16, 2026 16:04
@github-project-automation github-project-automation Bot moved this from On Hold to Done in BAS - Baselibs FT Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bazel Bazel and Starlark build files

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants