Repository navigation
test(webviews): mark the two 3 s frame-watch windows as fixed waits (base red) - #23414
Conversation
#23374 merged after the fixed-wait ratchet (#23365) ran CI, and it added a 3 s waitForTimeout in two tests, which puts feat-cmux-next over its baseline. Both waits are observation windows: the test records every painted frame for 3 s after the chat opens and asserts none jumped, so the time is the test. They carry a fixed-wait marker instead of a raised baseline. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?harness=claude&session=01a15c78-27ca-7140-a6c7-95f0db83b18c&host=huge-blue
Bugbot needs on-demand usage enabledBugbot uses usage-based billing for this team and requires on-demand usage to be enabled. A team admin can enable on-demand usage in the Cursor dashboard. |
|
cmux status (one comment, edited in place; each line is updated by the job that owns it) Review App of this head (app.zip, kept 1 day)
Unclear: CI failed on
Not re-run automatically: Written by red: web / Web status; NEW: green on the base 0b1a93e; do not merge until green; see lane-rules Tour of |
|
Bead |
|
|
|
Review (subagent): SHIP at 93771bc Reds are not this PR's (it only adds two
|
…#23450) * webviews: composer-type-scale reads its variants four pages at a time The file checks 41 gallery states one after another. Each one opens a fresh page that loads ~700 dev-server modules (~2.2 s), after a ~30 s cold warm-up, so the file ran 122-173 s alone on Huge Blue and 134 s next to five other browser test files: past the runner's 120 s file limit (react-apps-check timed it out on #23414). Four pages now read variants at once, each variant still in its own page, and each test awaits its own result. 73-84 s alone and under the same load, 41 pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?harness=claude&session=01a15d90-e8f9-7e11-bdf0-cba6a4790d6a&host=huge-blue * Format composer-type-scale test with vp Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?harness=claude&session=01a15d90-e8f9-7e11-bdf0-cba6a4790d6a&host=huge-blue --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Shipped in:
|
feat-cmux-next is over the fixed-wait baseline. #23374 merged after the ratchet (#23365) had run its CI, and it added a 3 s
waitForTimeouttoagent-pane-stream-jitter.test.tsand toagent-pane-history-paging.test.ts. Every PR's webviews check now fails oncheck:fixed-waits.Both waits are observation windows. Each test records every painted frame for 3 s after the chat opens, then asserts that nothing jumped. The fixed time is what the test measures, so each wait gets a
// fixed-wait:marker and the baseline stays where it is.Verified with
bun run check:fixed-waits(992 on the baseline) andscripts/web-lint.sh. The change is comments only.Agent session: huge-blue
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Marks the two 3-second frame-watch windows in the webviews tests as fixed waits so
check:fixed-waitspasses again on the baseline.#23374 added the waits after the fixed-wait ratchet (#23365) had run CI, putting
feat-cmux-nextover its baseline. Both waits are observation windows: each test records painted frames for 3 s after the chat opens and asserts no jumps, so the fixed time is what the test measures. The change adds// fixed-wait:markers to both waits and is comments only.Written for commit 93771bc. Summary will update on new commits.