Repository navigation
test(webxr): enable warm-up simulation in StreamAttachTimeoutTest attempt 2 - #1259
Merged
Merged
Conversation
Contributor
gareth-morgan-nv
requested review from
AndreusNvidius,
sgrizan-nv and
yanziz-nvidia
October 13, 2026 19:35
2 of 3 tasks
sgrizan-nv
approved these changes
Oct 13, 2026
…empt 2
Attempt 2 ("attaches, no frame ever") left MockCloudXR's warm-up simulation off, so the
mock rendered normally and emitted streaming metrics for the whole attempt. The test's
"no streaming metrics before warm-up completes" check treated that as a failure, so the
spec failed on main.
Turn the simulation on with warmupTotalFrames: null. render() then stays black like a
stuck decoder, no metrics fire, and the warm-up-begin timeout still triggers because no
warm-up frame is ever fed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Signed-off-by: Gareth Morgan <gmorgan@nvidia.com>
gareth-morgan-nv
force-pushed
the
gmorgan/fix-attach-timeout-test-attempt2
branch
from
October 13, 2026 19:51
8d315da to
122f97c
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
StreamAttachTimeoutTest.spec.jsfails onmain: attempt 2 ("attaches fine, no frame ever") never turned onMockCloudXR's warm-up simulation, so the mock rendered normally and emitted streaming metrics for the whole attempt. The test's "no streaming metrics before warm-up completes" check counts any metric before a warm-upcompletedstatus as a failure, so it reportedstreamingMetricsFiredDuringWarmup=true.Fix: give attempt 2
warmupTotalFrames: null. That turns the simulation on, sorender()stays black like a stuck decoder and no metrics fire. No warm-up frame is ever fed, so the warm-up-begin timeout still triggers, which is what attempt 2 is meant to exercise.Test-only change; no product code touched.
Why CI did not catch it
CI runs
npm test(jest), which excludestests/playwright/. The Playwright specs only run vianpm run test:playwright, which no workflow calls.Test plan
npx playwright test tests/playwright/StreamAttachTimeoutTest.spec.js: failed before, passes 3/3 after (about 9 s each)SKIP=check-copyright-year pre-commit run --all-filesclean🤖 Generated with Claude Code
Summary by CodeRabbit