Skip to content

[SPARK-55729][SPARK-55630][SS][FOLLOWUP] Fix failing test due to dependencies of two changes#55071

Closed
HeartSaVioR wants to merge 2 commits intoapache:masterfrom
HeartSaVioR:SPARK-55729-followup-fix-test
Closed

[SPARK-55729][SPARK-55630][SS][FOLLOWUP] Fix failing test due to dependencies of two changes#55071
HeartSaVioR wants to merge 2 commits intoapache:masterfrom
HeartSaVioR:SPARK-55729-followup-fix-test

Conversation

@HeartSaVioR
Copy link
Copy Markdown
Contributor

What changes were proposed in this pull request?

This PR proposes to fix the failing test introduced in SPARK-55729 due to the fact SPARK-55630 changes the behavior but misses to reflect the change to the test.

Why are the changes needed?

The new commit broke the test introduced by old commit.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

CI will follow.

Was this patch authored or co-authored using generative AI tooling?

Generated-by: Claude 4.6 Opus

@HeartSaVioR
Copy link
Copy Markdown
Contributor Author

HeartSaVioR commented Mar 28, 2026

Let's wait for CI result. Due to recent compromising issue with LiteLLM, running tests in local requires some manual intervention. While such a restriction on devloop is specific to only part of the Apache Spark community, it should be OK as long as CI can run the test.

@HeartSaVioR
Copy link
Copy Markdown
Contributor Author

CI passes. Thanks! Merging to master. (And thanks for the patience!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants