Repository navigation
fix(cmux-next): VNC reconnect test helpers are nonisolated (CmuxNextAppTests compile red) - #27862
Conversation
…et compile red) #26557 added RemoteVNCReconnectTests; under the test target's MainActor default isolation, AttemptCounter.increment() is main-actor isolated and the @sendable transport factory cannot call it, so CmuxNextAppTests does not compile on feat-cmux-next. Both lock-guarded helpers are nonisolated, as #27811 already writes them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Owned by an agent session · session |
|
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)
Not verified: macOS jobs did not run: compile and app tests were skipped on CI passes on Written by red: cmux-next checks (god files, concurrency, crash safety, l10n); no finished base run on c033155 to compare; do not merge until green; see lane-rules |
|
Review (codex gpt-6-astra high fast, independent box): SHIP at 4a4c593 SHIP No findings. Both helpers safely support nonisolated access: the transport is stateless, and the counter protects all mutable state with a lock. Tests could not run because Swift is unavailable. |
|
Review (codex-review-box/gpt-6-astra high, lane-place): SHIP at 4a4c593 SHIP No findings. Both helpers safely support nonisolated access: the transport is stateless, and the counter protects all mutable state with a lock. Tests could not run because Swift is unavailable. |
|
Found 8 test failures on Blacksmith runners: Failures
|
|
Fleet focused run at 4a4c593 (step fc0c7d0c99ce6df26bc51880): RemoteVNCReconnectTests, RemoteVNCMappingTests, PaneTabBarControlsTests and NewTabMenuTriggerTests all passed. On current feat-cmux-next the same test target does not compile (RemoteViewVNCTests.swift:130:22, a call to main actor-isolated 'increment()'; step 7e6da2ca3ec136fbda9cad5c). The 'cmux-next checks' and release-notary reds here also fail on base e430ffd; prepush-gate on this commit reports no new violations. |
|
The feat-cmux-next push run https://github.com/manaflow-ai/cmux/actions/runs/40994392464 at b0b87c9 failed: cmux-next checks (god files, concurrency, crash safety, l10n). |
#27862 made the old test's helpers nonisolated; this branch replaces that test with the stronger one, whose helpers already are. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-b22822edaca3611659c9
|
Shipped in:
|
|
Shipped in:
|
…ice 1 merge seam) Slice 1 switch/conflict review (2026-10-30), finding 1: feat's tests merged without a text conflict but call APIs perf changed, so CmuxNextAppTests does not compile. - PaneTabBarControlsTests: TabStripView.testing(model:) (perf makes input: required) and strip.scroller.settle() (perf moved feat's settleScroll() into TabStripScroller.settle(), the same body). - RemoteViewVNCTests (#27862): RemoteVNCSession(cloudRecord:makeTransport:) now also takes perf's work:, mainWork: and signIns:; the test passes its own lane, scheduler and in-memory sign-ins, as RemoteVNCSignInReadTests does. No assertion changes. Proof: the fleet compile of CmuxNextAppTests on this head.
![Fix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/fix-with-codesmith-light-3x.png)
#26557 landed
RemoteVNCReconnectTests(carried from #26697). Under the CmuxNext test target's.defaultIsolation(MainActor.self), the privateAttemptCounteris main-actor isolated, so the@Sendabletransport factory cannot callincrement():CmuxNextAppTests does not compile on feat-cmux-next at 0ce3c31, so every CmuxNext suite run fails at build. This marks the two lock-guarded test helpers
nonisolated, as #27811 already writes them (that PR now conflicts with base). Two lines, tests only.Observed / Not run
Changelog
none
Agent session: agent session
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Fixes the CmuxNextAppTests compile failure on
feat-cmux-nextby marking two VNC reconnect test helpers asnonisolated.Under the test target's
MainActordefault isolation, the@Sendabletransport factory could not callAttemptCounter.increment(), breaking the build for every CmuxNext suite run. The lock-guardedCountingRFBTransportandAttemptCounterhelpers are nownonisolated; test behavior is unchanged.Written for commit 4a4c593. Summary will update on new commits.