config: Enable parallel LTP execution #1218
Open
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
The Kirk LTP runner which we are using supports parallel execution of tests, this is fortunately able to identify and appropriately handle tests that have to be run single threaded making it relatively easy to use. It does unfortunately make the console output a bit less helpful but they're still there, and Kirk does report per-test logs. With the test-definitions integration we can specify the number of workers as "max" in order to allow one worker per CPU in the system, do that by default. There is some risk that tests might interfere with each other and become less stable, if this becomes an issue we can revisit and use this only for suites that particularly benefit. Signed-off-by: Mark Brown <broonie@kernel.org>
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.
The Kirk LTP runner which we are using supports parallel execution of
tests, this is fortunately able to identify and appropriately handle
tests that have to be run single threaded making it relatively easy to
use. It does unfortunately make the console output a bit less helpful
but they're still there, and Kirk does report per-test logs.
With the test-definitions integration we can specify the number of
workers as "max" in order to allow one worker per CPU in the system, do
that by default. There is some risk that tests might interfere with
each other and become less stable, if this becomes an issue we can
revisit and use this only for suites that particularly benefit.
Signed-off-by: Mark Brown broonie@kernel.org