[SPARK-56688][INFRA][PYTHON] Reorganize pyspark tests to empty a CI slot#55638
Open
gaogaotiantian wants to merge 1 commit intoapache:masterfrom
Open
[SPARK-56688][INFRA][PYTHON] Reorganize pyspark tests to empty a CI slot#55638gaogaotiantian wants to merge 1 commit intoapache:masterfrom
gaogaotiantian wants to merge 1 commit intoapache:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
We emptied a CI slot for future usage.
After some optimization work, we have a CI slot
pyspark-core, pyspark-errors, pyspark-streaming, pyspark-loggerthat normally just takes 30 minutes. It's a waste of slot because we can only have 20 concurrent jobs. This PR splits the workload into other slotspyspark-core, pyspark-errors, pyspark-logger->pyspark-sql, pyspark-resource, pyspark-testingpyspark-streaming->pyspark-structured-streaming, pyspark-structured-streaming-connectpyspark-logger-> followpyspark-pipelinesnowWe should still be able to keep all the CI slots below 90 minutes most of the time (120 is the limit). And we can have a new slot.
Why are the changes needed?
The reason we want a new slot, is to have a CI test against old client (4.0 client for example) to check backward compatibility issues. We have broken the client multiple times this year and we have 0 tests to gate it.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
It's a CI change only.
Was this patch authored or co-authored using generative AI tooling?
No.