fix(operator): the merge train must not skip a car whose Build is alive #2073

Merged
pipeline-bot merged 1 commit from fix/train-slow-ci into trunk 2026-08-19 08:21:18 +00:00
Owner

Kaizen improvement 3 (found live: sf40 linux#33 skipped at 20m while its kernel bake was healthy at minute 20). Live Build extends to a 60m hard ceiling; absent/terminal still times out at 20m. Pure-helper decision + 7-case table test.

Kaizen improvement 3 (found live: sf40 linux#33 skipped at 20m while its kernel bake was healthy at minute 20). Live Build extends to a 60m hard ceiling; absent/terminal still times out at 20m. Pure-helper decision + 7-case table test.
fix(operator): the merge train must not skip a car whose Build is alive
All checks were successful
pipeline/ci CI green @ a5e4d0f8c8f2
a5e4d0f8c8
Slow CI is not absent CI. The 20m integration deadline exists so a
change whose CI NEVER REPORTS cannot hold the train — but the kernel
bake runs 21-35 minutes and twice outlived it (builder-images change
105 on 2026-08-18, linux change 33 on 2026-08-19), each time skipping
a healthy car as "ci-timeout" and leaving trunk already-tagged.

stepAwaitCI now distinguishes: a Build that EXISTS and is not terminal
extends the wait to a harder 60m ceiling; a missing or terminal
non-releasable Build still times out at 20m; a hung executor still
cannot hold the train (and every car behind it) past 60m. The decision
is a pure helper with a 7-case table test.
pipeline-bot force-pushed fix/train-slow-ci from a5e4d0f8c8
All checks were successful
pipeline/ci CI green @ a5e4d0f8c8f2
to 212d11295d
All checks were successful
pipeline/ci CI green @ 212d11295d16
2026-08-19 08:19:02 +00:00
Compare
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
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
sean/pipelines!2073
No description provided.