Repository navigation
ci: use larger GitHub runners for Rust and browser journeys - #3090
Merged
Merged
Conversation
Signed-off-by: James Kraus <jamespkraus@gmail.com>
jameskraus
marked this pull request as ready for review
November 9, 2026 14:52
dr0uleau
approved these changes
Nov 9, 2026
dr0uleau
left a comment
Contributor
There was a problem hiding this comment.
🤖 approved at the checked commit. current CI passes
kazemek21
approved these changes
Nov 9, 2026
kazemek21
left a comment
Contributor
There was a problem hiding this comment.
🤖 Kyle reviewed this PR and the Nexus review-tracker notes and approves.
Posted by Codex (gpt-6.1-sol) on behalf of kylez.
baxen
added a commit
that referenced
this pull request
Nov 10, 2026
…3090)" (#3180) Reverts #3090, moving Rust/tool integration and browser journeys back to standard `ubuntu-24.04` runners. **Why:** each CI run now asks the shared `ubuntu-x86-runners` pool for 28 runners at once (1 Rust + 9 Chromium + 18 WebKit). The pool can't keep up: - Since the merge, the Rust job typically waits **20–55 minutes** to get a runner. Before, it started immediately. - In the queued runs sampled, 20+ of the 27 browser shards were still waiting after 20–45 minutes. - Jobs on standard runners in those same runs (JavaScript, flake checks, macOS) started within ~3 seconds. - Renovate makes this worse: 108 of the 208 CI runs since 16:00 PT were Renovate rebases, and each one asks for 28 large runners. The larger runners did make each job faster (Rust 13.5 → 7 min), so a narrower version, such as only Rust on the large pool, could come back later. Co-authored-by: ART <ea39c1c8acf57180161ef4ba4ed68abf8589f5291956b909a5aa991fc66664ca@buzz.block.builderlab.xyz>
gilgtm
added a commit
that referenced
this pull request
Nov 10, 2026
…nt-progress-rows * origin/main: Revert "ci: use larger GitHub runners for Rust and browser journeys (#3090)" (#3180) Show Goose's unset thinking level as Default, not Off (#3124) ci(release): publish stable and beta desktop releases from v tags (#3150) fix(messages): end the New messages hold when no repair can sample (#3169) Signed-off-by: Gil Birman <gil@squareup.com>
damienrj
added a commit
that referenced
this pull request
Nov 10, 2026
…rminal-font-picker * 'main' of https://github.com/block/buzz-app: (168 commits) Unify Membership sharing and live roster updates (#3147) fix(activity): show one working cue per agent request (#3166) Introduce opt-in first-agent setup (#2804) fix(codex): drop the security-review sign-in prompt from harness defaults (#3188) feat(releases): publish desktop download manifest (#3154) fix(mcp): preserve current attachments across edits (#2937) fix(agents): call the Claude and Codex first-run download "the integration" (#3165) chore(goose): bump bundled goose-acp to v1.58.1 (#3161) Revert "ci: use larger GitHub runners for Rust and browser journeys (#3090)" (#3180) Show Goose's unset thinking level as Default, not Off (#3124) ci(release): publish stable and beta desktop releases from v tags (#3150) fix(messages): end the New messages hold when no repair can sample (#3169) fix(search): make Command F search the Bestie conversation (#3084) fix(plugins): keep failed update checks on the plugin's Settings row instead of a toast (#3088) Show single-agent Stop on the activity bubble (#3140) fix: support explicit hosted browser origins (#3149) fix: keep Codex tool namespace descriptions bounded (#3128) fix(messages): show "New messages" in channels longer than one page (#3071) Keep shared agent guidance generic (#3134) fix(typing): a thread reply also ends the agent's channel-level typing (#3148) ... Signed-off-by: damienrj <damien@squareup.com> # Conflicts: # src-tauri/Cargo.toml
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
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.
Move Rust/tool integration and browser journeys to Block's existing 16-core
ubuntu-x86-runnerspool. Test commands, coverage, sharding, workers, and measurement runners are unchanged.One paired trial passed with matching test counts:
Larger-runner trial compute cost approximately $1.01. These are preliminary results; full-matrix CI, repeatability, and human testing remain pending. Autoreview and local hooks passed.
Before/after full CI: standard runners vs. this PR. Blue jobs changed pools; all timelines use the same scale. Different PRs, so this is an observed comparison rather than a controlled benchmark.