The debug E2E added in #76, Rstest debug launch hits a breakpoint with port 9229 occupied and cleans up after continue, failed once on macOS and passed on rerun.
To find out: whether the breakpoint is sometimes bound after the debuggee has already passed it (js-debug child auto-attach timing on macOS), or the waitFor timeout is too tight for a slow runner.
The debug E2E added in #76,
Rstest debug launch hits a breakpoint with port 9229 occupied and cleans up after continue, failed once on macOS and passed on rerun.E2E (macos-latest)), on feat(vscode): support function names as test titles #78, whose change does not touch debugging or theworkspace-1fixture (string titles only).AssertionError [ERR_ASSERTION]: debuggee should stop at the breakpointfrom thewaitForate2e/rstest/suite/debug.test.ts:66. After the timeout the run is torn down (Rstest debug worker disconnected,[birpc] rpc is closed, cannot call "runTest").main.To find out: whether the breakpoint is sometimes bound after the debuggee has already passed it (js-debug child auto-attach timing on macOS), or the
waitFortimeout is too tight for a slow runner.