Logging CFT Weekly [2026-06-30]

[arsibo]

Participants

Agenda & Meeting Minutes

• topics from TL & Communities & CFTs meeting => topics will be clarified today via slack

  • https://github.com/orgs/eclipse-score/discussions/434?sort=new#:~:text=Status,-of%20v0.8%20/%20%22Code
    • req related to ???
      • rename relations for SysML compatibility process_description#618
      • feat: remove satisfies for feat_req/comp_req docs-as-code#616
    • needjson
    • ref int see https://eclipse-score.github.io/score/main/design_decisions/DR-008-int.html
      • Release candidate 07 reference_integration#219
      • [Test] score_logging integration - Bumps score_logging to v0.2.1 reference_integration#216
      • check is the dependency chain running on the last logging version

• 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
  • 30.06.2026: ongoing see Surface untested source files at 0% coverage in reports score_cpp_policies#9

• 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
  -30.06.2026: Agreement on Feature Arc required first. (see next point)

• 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

• 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.

• Release V0.8 topics

  • Pre release
  • Integration in Reference integration repo see first point
  • how to handle the log rust bridge (QM)? Logging for S-CORE Release v0.8 #2883 = > @arkjedrz will check this point
    • Detailed Design
    • Implementation Inspection
    • Unit Tests
    • C0/C1 Coverage
    • Component Integration Tests
    • Feature Integration Tests
    • Static Code Analysis findings
    • Dynamic Code Analysis findings

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, 1 PR merged in baselib

• AoB

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

[arkjedrz]

@arsibo
Regarding score_log_bridge - those process artifacts will be needed, but are they required for next releases?
QORIX doesn't have the bandwidth to handle that currently, but support from other parties is welcome.