Repository navigation
fix(ci): cap Infection threads at 4 - #23
Merged
Merged
Conversation
"max" resolves to the number of logical processors. On a developer machine that is commonly 16 logical processors across 8 physical cores, so max means 16 concurrent threads. Because this config sets staticAnalysisTool to mago, Infection spawns one mago analyze subprocess per mutant. At max that is 16 concurrent Mago processes contending for 8 physical cores, which saturates the host for tens of minutes and makes the machine unusable for anything else. A cap of 4 matches the vCPU count of the GitHub-hosted ubuntu-latest runner, so local and CI runs behave identically instead of diverging in both speed and resource shape. webware-acl and webware-migration already use 4, so this makes the fleet uniform. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
Caps Infection's parallel thread count at 4 in
infection.json5.dist.Rationale
"max"resolves to the number of logical processors. On a developer machine that is commonly 16 logical processors across 8 physical cores, somaxmeans 16 concurrent threads.Because this config sets
staticAnalysisTool: "mago", Infection spawns onemago analyzesubprocess per mutant. Atmaxthat is 16 concurrent Mago processes contending for 8 physical cores, which saturates the host for tens of minutes and makes the machine unusable for anything else.A cap of 4 matches the vCPU count of the GitHub-hosted
ubuntu-latestrunner, so local and CI runs behave identically instead of diverging in both speed and resource shape.webware-aclandwebware-migrationalready use 4, so this makes the fleet uniform.Diff
One line:
"threads": "max"becomes"threads": 4. Nothing else changes.