[WIP] Experiment with adding a operation queue #9243
Draft
Conversation
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
Add an operation queue around execution of swiftPM process execution. swift-testing based test will run all tests in parallel at the same time, causing each invocation to spawn a process which will then spawn many other subprocesses. These leads to a process bomb and consumes all CPU and causes massive I/O blocking. Add a limit to how many swiftPM top level processes at the same time.
kcieplak
requested review from
bkhouri,
bripeticca,
cmcgee1024,
daveyc123,
dschaefer2,
jakepetroules,
owenv,
plemarquand,
rconnell9 and
shawnhyam
as code owners
|
@swift-ci test |
|
@swift-ci test windows |
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.
Add an operation queue around execution of swiftPM process execution.
swift-testing based test will run all tests in parallel at the same time, causing each invocation to spawn a process which will then spawn many other subprocesses.
These leads to a process bomb and consumes all CPU and causes massive I/O blocking.
Add a limit to how many swiftPM top level processes at the same time.