Repository navigation
test(debugger): capture startup subscription failures - #150
BartvHelvert wants to merge 2 commits into
Conversation
The client can cancel debugger subscriptions on a kernel clock timeout before a session starts. Attach the earlier client errors and adapter state to a missing-variable assertion, preserving the original failure and the existing debugger workflow. Refs #147
Add an opt-in batch of ten full-class runs per OS and retain each run's logs so startup subscription failures can be compared with successful debugger sessions. Preserve ordinary PR checks. Refs #147
|
Closing: the batch answered the question, and the answer is that these diagnostics are not the ones needed. The twenty jobs on So the decisive evidence — The If this keeps costing runs, the small thing worth doing is to put the reason in the failure message: on timeout, report whether the client logged a clock timeout for any |
What this changes
Investigation of #147. A Windows runtime UI test timed out with empty debugger tree rows after client startup had already cancelled debugger RPC subscriptions with
TimedOutWaitingForClockException. The backend later processed a debug thread update.When the first variable assertion times out, preserve the original failure and attach the adapter's probe state plus the client's clock-timeout/debugger-startup log lines as a suppressed diagnostic. Add focused debugger traces in both IDEs. This distinguishes a missing client view from a slow adapter response without retrying or restarting the session.
Refs #147
The opt-in
repeat_ui_testworkflow input runs the complete runtime/debugger test class ten times per OS and retains each run's IDE logs, including successful runs. Twenty-job CI batch, dispatched on349478fb; results pending. The workflow passesactionlint(ShellCheck unavailable locally).Draft: the missing kernel transaction and cancelled platform subscriptions remain unresolved. This is diagnostic work toward that fix.
How it was tested
:ui-test:compileTestKotlin: passed.:ui-test:test --tests '*SplitModeRuntimeTest' -PsearchableOptions=false: passed on Windows, including variables, step, resume, pause, and stop. The startup synchronization failure did not reproduce.freshTest --console=plain --continue: passed once from sibling branchtest/attach-selection, on the sameb46ed7feproduct code. This branch changes only UI tests, which were compiled and run separately.npm ci; real-host test requiresCODEBRIDGE_TEST_LSP_HOST=1). Gradle reportsBUILD SUCCESSFUL; PowerShell reported exit 1 after treating IntelliJ shutdown INFO stderr asNativeCommandError.ui-test-reports-windows-2025-1and bothsplit-mode-runtimeIDE logs. Client subscription errors precede debug startup.Checklist
A new feature has a UI test.Diagnostics in the existing UI test.Investigation; no product behavior change.docs/is updated where behaviour changed,docs/status.mdespecially.Third-party material keeps its notice and is listed inNone added.NOTICE.md.