Logging CFT Weekly [2026-07-14]

[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 => valid_from/valid_until for Stakeholder Requirements shall be set => will filed out in an additional meeting
      https://eclipse-score.github.io/reference_integration/main/status_dashboard.html
      • rename relations for SysML compatibility process_description#618
      • feat: remove satisfies for feat_req/comp_req docs-as-code#616
    • needjson : 06.07.2026 : https://github.com/eclipse-score/reference_integration/blob/b2ae7912b2ddd12861fbc6e48008477c2e032abc/BUILD#L18
      • what means duplicate label in this context https://github.com/eclipse-score/reference_integration/blame/b2ae7912b2ddd12861fbc6e48008477c2e032abc/BUILD#L18 => @arsibo 14.07.2026 will be clarified after Alexander Lanin is back
    • 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
      • 06.07.2026:
        • https://eclipse-score.github.io/reference_integration/main/status_dashboard.html
        • Release v0.8 common checklist #3040
        • https://eclipse-score.github.io/reference_integration/main/integration_process/integration_process.html
      • 07.07.2026
        • [testing] bumps score_logging to v0.2.1 reference_integration#279 work in progress . After that Ragha will release a new version
        • Ragha will check Release v0.8 common checklist #3040
      • 14.07.2026
        • logging release availible https://github.com/eclipse-score/logging/releases/tag/v0.2.2
        • status check list Release v0.8 common checklist #3040 (comment)
        • @arsibo clarification about DocsAsCode update to 4.6.1 is required

  • v0.9 topics

    • Consolidate mw/log design documentation into docs/ logging#187
    • See check list Release v0.8 common checklist #3040 (comment)
    • @arsibo generate a folder structure for the components log_frontend; log_backend; datarouter
    • @arsibo check with the process community about the usage of mw folder . mw has also a meaning of a stateful component (Markus Bechter / Andrej knows about that)

• Fix GCC 14 Warnings logging#172 Ragha will check it

• 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
  • 07.07.2026: no update
  • 14.14.2026: PR available but not merged 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)
  -07.07.2026: blocked due to definition of components
  -14.07.2026: Components are defined mw/log frontend; mw/log backend; datarouter
  folder names log_frontend; log_backend; datarouter

• Component Requirements: @hoppe-and-dreams will check for deltas compared to the previous export

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

  • https://github.com/eclipse-score/score/issues/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.
  • 07.07.2026: PR is ready. Ragha will run the test
  • 14.07.2026: PoC is done Requirement Reports: https://eclipse-score.github.io/logging/main/logging/stats.html

• 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 => needs to be done but no capacity until 0.8 release for that topic ???
    • 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

• AoB

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

[hoppe-and-dreams]

Component Requirements -> No update, since last export.