Fleet changelogs · dev.ecs0.net
rdmpw3275m-changelog-20260916-0445-rtty-standard-closure-fixture-fix

rdmpw3275m-changelog-20260916-0445-rtty-standard-closure-fixture-fix

Resolved ISSUE-20260914-14 in RTTy by eliminating stale hardcoded test fixtures, dynamically deriving repo versions and graph entry counts, stripping comments before forbidden action checks, and re-rendering the standard trust chain.

Scope

Exact Files Touched

Changes Made

  1. standard_candidate_closure_test.py:
    • Replaced stale pre-Build 508 hand-derived fixture counts (59, 54, 1, 8) = 122 with reviewed counts (71 direct + 56 LatencyCore + 1 Network Filter + 8 RTTySyncSchema) = 136, closing the 11 compiler inputs added in Build 508 and matching compilerInputCount: 136 pinned in TrustedStandardProjectGraph.json.
  2. archive_standard_policy_test.sh:
    • Replaced hardcoded 0.3.832 / 507 in mock xcodebuild PlistBuddy and plutil calls with dynamically derived values from $root/VERSION and $root/BUILD_NUMBER.
    • Replaced hardcoded 125 and 156 compiler/build entry counts with dynamic extraction from $fixture_repo/script/TrustedStandardProjectGraph.json using /usr/bin/plutil -extract ... raw.
    • Added comment stripping (/usr/bin/sed -e 's/#.*//') before the forbidden deployment/upload/launch command regex check in $ARCHIVER and $VERIFIER, eliminating false positive failure caused by the word OPEN in line 792 comment of script/archive_standard.sh.
  3. TrustedStandardProjectGraph.json & TrustedStandardVerifierBundle.json:
    • Re-rendered via standard_project_graph.py render-graph to bind Apps/RTTyStandard/Config/Release.xcconfig sha256 (247cc62...), retaining compilerInputCount: 136 and buildInputCount: 167.
    • Re-rendered via standard_verifier_bundle.py render to seal TrustedStandardProjectGraph.json sha256 (e5bc26a...).

Commands Run & Verification Evidence

How to Undo

Outstanding Owner Actions