Wait 90 minutes for the tap, not 30 #8

Merged
Cody Bryant merged 1 commit from fix/outlast-a-slow-publish into main 2026-08-25 12:35:16 -07:00
Owner

build-bottles.sh waits for publish.yml first tap pass; publish second pass then waits for the bottles built here. That handshake is correct. The BUDGET was not: 90 x 20s = 30 minutes, against a publish measured at 37m18s. The tap appeared 60 seconds after the loop gave up, and a release lost its bottles and the install matrix that waits on them.

Now 270 x 20s = 90 minutes. Widening is close to free: the loop breaks the moment the formula appears, so this is a FAILURE bound rather than a delay.

This applies to stable as much as to candidates - bottles.yml triggers on v*.. - and stable publish does more before the tap pass while a stable tag is permanent.

Both consumers gain a repo-local invariant failing under a 60-minute budget, mutation-tested against fewer iterations AND a shorter sleep.

`build-bottles.sh` waits for publish.yml first tap pass; publish second pass then waits for the bottles built here. That handshake is correct. The BUDGET was not: 90 x 20s = 30 minutes, against a publish measured at 37m18s. The tap appeared 60 seconds after the loop gave up, and a release lost its bottles and the install matrix that waits on them. Now 270 x 20s = 90 minutes. Widening is close to free: the loop breaks the moment the formula appears, so this is a FAILURE bound rather than a delay. This applies to stable as much as to candidates - bottles.yml triggers on v*.*.* - and stable publish does more before the tap pass while a stable tag is permanent. Both consumers gain a repo-local invariant failing under a 60-minute budget, mutation-tested against fewer iterations AND a shorter sleep.
fix(bottles): wait 90 minutes for the tap, not 30 (publish took 37m18s to write the formula for one release and the tap appeared 60s after the loop gave up, costing that candidate its bottles)
All checks were successful
CI / Shell scripts (pull_request) Successful in 3s
CI / The standard can actually be vendored (pull_request) Successful in 14s
CI / Lint and test the standard's own code (pull_request) Successful in 21s
3ad2ad43e2
Sign in to join this conversation.
No reviewers
No labels
No milestone
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
SisyphusMD/project-standard!8
No description provided.