Repository navigation
Capture WebSocket background payload in the Linux timing oracle #355
Description
Parent: #227
Introduced by: #347
Blocks: #312 exact-current Linux requalification
Reproduction
The current-main NuGet Linux runtime build fails before native tests:
native_v8_runtime_websocket_tests.inc:356:59: error: 'background_bytes' is not captured
native_v8_runtime_websocket_tests.inc:352:64: note: the lambda has no capture-default
Exact evidence: PR #354, run 35330281188, Linux job 105553438327, head 2776af0f0c21e317d9bb962b362df88613a03eed, base cc18b9337374ea6aadc570280d503547f3621497.
Scope and acceptance
- Capture the immutable background payload size in the background sender without changing the Keep protocol timers fair across task sources #347 WebSocket timing workload.
- GCC/Linux and Clang/macOS compile the exact test.
- The focused protocol handshake/fairness oracle retains its frame counts, latency, queue, and teardown bounds.
- No runtime behavior changes.
Activity
wieslawsoltes commentedon Sep 18, 2026
Merged via #357 at
69d929f6fd0ca030c1394c921bebedad603f84b3.The correction captures the immutable 192 KiB background payload size by value in the #347 timing-oracle sender. Exact Linux package evidence compiled the native V8 test executable and entered CTest, proving the GCC failure is removed. The later run failures are the separately owned #312 parser timeout and existing native/crypto baseline.
Focused exact-head macOS evidence passed: 100-cycle WebSocket fairness p95 0.138 ms with flat heap; 20-cycle protocol Ready p95 3.641 ms and Initialized p95 12.577 ms; bounded worker/port/socket/FileReader queues; 1.99 s total and 135,708,672-byte peak RSS. No runtime behavior changed.