Repository navigation
fix(e2e): connect the mobile suite to realtime and give dev-server round trips the server budget - #8937
Conversation
…und trips the server budget - Start the realtime server for the mobile group. Without it every workspace page raised a persistent "Reconnecting..." toast ~2s after load; on the locked-workflow reload it raced the lock toast and, when it arrived second, sat in front of the Unlock Workflow action, so the tap timed out on "subtree intercepts pointer events" - Wait 120s, the suite's budget for a next dev round trip, for the URL after a sidebar link tap, the Files list after it, and the table cell after a reload. next dev spent 16.4s (application code 70ms) serving the /home RSC payload and left the rows request unanswered past 20s - Install the browsers while the app boots
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
No issues found across 2 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.
Turn on auto-fix | Re-trigger cubic
…tall and realtime logs on failure
|
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
No issues found across 2 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.
Turn on auto-fix | Re-trigger cubic
| bunx --no-install playwright install --with-deps chromium webkit & | ||
| browsers_pid=$! |
There was a problem hiding this comment.
Installer outlives failed startup
The browser installer now runs in the background, but finish() only stops the app and realtime server. If either server fails during startup, wait_ready() exits before wait "$browsers_pid", leaving downloads or package installs running through later CI steps. Track and stop the installer’s children in the exit cleanup too.
Summary
e2e (mobile)failed the first attempt on 6 of the last 43 staging pushes, and both attempts of the v0.9.19 release run on main. A different single check failed each time (185 of 186 passed). This PR fixes the three causes found in recent CI history.next devtook 16.4s to serve the/homeRSC payload; 70ms of that was application code, and the rest was the dev server reloading modules. These checks waited 20s; the suite gives every other dev-server round trip 120s, and they now get 120s too."The long draft must have a scrollable editor" was already fixed by #8892: 19 failures before it, 0 in 94 runs since.
Not fixed here:
Test plan
e2e (mobile)passes, and its log shows "mobile realtime server ready"