Skip to content

ci(cmux-next): the landing DEV compile never overflows to Blacksmith macOS - #31600

Merged
teamleaderleo merged 1 commit into
feat-cmux-nextfrom
lane/dev-compile-no-blacksmith-macos
Nov 2, 2026
Merged

teamleaderleo merged 1 commit into
feat-cmux-nextfrom
lane/dev-compile-no-blacksmith-macos

Conversation

@teamleaderleo

Copy link
Copy Markdown
Collaborator

Leo-ask: ask-6ebdd36a0d

Leo: "...Now the 12-core option is only used when nothing else is waiting for Blacksmith Macs." but we have the fleet we have linux blacksmith... why are we STILL TALKING ABOUT BLACKSMITH MACOS

What changed

Every feat-cmux-next landing compiles the DEV Release app (dev-landing-compile) on the owned Mac whose host tree is nearest. When no owned Mac was free for about two minutes, it overflowed to blacksmith-12vcpu-macos-26. That is the 12-core label from Leo's quote, which also started nothing for about a day on 2026-10-28 and again on 2026-10-30. Now it overflows nowhere:

  • scripts/ci/dev_landing_place.py: with no owned Mac free after the wait, with owned pools off, or with the runners unreadable, it prints an empty runs_on and pool=none. overflow_label() and the snapshot read are gone.
  • cmux-next.yml: dev-landing-compile runs only when the placement chose a runner. OVERFLOW_LABEL is removed.

Why skipping costs nothing: a landing compile exists to warm a host tree for the next landing. A Blacksmith VM keeps no tree, and the DEV run compiles that commit on its own route anyway. The DEV daily placement (place_daily) is unchanged.

Risk: low. If no owned Mac is free, a landing just has no early compile. A skipped job blocks nothing downstream.

Changelog

none

Observed / Not run

Ran on the head: tests/test_dev_landing_place.py (22 OK), tests/test_cmux_next_dev_landing_workflow.py (7 OK), tests/test_nightly_sign_runner.py (49 OK). Not observed yet: a real landing that finds no owned Mac free.

🤖 Generated with Claude Code

Agent session: agent session

…macOS

With no owned Mac free after about two minutes (or owned pools off, or the
runners unreadable), dev_landing_place.py now places nothing and
dev-landing-compile is skipped, instead of sending the compile to
blacksmith-12vcpu-macos-26. A landing compile exists only to warm a host
tree for the next landing; a Blacksmith VM keeps none, and the DEV run
compiles the commit on its own route anyway.

Leo-ask: ask-6ebdd36a0d

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Agent-Session: https://cmux.com/deeplink/agent?id=aid-0b2db51297212290ca7f
@github-actions

github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

cmux status (one comment, edited in place; each line is updated by the job that owns it)

Review 094b954: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr31600 -f ref=lane/dev-compile-no-blacksmith-macos -f platform=macos -f backend_mode=local

Shipped in:

@github-actions github-actions Bot added the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026
@teamleaderleo

Copy link
Copy Markdown
Collaborator Author

Review (subagent claude-opus-5-5 medium): SHIP at 094b954
Follow-ups: the unreachable blacksmith-6vcpu-macos-26 fallbacks in dev-landing-compile's runs-on and CMUX_NEXT_RUNNER, and the test that pins them, can be dropped. Base red, not this PR's: WebviewsWarnSplitCoversCheck fails the same way on base.

This branch was previously deployed

1 inactive deployment
ci-routing-agent — 094b954e Deployed Nov 2, 2026 by teamleaderleo via cmux-tui tree preflight #98272
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk:high Risk tier (docs/ci/risk-tiers.md)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant