Skip to content

test(openai): synchronize WebSocket TTFT fixtures - #8756

Open
r266-tech wants to merge 1 commit into
Wei-Shaw:mainfrom
r266-tech:codex/synchronize-ws-ttft-fixture
Open

r266-tech wants to merge 1 commit into
Wei-Shaw:mainfrom
r266-tech:codex/synchronize-ws-ttft-fixture

Conversation

@r266-tech

@r266-tech r266-tech commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

The WebSocket TTFT fixture can start reading the next scripted turn before the client's next response.create, consuming part of its delay before that turn's TTFT clock starts. Gate each turn on its upstream request and cover immediate and 75ms-delayed clients in both semantic and visible mode. The original two-turn timing bounds remain the oracle (follow-up to #8565).

This PR now contains only the WebSocket fixture. The repeated pre-content keepalive fixture is tracked in #8839.

Validation on Go 1.27.4 / macOS arm64, based on main@15871f904 (including #8767):

  • The WebSocket patch is unchanged from the original head (stable patch-id matches); the overlapping Antigravity hunk was removed.
  • Related first-token/TTFT tests repeated three times: 81 tests/subtests passed. The WebSocket fixture also passed three repetitions with -race (21 tests/subtests).
  • golangci-lint 2.14.0: zero issues. govulncheck: no reachable vulnerabilities or affected imported packages; six uncalled module advisories.
  • Reused the original delayed-client and ignored-TTFT-rule negative controls, plus the original full unit/integration results. Full unit/integration also passed on the current main baseline in this run; these were not rerun for this test-only head.

AI-assisted implementation and local HTTP/WebSocket fixture validation. No live provider was used.

@r266-tech
r266-tech force-pushed the codex/synchronize-ws-ttft-fixture branch from dfcc842 to fb9ba3f Compare November 17, 2026 14:03
@r266-tech r266-tech changed the title test(streaming): synchronize TTFT and keepalive fixtures test(openai): synchronize WebSocket TTFT fixtures Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant