fix(build): restore unittest targets to the t7 lane (10-week silent skip) #45

Merged
triform-admin merged 3 commits from fix/t7-lane-restore-unittests into main 2026-07-30 06:29:09 +00:00

The t7 job carried build-czar 2026-05-17 opt B (worker-only targets), a build-#23-era mitigation for compile errors in cloud_browser_pcf_test.cc. Those test TUs were repaired long ago (BUILD.gn Wall #37 test_support work) and every other lane kept building the encoder+framesink unittest binaries — but t7, the lane actually used for verification builds, has been skipping them for 10 weeks.

Surfaced 2026-07-30 by the first verify-loop build of main: the worker compiled clean in 11m15s, then STEP 7 failed exit-127 on both missing test binaries — chromeless-build.sh treats absent tests as FATAL (the CHROMELESS_TESTS_NONFATAL=1 and record why guard), which is exactly the honesty this lane was quietly defeating.

A rebuild with the targets restored is running now; this PR makes the lane definition durable. t2's extra pcf_unittests target stays t2-only.

🤖 Generated with Claude Code

The t7 job carried build-czar 2026-05-17 opt B (worker-only targets), a build-#23-era mitigation for compile errors in `cloud_browser_pcf_test.cc`. Those test TUs were repaired long ago (BUILD.gn Wall #37 test_support work) and every other lane kept building the encoder+framesink unittest binaries — but **t7, the lane actually used for verification builds, has been skipping them for 10 weeks**. Surfaced 2026-07-30 by the first verify-loop build of main: the worker compiled clean in 11m15s, then STEP 7 failed exit-127 on both missing test binaries — `chromeless-build.sh` treats absent tests as FATAL (the `CHROMELESS_TESTS_NONFATAL=1 and record why` guard), which is exactly the honesty this lane was quietly defeating. A rebuild with the targets restored is running now; this PR makes the lane definition durable. t2's extra pcf_unittests target stays t2-only. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(build): restore unittest targets to the t7 lane (10-week silent skip)
Some checks failed
CI / Docs link check (pull_request) Successful in 25s
CodeQL / Analyze javascript-typescript (pull_request) Has been skipped
CodeQL / Analyze go (pull_request) Has been skipped
E2E / docker-compose + Playwright (pull_request) Has been skipped
native-peer-gate / native-peer-gate-strict (M7 gate) (pull_request) Successful in 14s
native-peer-gate / native-peer-gate-scaffold (permissive) (pull_request) Successful in 15s
CI / Container smoke test (pull_request) Successful in 1m45s
CI / Lint (pull_request) Failing after 9m24s
16b24b6ba7
The t7 job carried build-czar 2026-05-17 opt B (worker-only targets), a
build-#23-era mitigation for compile errors in cloud_browser_pcf_test.cc.
Those test TUs were repaired long ago (BUILD.gn Wall #37 test_support
work) and every other lane kept building the encoder+framesink unittest
binaries — but t7, the lane actually used for verification builds, has
been skipping them for 10 weeks.

Surfaced 2026-07-30 by the first verify-loop build of main: the worker
compiled clean in 11m15s, then STEP 7 failed exit-127 on both missing
test binaries — chromeless-build.sh treats absent tests as FATAL (the
'set CHROMELESS_TESTS_NONFATAL=1 and record why' guard), which is
exactly the honesty this lane was quietly defeating.

t2's extra pcf_unittests target stays t2-only for now.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ci: re-run — Lint's runner dind restarted mid-job (dind-gc fleet rollout 04:04-04:37Z)
Some checks failed
CI / Docs link check (pull_request) Failing after 21s
CI / Container smoke test (pull_request) Successful in 25s
CodeQL / Analyze go (pull_request) Has been skipped
CodeQL / Analyze javascript-typescript (pull_request) Has been skipped
E2E / docker-compose + Playwright (pull_request) Has been skipped
native-peer-gate / native-peer-gate-scaffold (permissive) (pull_request) Successful in 20s
CI / Lint (pull_request) Successful in 1m32s
native-peer-gate / native-peer-gate-strict (M7 gate) (pull_request) Successful in 4m48s
5ef7085374
ci: re-run — docs-check runner's dind died mid-pull (fleet rollout tail)
All checks were successful
CI / Container smoke test (pull_request) Successful in 5s
CI / Docs link check (pull_request) Successful in 10s
CodeQL / Analyze go (pull_request) Has been skipped
CodeQL / Analyze javascript-typescript (pull_request) Has been skipped
E2E / docker-compose + Playwright (pull_request) Has been skipped
native-peer-gate / native-peer-gate-scaffold (permissive) (pull_request) Successful in 18s
native-peer-gate / native-peer-gate-strict (M7 gate) (pull_request) Successful in 15s
CI / Lint (pull_request) Successful in 28m37s
87cebf03fb
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
triform/chromeless!45
No description provided.