Repository navigation
carry of #27531: gate nightly recovery on tree marker - #28197
Merged
Merged
Conversation
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)
|
teamleaderleo
temporarily deployed
to
ci-routing-agent
October 30, 2026 09:01 — with
GitHub Actions
Inactive
Collaborator
Author
|
Review (codex-review-box/gpt-6-astra high, lane-place): BLOCK at b9559c1 BLOCK
|
Collaborator
Author
|
Owned by an agent session · session |
… when the tree publishes A tree-changing landing waited about 27 minutes for its cmux-tui tree (build, R2 upload, tree publish, marker) before its NEXT nightly could start. Main's promote guard now accepts such a commit when its nightly.yml carries NIGHTLY_NEXT_TREE_AT_INSTALL: v1 (#27498). This is that nightly: - resolve-nightly-cmux-tui-client: a tip whose tree is a clean 404 is built as it is (tree_pending, with its same-key first-parent candidates); - build-nightly-app compiles at once. Bundle acpmux gets a stand-in input (the phase only aliases bin/acpmux to bin/cmux), and "Bundle the cmux-tui client" waits for the tree's attested manifest (await-tree-client.sh), then installs it with the same install-cmux-tui-client.sh command; - await-nightly-tree-marker gates publish-nightly on the build commit's tree-commit marker naming the installed client's commit (G5, in the run); - request-nightly-next.sh requests such a tip while an artifacts run builds its tree. nightly.yml stays under its size limit: two steps live in scripts/ci/nightly-steps/ and some comments in the touched jobs are shorter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-a7306ef145c005ad24ab
…own, resumed or recovered Review findings on 18c51bd: - publish-nightly's source selection takes this run's own build only when await-nightly-tree-marker passed (or the build never waited for its tree), so a recovered build can no longer stand in while the own build is used; - the marker check also runs for an unsigned resume, against the commit the resumed app installed; - recovery refuses a run whose marker check failed, was cancelled or has not finished (recover-tree-marker-ok.sh); - await-tree-client.sh reads each candidate's own artifacts runs before the newest-50 listing, so a crowded listing never reads as no publisher. publish-nightly's own if clause is left as it is (#27508 changes it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-a7306ef145c005ad24ab
…s size limit Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-a7306ef145c005ad24ab
…t (no gh api paginate) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-a7306ef145c005ad24ab
…dled The sign variant now reads build-nightly-app.outputs.cmux_tui_commit first (the commit await-tree-client.sh found while the tip tree publishes), so the universal-build guard accepts that expression instead of the resolver output alone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-d35d25d288d130b0c84c
teamleaderleo
force-pushed
the
lane/carry-27531-nightly-marker
branch
from
October 30, 2026 13:56
b9559c1 to
495fb84
Compare
teamleaderleo
temporarily deployed
to
ci-routing-agent
October 30, 2026 13:56 — with
GitHub Actions
Inactive
|
Found 4 test failures on Blacksmith runners: Failures
|
teamleaderleo
temporarily deployed
to
ci-routing-agent
October 30, 2026 14:10 — with
GitHub Actions
Inactive
teamleaderleo
temporarily deployed
to
ci-routing-agent
October 30, 2026 14:14 — with
GitHub Actions
Inactive
teamleaderleo
temporarily deployed
to
ci-routing-agent
October 30, 2026 14:28 — with
GitHub Actions
Inactive
teamleaderleo
temporarily deployed
to
ci-routing-agent
October 30, 2026 14:41 — with
GitHub Actions
Inactive
teamleaderleo
temporarily deployed
to
ci-routing-agent
October 30, 2026 14:50 — with
GitHub Actions
Inactive
Contributor
|
Shipped in:
|
This was referenced Nov 1, 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.
![Fix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/fix-with-codesmith-light-3x.png)
Carry of #27531: ci(nightly-next): build the tip at once and install its tree's attested client when the tree publishes.
Carries the nightly tree-at-install work onto current feat-cmux-next. The publish source selector now requires the current build's tree-marker eligibility before selecting it; a recovered build cannot bypass a failed marker gate. The carried tests cover marker-aware recovery selection.
Original PR: #27531
Agent session: agent session
Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Carries #27531's nightly tree-at-install work onto current
feat-cmux-next. A nightly that starts before its tip's cmux-tui tree is published now compiles the app immediately, installs the tree's attested client once its manifest is uploaded, and publishes only after the build commit's tree-commit marker names the installed client's commit as the tree's publisher.Behavior changes
publish-nightlyevaluates its job condition withalways()so a skipped marker-wait job still lets publication proceed.build-nightly-app's output instead of the resolver's alone.request-nightly-next.shrequests such a tip at once while an artifacts run builds its tree.Written for commit 4fed48b. Summary will update on new commits.