Fix Node 24 Playwright install hang#4
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 10 minutes and 29 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
npx --no-installand cap browser installation to 5 minutes so stale downloads fail fast instead of blocking the workflowWhy
The stale Node 24 runs were not failing in the app or tests. They hung in the Playwright browser install step after the Chromium archive reached 100% downloaded. Node 20 and Node 22 completed the same install path; installing the browser under Node 22 avoids the installer hang while still running the integration test under Node 24.
Verification
npx --no-install playwright --versionnpx --no-install playwright install --with-deps --only-shell --dry-run chromiumbun run test:playwright