Logging CFT Weekly [2026-06-23]

[arsibo]

Participants

Agenda & Meeting Minutes

• Code coverage

  • exclusion commands are ignored by bazel coverage
  • take over solution applied in CFT Com (LLVM) use llvm cov for coverage and justification communication#549 in a PoC
  • open discussions on this topic
    • Coverage calculation for C++ and Rust reference_integration#259
    • Added a new reusable full-denominator C++ coverage workflow and coverage tooling (target discovery, LCOV processing, denominator validation, local runner script, and unit tests). cicd-workflows#115
  • Decision: We want to have a common solution . We want to have a CFT logging proxy in that discussion. Murathan Güzel AVL will take over that task. Please check with the group in Slack for the current status. https://sdvworkinggroup.slack.com/archives/C0B8049QTNV

• Tracking Milestones for v0.8: https://github.com/eclipse-score/score/milestone/30
  -@arsibo: generate a ticket per missing process artifact . add definition of done or link to process description

• Expectation from Tech Lead circle: Close gaps on Requirements and Architecture design. [create a ticket] - @RSingh1511

  • Requirements and Architecture Design gap closure #3008
  • Add Detailed Design documents for mw/log and datarouter #3009
  • follow up
    • process: DR-005 POC logging#52 please give feedback for the needed components
      • arc driver : QM/ASIL B; Qualification scope (project with Rust usage and without); extendability e.g. additional proprietary recorder

• Cleanup outstanding PRs automatically [Create a ticket]. General consensus is that the PR owner requests for review in slack logging channel OR logging CFT. Same goes for outstanding planned issues in: LOG - Logging FT (view). @rmaddikery @arvindr19
  Add daily maintenance workflow for stale PR logging#155

• follow up

  • @MaciejKaszynski to update the https://github.com/eclipse-score/logging/pull/136/changes to include stats as PoC which can be used as a basis for REQ traceability.

Info

• PR will be rejected due to CI time out of QNX 8
  https://sdvworkinggroup.slack.com/archives/C0894QGRZDM/p1780058512257829 => check for status with Alexander Lanin would it be possible to trigger the re run by a developer?
  Follow-up: https://github.com/orgs/eclipse-score/discussions/2508#discussioncomment-16990977
  Status: open, in discussion with blackberry

• Internal API was leaked and will be fixed by a proper Public API
  change visibility of private interface and introduce a public interface
  Move the file | runtime.h/.cpp → detail/ folder | Correct location matches the detail namespace |
  Block direct access | Restrict visibility in Bazel | Build will fail if anyone tries to depend on it from outside |
  Give a public alternative | Add public API to logging.h | Teams have a safe, supported function to call |
  Status: ongoing

• AoB

  • https://sdvworkinggroup.slack.com/archives/C089XP2PGQ