We have multiple macOS CI debugger flakes where the debuggee appears to pause, but the
inspector client process never observes the expected Debugger.paused event.
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
Why is Debugger.paused sometimes never delivered to the inspector client process on macOS CI?
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