X_CDP_TIMEOUT
Means
a DevTools call did not answer inside its deadline
Typical cause
its own code rather than X_TIMEOUT, because the actionable half is WHICH call: a hung Page.navigate is an app that never finishes responding, a hung Runtime.evaluate is an expression that never settles. A call the connection timed carries what the wire did meanwhile — meta.reading is target-gone (its session detached, or its target was destroyed or crashed), lost-in-transport (meta.framesDropped frames arrived unparseable after the call) or no-answer (the target was there and silent; meta.framesArrived, meta.lastFrames, meta.navigations, meta.transportOpen say what else happened)
Fix
no-answer: raise timeoutMs on installE2eDriver({ timeoutMs }), or find the request the page is still waiting on. The other two: x test e2e --json again — the cause names what went