-
-
Notifications
You must be signed in to change notification settings - Fork 38.1k
Debugger paused event is sometimes not delivered to inspector client on macOS CI #64116
Copy link
Copy link
Open
Labels
debuggerIssues and PRs related to the Node.js command-line debugger.Issues and PRs related to the Node.js command-line debugger.flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.macosIssues and PRs related to the macOS platform.Issues and PRs related to the macOS platform.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Activity
Metadata
Metadata
Assignees
Labels
debuggerIssues and PRs related to the Node.js command-line debugger.Issues and PRs related to the Node.js command-line debugger.flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.macosIssues and PRs related to the macOS platform.Issues and PRs related to the macOS platform.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
We have multiple macOS CI debugger flakes where the debuggee appears to pause, but the
inspector client process never observes the expected
Debugger.pausedevent.This has affected interactive debugger tests and probe mode. In probe mode,
handlePaused()should either record hits or resume unknown pauses. When the report has no hits and eventually
times out, the most likely signal is that the paused event never reached the inspector client
process.
The AI-assisted PRs have mostly tried to address nearby symptoms or test races, but they have
not resolved the underlying observation:
Refs: #63632 (comment)
The question we need to answer is