-
-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✅(jest) Make tests run concurrently #5378
Conversation
They used to be running in a concurrent fashion in the past. But we stopped doing it due to a recent regression on the stability of our CI with Node 23. The regression being still noticeabl even without it and because of the cost of not doing the runs in a concurrent fashion, we move back to concurrent execution.
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit a10166a:
|
👋 A preview of the new documentation is available at: http://671fde65e834e833a687328d--dubzzz-fast-check.netlify.app |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5378 +/- ##
=======================================
Coverage 95.27% 95.27%
=======================================
Files 234 234
Lines 10478 10478
Branches 2795 2795
=======================================
Hits 9983 9983
Misses 495 495
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
👋 A preview of the new documentation is available at: http://67209856809930aa0473794a--dubzzz-fast-check.netlify.app |
👋 A preview of the new documentation is available at: http://67209c5178a44c2e819e388b--dubzzz-fast-check.netlify.app |
👋 A preview of the new documentation is available at: http://67209ef0908ab6b570e4fdff--dubzzz-fast-check.netlify.app |
Description
They used to be running in a concurrent fashion in the past. But we stopped doing it due to a recent regression on the stability of our CI with Node 23.
The regression being still noticeable even without it and because of the cost of not doing the runs in a concurrent fashion, we move back to concurrent execution.
Checklist — Don't delete this checklist and make sure you do the following before opening the PR
yarn bump
and flag the impacts properlyAdvanced