Ahmed IbrahimandGitHub b39ae9501f Stabilize websocket test server binding (#14002) ...

## Summary
- stop reserving a localhost port in the websocket tests before spawning
the server
- let the app-server bind `127.0.0.1:0` itself and read back the actual
bound websocket address from stderr
- update the websocket test helpers and callers to use the discovered
address

## Why this fixes the flake
The previous harness reserved a port in the test process, dropped it,
and then asked the server process to bind that same address. On busy
runners there is a race between releasing the reservation and the child
process rebinding it, which can produce sporadic startup failures.
Binding to port `0` inside the server removes that race entirely, and
waiting for the server to report the real bound address makes the tests
connect only after the listener is actually ready.

2026-03-09 23:39:56 -07:00

..

common

chore: plugin/uninstall endpoint (#14111)

2026-03-09 12:40:25 -07:00

suite

Stabilize websocket test server binding (#14002)

2026-03-09 23:39:56 -07:00

all.rs

fix: separate codex mcp into codex mcp-server and codex app-server (#4471)

2025-09-30 07:06:18 +00:00