-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Performance Tests: --runInBand to avoid performance issues in CI environment #44905
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
base: trunk
Are you sure you want to change the base?
Conversation
|
Size Change: 0 B Total Size: 1.33 MB ℹ️ View Unchanged
|
f33281e to
3aa1054
Compare
3aa1054 to
067b3cc
Compare
|
Closing because this change isn't significantly impacting the test run times either good or bad. After 50 experimental runs there is no statistical reason to believe this change impacts the test runtime. Assuming the test runs follow a normal distribution, then we approximate this branch to have N(2851s, 532s) and |
067b3cc to
052e429
Compare
|
Flaky tests detected in 052e429. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4129373690
|
…ronment Some projects have seen dramatic performance bottlenecks in CI environments because of the way `jest` parallelizes its test runs and bloats its memory usage. In this patch we're running the tests in serial to determine if this sequential-vs-parallel effect is in play in our GitHub Actions runs.
052e429 to
fe252cf
Compare
Please ignore for now, this is for testing.
Does limiting test runs to
--runInBandreduce variation in measured metrics?