[eclipse-score-bot]

This PR contains the following updates:

Package	Type	Update	Change
score_coverage	bazel_dep	minor	0.3.1 → 0.4.1

---

Release Notes

eclipse-score/coverage_tool (score_coverage)

v0.4.1

What's Changed

• reporter: read llvm-cov names displayed relative to the root by @​dcalavrezo-qorix in #​36
• docs: date the 0.4.1 release notes by @​dcalavrezo-qorix in #​37

Full Changelog: eclipse-score/coverage_tool@v0.4.0...v0.4.1

In plain words

Measuring system headers no longer empties the report. Headers that a
library publishes through includes = [...] reach the compiler as system
headers, and clang records no coverage for functions defined in system
headers unless the build adds -mllvm -system-headers-coverage. With that
flag the data also contains real system headers such as
/usr/include/c++/..., and llvm-cov then prints every file name relative to
/. The reporter did not recognise the names in that form, treated every
in-scope file as untested and let the out-of-scope system headers into the
report. Found on qorix_middleware, where the flag is needed for the public
headers of every component. Without the flag nothing changes: the reporter
takes the same path as in 0.4.0.

Details for integrators

• get_covered_files restores the leading slash when llvm-cov report
  displays names relative to the root, and keeps files outside the workspace
  absolute so the exclusion filter matches them (unit test with such a
  table).
• User manual step 4: when libraries publish headers through includes, add
  --copt=-mllvm --copt=-system-headers-coverage to the coverage config;
  without it those headers show as uncovered or no-data. The real system
  headers the flag instruments stay out of the report through the scope.
  Known-problems entry added.
• Validation on qorix_middleware with the flag: 307 headers newly measured,
  no file lost coverage, line coverage 12.37 % to 17.11 %.

v0.4.0

What's Changed

• Evaluate the coverage scope for the run's platform by @​dcalavrezo-qorix in #​24
• Add downstream coverage workflow tests by @​AlexanderLanin in #​22
• Consolidate tests under a common directory by @​AlexanderLanin in #​31
• Set up end-to-end pytest with CI and requirement traceability by @​AlexanderLanin in #​33
• ci: run formatting checks through pre-commit using devcontainer tools by @​AlexanderLanin in #​32
• ci: use the shared tools copyright hook by @​AlexanderLanin in #​34
• docs: clarify coverage architecture artifacts by @​dcalavrezo-qorix in #​13
• docs: clarify coverage architecture for readers by @​AlexanderLanin in #​18
• chore(docs): update score_docs_as_code gitignore configuration in #​21

Full Changelog: eclipse-score/coverage_tool@v0.3.1...v0.4.0

In plain words

The QNX report now shows QNX code, not Linux code. The first QNX report
of baselibs listed the Linux-only files at 0 % and did not contain the
QNX-only files at all. Cause: Bazel evaluates the list of files to measure
for the machine the tool runs on, not for the platform the tests run on. A
scope can now name its platform, and a QNX run gets a scope of its own that
says so. Everything that is not platform-specific was already measured
correctly. Linux-only consumers are not affected and need no change.

Details for integrators

• score_coverage_scope gains platform: the label the run passes as
  --platforms. The transition on the scope rule sets --platforms next to
  --collect_code_coverage, so the traversal, the baseline objects, the gcno
  notes and a select() in the scope's own deps are those of the target
  platform. Without platform nothing changes (issue #​23).
• Declare one scope per platform and point the gcov reporter at the QNX one
  (user manual, steps 3 and 4b):

score_coverage_scope(
    name = "coverage_scope_qnx",
    testonly = True,
    platform = "@score_bazel_platforms//:x86_64-qnx-sdp_8.0.0-posix",
    tags = ["manual"],
    deps = SCOPE_DEPS,
)

• Roots that exist on one platform only must sit behind a select() in the
  scope's deps. A root that is incompatible with the platform does not fail
  loudly: Bazel marks the scope, the report generator and every test
  incompatible, and bazel coverage executes no test and writes no report.
  The manual documents the diagnostic (bazel build --config= --collect_code_coverage //tools/coverage:coverage_scope_qnx prints the
  dependency chain) and the known problem is listed (ERR-14).
• Tag a platform scope manual, like the gcov reporter, so wildcard builds on
  the host do not analyse it for a platform whose toolchains are not
  registered.
• Qualification: new requirement tool_req__coverage_scope_platform, two
  analysis tests and platform-selected libraries in the end-to-end workspace,
  measured as the host variant by the LLVM run and as the target variant by
  the gcov run. Verification report updated.
• Repository layout: tests now live under tests/unit, tests/end_to_end and
  tests/downstream; an end-to-end pytest target runs in CI with requirement
  metadata, and the downstream tests exercise the real baselibs and lifecycle
  coverage workflows against the checkout. Formatting and copyright checks run
  through pre-commit with the shared S-CORE hooks. None of this changes the
  consumer API or the published Bazel module content.

Known limitation

Platform-only roots still have to be listed per platform in the consumer's
scope. A scope computed from a target pattern, where Bazel drops incompatible
targets itself, is under discussion for a later release.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by #infrastructure automation. Contact us if you have any questions or feedback.

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: b3babf0f-6fd8-4fd1-8f0b-7da96a8bc5f8
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 4 packages loaded
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:license-check': no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
INFO: Elapsed time: 15.432s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

[eclipse-score-bot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: MODULE.bazel.lock

Command failed: bazel mod deps --lockfile_mode=update
Starting local Bazel server (8.6.0) and connecting to it...
 no actions running
 no actions running
 no actions running
 no actions running
 no actions running
 no actions running
 no actions running
WARNING: Download from https://github.com/eclipse-score/devcontainer/archive/refs/tags/v1.11.1.tar.gz failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException Checksum was sha256-XhiGdP4K7IVUADCqAxURtnK6wpFTt1JsL+Jn9Xl/Md4= but wanted sha256-B9caGwH1Ff/asDuyQBEwE8KRRYIozv4NYwdwChraNwY=
INFO: Repository score_devcontainer+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/a80e41adaca880de67f679046093c85f/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
ERROR: /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/a80e41adaca880de67f679046093c85f/external/bazel_tools/tools/build_defs/repo/http.bzl:156:45: An error occurred during the fetch of repository 'score_devcontainer+':
   Traceback (most recent call last):
	File "/tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/a80e41adaca880de67f679046093c85f/external/bazel_tools/tools/build_defs/repo/http.bzl", line 156, column 45, in _http_archive_impl
		download_info = ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://github.com/eclipse-score/devcontainer/archive/refs/tags/v1.11.1.tar.gz] to /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/a80e41adaca880de67f679046093c85f/external/score_devcontainer+/temp14508748427923696269/v1.11.1.tar.gz: Checksum was sha256-XhiGdP4K7IVUADCqAxURtnK6wpFTt1JsL+Jn9Xl/Md4= but wanted sha256-B9caGwH1Ff/asDuyQBEwE8KRRYIozv4NYwdwChraNwY=
 no actions running
 no actions running
 no actions running
 no actions running
 no actions running
 no actions running
 no actions running
 no actions running
ERROR: no such package '@@score_devcontainer+//tools': java.io.IOException: Error downloading [https://github.com/eclipse-score/devcontainer/archive/refs/tags/v1.11.1.tar.gz] to /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/a80e41adaca880de67f679046093c85f/external/score_devcontainer+/temp14508748427923696269/v1.11.1.tar.gz: Checksum was sha256-XhiGdP4K7IVUADCqAxURtnK6wpFTt1JsL+Jn9Xl/Md4= but wanted sha256-B9caGwH1Ff/asDuyQBEwE8KRRYIozv4NYwdwChraNwY=

[eclipse-score-bot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[eclipse-score-bot]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.