ci: throttle integration test parallelism to reduce server overload#2311
Merged
ci: throttle integration test parallelism to reduce server overload#2311
Conversation
Add max-parallel limits and sequence package tests after integration tests to prevent ~47 simultaneous jobs from overwhelming the dev server. - integration-test: max-parallel 8 - asset-import-test: max-parallel 3, runs after integration-test - package-test: max-parallel 5, runs after integration-test Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Chris (He/Him) <cgrote@gmail.com>
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
Signed-off-by: Chris (He/Him) <cgrote@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
max-parallel: 8tointegration-testmatrix to cap concurrent jobspackage-testandasset-import-testas wave 2 (afterintegration-testcompletes) vianeeds: integration-testmax-parallel: 5andmax-parallel: 3to package and asset-import jobs respectivelyif: always() && needs.build.result == 'success'so wave 2 still runs even when some integration tests failMotivation
Without limits, ~47 jobs run simultaneously against a single dev server, causing 403 (policy propagation too slow), 500 (server overload), and context deadline timeout errors. In run 22952102612, 39/62 jobs failed — re-running with no code changes showed more passing each time, confirming server overload as root cause.
Test plan
workflow_dispatchand confirm jobs run in two wavesintegration-testmax-parallel to 5–6; if all pass reliably, try increasing to 10–12🤖 Generated with Claude Code