Repository navigation
test(usercentrics): use the repo cold-start budget for the loader tag wait - #958
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🤖 MERGED
GitHub merged this pull request.
The pull request closed. Selected findings run after merge and open separate pull requests. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 23 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The longer loader wait accommodates the stated cold-start delay, and the described waits fit within the 90-second test limit. No material merge risk remains. Pre-merge checks |
|
commit: |
📦 Package Size✅ No notable size changes 📚 22 runtime dependencies (no change) All tracked output (25)
Runtime dependencies (22)
Baseline: main_@_965839c7___2026-10-12 · gzip is the comparison metric · changes below 16 B gzip are ignored |
There was a problem hiding this comment.
Open (82/100): The flake budget bump may be insufficient: short waits after the initial selector wait and unchanged suites can still exceed their timeouts on a cold CI start, and CI on head is red.
Proof: The required check "test" fails on the head commit cf712e0 while the PR's purpose is to stop that flake. Line 82 still bounds a later waitForFunction at 15000, and other suites (calendly, linkedin, partytown) keep 15000 waits under 60000 te.
Next: Raise the remaining 15000 waitForFunction budget in this suite (and audit calendly/linkedin/partytown suites) to a cold-start-safe value, then confirm the "test" check passes on head.
Harlan Agent Kit posted this automated review. It is not Harlan's personal review or approval. AI open source policy.
🔗 Linked issue
📚 Description
The v3 loader tag renders after Nuxt resolves suspense and the idle callback runs, and a cold fixture start on CI can push that well past domcontentloaded, so the fixed 15s wait flaked. This gives the wait the same 30s cold-start budget the ahrefs and linkedin suites already use, with a matching 90s test timeout.