Repository navigation
[SPARK-60082] Deduplicate the remaining E2E SparkApplication fixtures - #958
Closed
dongjoon-hyun wants to merge 1 commit into
Closed
dongjoon-hyun wants to merge 1 commit into
dongjoon-hyun wants to merge 1 commit into
Conversation
dongjoon-hyun
force-pushed
the
SPARK-60082
branch
from
October 8, 2026 04:46
791defb to
7d96811
Compare
peter-toth
approved these changes
Oct 8, 2026
Member
Author
|
Thank you, @peter-toth . |
Member
Author
|
Merged to main |
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
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?
As a follow-up of SPARK-59958, this PR aims to deduplicate the remaining E2E
SparkApplicationfixtures.tests/e2e/kueue/spark-example.yamlwith the sharedtests/e2e/fixtures/spark-application/spark-example.yaml.tests/e2e/fixtures/spark-application/spark-application-succeeded.yamlintospark-example.yaml. They differ only in the image. This PR keepsapache/spark:{{SPARK_VERSION}}-scala, which isapache/spark:{{SPARK_VERSION}}without Python.Why are the changes needed?
To reduce the maintenance cost. For example, a Spark version upgrade needs to update
sparkVersionin 18 E2E files instead of 20.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 5.5