Repository navigation
ci(cmux-next): the landing DEV compile never overflows to Blacksmith macOS - #31600
Merged
teamleaderleo merged 1 commit intoNov 2, 2026
Merged
Conversation
…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
Contributor
|
cmux status (one comment, edited in place; each line is updated by the job that owns it) Review App of this head (app.zip, kept 1 day)
Shipped in:
|
Collaborator
Author
|
Review (subagent claude-opus-5-5 medium): SHIP at 094b954 |
This was referenced Nov 2, 2026
This branch was previously deployed
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.
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 toblacksmith-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 emptyruns_onandpool=none.overflow_label()and the snapshot read are gone.cmux-next.yml:dev-landing-compileruns only when the placement chose a runner.OVERFLOW_LABELis 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