ci(e2e): install bun from npm instead of apt unzip plus setup-bun - #3407
Merged
Conversation
The e2e shards ran apt-get update inside the Playwright container to get unzip for oven-sh/setup-bun. That fetch pulled ~30 MB of Ubuntu package indexes on every shard, crawled to the 12-minute job timeout often enough to be the top cause of red e2e gates in the 2026-09 audit, and surfaced as "cancelled" shards rather than a failed step. The npm bun package resolves a platform package that carries the binary, so the shard now touches only the registry bun install already depends on, capped at 2 minutes. bun lint now checks the e2e workflow's bun@ pin against test-unit.yml the same way it checks the Dockerfiles. Adds docs/CI-CD/ci-audit-2026-09.md with the before numbers. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
tyler-dane
marked this pull request as ready for review
September 5, 2026 14:44
tyler-dane
added
the
agent-automerge
tyler-dane
enabled auto-merge
September 5, 2026 14:44
This was referenced Sep 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: no issue. Follow-up to the manual rerun PR #3388 needed on e2e run 33938967483.
What and why
The e2e shards ran
apt-get update && apt-get install unzipinside the Playwright container sooven-sh/setup-buncould unzip Bun on a cache miss. That fetch pulled ~30 MB of Ubuntu package indexes fromarchive.ubuntu.comon every shard. In the newest 100 e2e runs it had a p50 of 6s, a p95 of 47s, and an unbounded tail: all 10 rede2egates in that window were shards cancelled by the 12-minute job timeout while still inside that step, which is why the failure read as "cancelled" instead of a failed step.This replaces the apt step and
setup-bunwithnpm install --global bun@1.3.14, capped at 2 minutes. The npmbunpackage resolves a platform package that carries the binary, so the shard now touches only the registrybun installalready depends on and no Ubuntu mirror.bun lintnow checks the e2ebun@pin against thebun-versionpin intest-unit.yml, the same way it checks the Dockerfiles.Also adds
docs/CI-CD/ci-audit-2026-09.mdwith the before numbers for the whole audit (per-job p50/p95, failure split, shard balance, tests that passed only on retry). Follow-up PRs land the other fixes and append to its change log.Verify
The three failing tests are
agent-loop-next pickerand twoagent-loop launch quota recoverycases, all with.github/scripts/agent-loop-next.sh: line 21: mapfile: command not found. That is macOS/bin/bash3.2 lacking a bash 4 builtin; those scripts and tests are not touched by this diff and pass on the Linux runner. The other 116 scripts tests, type-check, lint (including the new pin check), and knip pass locally. CI on Linux is the arbiter for this PR, and this PR's own e2e run exercises the new install step directly.🤖 Generated with Claude Code