fix: run-tests cancel now exits Play Mode before re-enabling domain reload#1740
Conversation
…ishes Timeout and disconnect cancels used to dispose DomainReloadDisableScope as soon as the await ended, re-enabling domain reload while Test Runner work could still be active. Run a no-throw stop/restore step with its own wait budget before scope dispose, using public Play Mode exit until CancelTestRun access is decided. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reached
Next review available in: 11 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…e cancel notes The flag was always set before any await, so the catch branch could never see it false. Also avoid warning about missing CancelTestRun after Play Mode exit is already confirmed, which only confused agents. Co-authored-by: Cursor <cursoragent@cursor.com>
|
LGTM (reviewer: Fable). Design-agreement conditions verified: no-throw StopAndRestore, CancellationToken.None + 10s bounded waits, DomainReloadDisableScope disposed only after the stop wait, and the null TryCancelTestRun shape stays compatible with a future Option A fallback. Review fixes confirmed at 142bc5f (unreachable executionStarted guard removed; degradation note quieted on confirmed PlayMode exit). Local pure C# tests 16/16 green. |
Refs: hang survey section 2 / PR 1-2 (Option B baseline; Option A pending user permission)
Summary
DomainReloadDisableScopeUser Impact
Changes
RunTestsCancelStopRestoreorchestrator (no-throw; internal waits useCancellationToken.None+ 10s bound)EditorApplication.isPlaying = falseonly;CancelTestRunreflection not enabled yet (needs explicit user permission). If approved, Option A will plug intoTryCancelTestRunwith cached lookup and automatic B fallbackVerification
dotnet test tests/RunTestsExecutionTimeout.UnitTests/RunTestsExecutionTimeout.UnitTests.csproj(16 passed)uloop compilegreenuloop run-tests --filter-type regex --filter-value "RunTestsUseCaseTests|PlayModeTestExecuterTests|DomainReloadDisableScopeTests"(25 passed)Made with Cursor