fix(e2e): reduce staging E2E concurrency to avoid rate limiting#8129
fix(e2e): reduce staging E2E concurrency to avoid rate limiting#8129jacekradko merged 1 commit intomainfrom
Conversation
Staging instances have stricter FAPI rate limits than production. Running all 9 test suites in parallel causes 'Too many requests' errors during sign-in flows. Limit to 3 parallel jobs to stay within rate limits.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe change adds a concurrency constraint to the e2e-staging workflow by setting 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📝 Coding Plan
Comment |
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Summary
Test plan
Too many requests. Please try again in a bit.Summary by CodeRabbit