beads/.github/workflows
Jim Wordelman 6e36c3f19c
ci: raise proxied Dolt cmd test job timeout, add step timeout, refresh shard manifest (#6689)
* ci(proxied-cmd): green — give the proxied-shard job its own step timeout, refresh manifest (refs be-bruke)

The job-level timeout-minutes was the only backstop for the "Test
proxied-server cmd shard" step, and it counts the "Download binaries"
step too — so a slow download alone could exhaust the job budget and
kill an otherwise-healthy shard's test run with no way to tell the two
failure modes apart. Give the test step its own 16m timeout inside the
existing 30m job budget, and regenerate the bin-packed shard manifest
via scripts/ci/gen_proxied_shard_manifest.py so it stays in sync with
the current TestProxiedServer* set (0 drift, all 15 shards fallback:0).

* ci(proxied-cmd): mirror the shard timeouts onto the main lane, regen the manifest at the adoption base

Adoption review of #6689, iteration 1 — three minor findings, applied here
rather than deferred.

main.yml's `test-proxied-cmd` is the same job as pr-risk.yml's twin — same
proxied-test-shard.sh, same manifest, same total 15 — behind a
download/verify step inside a 20m budget with no step timeout, so the exact
ambiguous-timeout failure mode this PR removes from the PR lane survived on
the post-merge lane, which is where triage happens with nobody watching.
Mirror both edits (job 20m -> 30m, step 16m) and record the ordering at the
step, since it is not obvious from the site that 16m is deliberately below
the script's own -test.timeout=15m plus setup.

The manifest's only record of the cost proxy's two known blind spots lived
in a hand-written comment block the regeneration deleted:
TestProxiedServerListSortRetiresTheWalk seeds 1400 rows and walks the
listing three ways off a single init, and TestProxiedServerServeReadParity
is the CLI/HTTP read-parity oracle whose presence in this gate-required lane
is what makes the anti-drift claim enforced. Re-adding prose to a generated
file would just be deleted again, so it moves into the generator's emitted
header.

Base drift since authoring left the refreshed manifest one test stale —
#6584 added TestProxiedServerBackupRefusedOnExternalTopology, which
hash-distributed to shard 14 — so "0 drift, all 15 shards fallback:0" was
already false on the merge base. Benign (unlisted tests hash-distribute and
still run, and drift removed no name, so the strict parser's stale-entry
hard-fail was unreachable), but the stated deliverable did not hold.
Regenerated at the adoption base: 149 of 149 discovered tests listed,
fallback:0 on every shard, peak load unchanged at 39 estimated inits. That
figure is a point-in-time measurement, not an invariant: nothing in CI diffs
the committed manifest against a regeneration, so it re-drifts the moment
the next TestProxiedServer* lands. A freshness step
(`gen_proxied_shard_manifest.py 15 | diff - <manifest>`) on a lane already
triggered by .github/scripts/* would make it one; that is follow-up scope.

Verified: the generator reproduces the committed manifest byte-identically;
BEADS_TEST_SHARD_LIST_ONLY=1 across all 15 shards assigns all 149 discovered
TestProxiedServer* functions exactly once with no duplicates or orphans;
actionlint clean on both workflows.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Julian Knutsen <julianknutsen@users.noreply.github.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-09-26 07:17:03 -07:00
..
ci-measurements.yml Merge release/1.3.0 into main (post-tag forward-port) 2026-09-15 22:09:13 +00:00
close-stale-needs.yml ci: add needs-triage inbox labeling (mirrors gastownhall/gascity) (#6622) 2026-09-19 14:37:19 -07:00
conformance.yml release: prep v1.3.0 — version bump, changelog rollup, release process docs, formula fixes (#6038) 2026-08-30 22:19:35 -07:00
cross-version-smoke.yml release: prep v1.3.0 — version bump, changelog rollup, release process docs, formula fixes (#6038) 2026-08-30 22:19:35 -07:00
deploy-pages-redirect.yml build(deps): bump actions/checkout from 7.0.0 to 7.0.1 (#5016) 2026-07-25 08:52:22 -07:00
docs-autofix.yml build(deps): bump actions/checkout from 7.0.0 to 7.0.1 (#5016) 2026-07-25 08:52:22 -07:00
docs-mintlify.yml build(deps): bump the actions group across 1 directory with 3 updates (#5059) 2026-07-25 19:05:02 -07:00
main.yml ci: raise proxied Dolt cmd test job timeout, add step timeout, refresh shard manifest (#6689) 2026-09-26 07:17:03 -07:00
migration-test.yml test(migration): wisp-plane upgrade corpus — seed and assert the ignored-plane classes the 1.3.0 chain depends on (#6049) 2026-08-28 23:24:39 -07:00
nightly.yml fix(ci): pin the Dolt CLI — 2.3.0 broke DOLT_RESET on fresh databases (ga-m0dlk) (#5894) 2026-08-20 20:59:27 -07:00
nix-build.yml chore(deps): bump DeterminateSystems/determinate-nix-action (#6042) 2026-09-02 17:41:12 -07:00
pr-risk.yml ci: raise proxied Dolt cmd test job timeout, add step timeout, refresh shard manifest (#6689) 2026-09-26 07:17:03 -07:00
pr.yml Merge release/1.3.0 into main (post-tag forward-port) 2026-09-15 22:09:13 +00:00
proxied-local-smoke.yml test(tracker): add real UOW proxy conformance fixture (#6445) 2026-09-23 02:19:18 -07:00
regression.yml release: prep v1.3.0 — version bump, changelog rollup, release process docs, formula fixes (#6038) 2026-08-30 22:19:35 -07:00
release.yml fix: bound and retry apt-get calls in CI to avoid unbounded 15-minute job timeout (#5810) 2026-08-19 11:47:22 -07:00
remove-needs-info.yml ci: add needs-triage inbox labeling (mirrors gastownhall/gascity) (#6622) 2026-09-19 14:37:19 -07:00
remove-needs-triage.yml ci: add needs-triage inbox labeling (mirrors gastownhall/gascity) (#6622) 2026-09-19 14:37:19 -07:00
request-needs-info.yml ci: add needs-triage inbox labeling (mirrors gastownhall/gascity) (#6622) 2026-09-19 14:37:19 -07:00
test-pypi.yml build(deps): bump the actions group across 1 directory with 3 updates (#5059) 2026-07-25 19:05:02 -07:00
triage-label.yml ci: add needs-triage inbox labeling (mirrors gastownhall/gascity) (#6622) 2026-09-19 14:37:19 -07:00
update-flake-lock.yml chore(deps): bump DeterminateSystems/determinate-nix-action (#6042) 2026-09-02 17:41:12 -07:00
update-vendor-hash.yml chore(deps): bump DeterminateSystems/determinate-nix-action (#6042) 2026-09-02 17:41:12 -07:00