[SPARK-48116][INFRA][3.5] Run pyspark-pandas* only in PR builder and Daily Python CIs
#46482
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
…d Daily Python CIs
|
Could you review this backporting PR, @viirya ? Since this is applied to |
viirya
approved these changes
May 8, 2024
|
Thank you so much, @viirya ! |
dongjoon-hyun
added a commit
that referenced
this pull request
May 8, 2024
…d Daily Python CIs ### What changes were proposed in this pull request? This PR aims to run `pyspark-pandas*` of `branch-3.5` only in PR builder and Daily Python CIs. In other words, only the commit builder will skip it by default. Please note that all PR builders is not consuming ASF resources and they provides lots of test coverage everyday. `branch-3.5` Python Daily CI runs all Python tests including `pyspark-pandas` like the following. https://github.com/apache/spark/blob/21548a8cc5c527d4416a276a852f967b4410bd4b/.github/workflows/build_branch35_python.yml#L43-L44 ### Why are the changes needed? To reduce GitHub Action usage to meet ASF INFRA policy. - https://infra.apache.org/github-actions-policy.html > All workflows MUST have a job concurrency level less than or equal to 20. This means a workflow cannot have more than 20 jobs running at the same time across all matrices. Although `pandas` is an **optional** package in PySpark, this is essential for PySpark users and we have **6 test pipelines** which requires lots of resources. We need to optimize the job concurrently level to `less than or equal to 20` while keeping the test capability as much as possible. https://github.com/apache/spark/blob/a762f3175fcdb7b069faa0c2bfce93d295cb1f10/dev/requirements.txt#L4-L7 - pyspark-pandas - pyspark-pandas-slow - pyspark-pandas-connect - pyspark-pandas-slow-connect ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Manual review. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #46482 from dongjoon-hyun/SPARK-48116-3.5. Authored-by: Dongjoon Hyun <dhyun@apple.com> Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
|
Merged to branch-3.5. |
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 were proposed in this pull request?
This PR aims to run
pyspark-pandas*ofbranch-3.5only in PR builder and Daily Python CIs. In other words, only the commit builder will skip it by default. Please note that all PR builders is not consuming ASF resources and they provides lots of test coverage everyday.branch-3.5Python Daily CI runs all Python tests includingpyspark-pandaslike the following.spark/.github/workflows/build_branch35_python.yml
Lines 43 to 44 in 21548a8
Why are the changes needed?
To reduce GitHub Action usage to meet ASF INFRA policy.
https://infra.apache.org/github-actions-policy.html
Although
pandasis an optional package in PySpark, this is essential for PySpark users and we have 6 test pipelines which requires lots of resources. We need to optimize the job concurrently level toless than or equal to 20while keeping the test capability as much as possible.spark/dev/requirements.txt
Lines 4 to 7 in a762f31
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.