[dcalavrezo-qorix]

Bumps score_coverage to 0.4.2 (release notes), the release that fixes eclipse-score/coverage_tool#40: the own sources of a cc_binary, here launch_manager's main.cpp, are listed in the report at 0 % instead of under no-data in unmapped_files.txt, and baseline-only files are rendered in their own HTML run so an executable's main cannot pick up a test binary's counts. The temporary git_override used for validation is gone.

Also adds coverage:gcov --host_cxxopt=-O0: the scope's baseline .gcno notes of untested files are built in the exec configuration with the host options; without it GCC optimises them and their line tables differ from the -O0 test builds (user manual step 4b).

Validation with the override, Linux coverage run 38912573302: main.cpp at 0 of 3 lines in the HTML index and the LCOV, totals include it, effective line coverage 81.88 %. Expect the effective figure to be slightly below the previous report, since the untested binary source now counts.

[dcalavrezo-qorix]

Result of the Linux coverage job (run 38887734269): score/launch_manager/src/daemon/src/main.cpp is now in the report at 0 % (3 lines) and no longer listed in unmapped_files.txt (no-data 31 → 30). That is the behaviour coverage_tool#44 adds; this PR stays a draft until 0.4.2 is released, then the git_override goes and the version bump plus the --host_cxxopt=-O0 line remain.

[NicolasFussberger]

@dcalavrezo-qorix thanks for investigating the issue.

I checked the resulting coverage report from the pipeline and the main.cpp file is removed from unmapped_files.txt and now part of the coverage report.
However, it is shown with 100% coverage which is unexpected since we do not have a test for this file.

[github-actions]

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