-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-49696][SQL][TESTS] Disable flaky test Cancellation APIs in SparkSession are isolated
#48736
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@dongjoon-hyun Could you review this PR? |
sql/core/src/test/scala/org/apache/spark/sql/SparkSessionJobTaggingAndCancellationSuite.scala
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW, please attach the failure links into the PR description.
Cancellation APIs in SparkSession are isolated
Cancellation APIs in SparkSession are isolated
Cancellation APIs in SparkSession are isolated
Cancellation APIs in SparkSession are isolated
Cancellation APIs in SparkSession are isolated
Cancellation APIs in SparkSession are isolated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM (Pending CIs). I revised the PR title properly, @xupefei .
Please re-triggered the failed test pipeline.
Although we have still two failures, there are irrelevant to this test only PR . Let me merge this. Thank you, @xupefei .
|
Merged to master. SPARK-49696 is assigned to you, @xupefei . ![]() |
Thank you. I'll work on that ticket. |
Oh, no~ The issue SPARK-49696 was assigned to you as a recognition of this PR. There is not thing for you to work with it further, @xupefei. :)
|
What changes were proposed in this pull request?
This PR disables a flaky test
SparkSessionJobTaggingAndCancellationSuite.Cancellation APIs in SparkSession are isolated
(failure example: https://github.com/apache/spark/actions/runs/10915451051/job/30295259985). The flakiness is caused by CI sometimes creating only 2 threads instead of the requested 3. We should refactor the test to use only 2 threads.I created https://issues.apache.org/jira/browse/SPARK-50205 to fix and re-enable this test case.
Why are the changes needed?
To keep the CI green.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A.
Was this patch authored or co-authored using generative AI tooling?
No.