[Testing] Limit concurrency in monitoring app deployment to reduce CPU contention on slower macines#9595
Merged
assaf758 merged 1 commit intomlrun:developmentfrom Apr 21, 2026
Conversation
…ontention Cap the ThreadPoolExecutor in `_set_and_deploy_monitoring_apps` to `os.cpu_count() // 4` workers. Concurrent kaniko builds were exhausting available CPUs on the CI runner (8 vCPUs), causing `test_app_flow` to exceed the 1800s pytest timeout. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
📊 Diff Coverage Report📂 Click to view full coverage detailsDiff CoverageDiff: origin/development...HEAD, staged and unstaged changesNo lines with coverage information in this diff. |
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
1 participant
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.
Cap the ThreadPoolExecutor in
_set_and_deploy_monitoring_appsto 1 workers for machines with 8 or below vCPUs.Reason: concurrent kaniko builds are exhausting available CPUs on the self-hosted runner (8 vCPUs), causing
test_app_flowto exceed the 1800s pytest timeout.📝 Description
🛠️ Changes Made
✅ Checklist
🧪 Testing
🔗 References
🚨 Breaking Changes?
🔍️ Additional Notes