[Internal] Allow control over pytest concurrency #894
+3
−1
Conversation
This file contains 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
rauchy
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
rauchy
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
rauchy
force-pushed
the
set-pytest-concurrency
branch
from
1d414d3 to
12fc173
Compare
rauchy
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
rauchy
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
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 changes are proposed in this pull request?
This pull request introduces an environment variable, PYTEST_CONCURRENCY, allowing developers to control the number of concurrent processes used during pytest execution. Previously, the concurrency level for pytest was fixed and based on the number of processes on the host it ran in.
If the env variable is unspecified, it will still fall back to the number of processes in the host.