[hotfix][python][ci] Parallelise Flink Python test execution #26551
+2
−1
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
|
@flinkbot run azure |
airlock-confluentinc
bot
force-pushed
the
hotfix-pytest-xdist
branch
from
2a29473 to
d061ee5
Compare
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.
What is the purpose of the change
Currently, the PyFlink pytests are run sequentially on a single CPU core. This PR adds the
pytest-xdistplugin that creates workers for each CPU core available and distributes the tests across them. On the Github runners this leads to shaving off 4-5 mins per tox test run, and scales with the number of cores available.Brief change log
pytest-xdistplugin for parallelising Flink Python pytest runs in CI