-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-33934][SQL][FOLLOW-UP] Use SubProcessor's exit code as assert condition to fix flaky test #31046
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
|
FYI @dongjoon-hyun |
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.
Thank you for the quick follow-up, @AngersZhuuuu .
|
@AngersZhuuuu . Since you are one of the active contributors, I want to give some advice. |
|
The fix itself seems fine. As Dongjoon suggested above, I think the title and PR description need to be modified a bit though. |
Done |
Really? It seems you forgot to update the PR title... |
| package org.apache.spark.sql.execution | ||
|
|
||
| import java.io._ | ||
| import java.io.{BufferedReader, File, InputStream, InputStreamReader, OutputStream} |
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.
Oh, I don't know why I thought it's more than 5+. It's more than 6+ (https://github.com/databricks/scala-style-guide#imports).
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.
Oh, I don't know why I thought it's more than 5+. It's more than 6+ (https://github.com/databricks/scala-style-guide#imports).
Seems my local ideal's rule is 5, emmm I need to check this.
|
@AngersZhuuuu . You didn't change the PR title yet. |
Sorry for my bad network when at home...re-edit the title but seems failed to change. Updated now, cc. @maropu |
Co-authored-by: Hyukjin Kwon <[email protected]>
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.
|
Test build #133694 has finished for PR 31046 at commit
|
|
@AngersZhuuuu . Could you add three empty commits because this is a fix for flaky tests? |
Done, but I am confused why we do this == |
Emmmm, got your point, push some empty commit to trigger GA to test the UT's stability. |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #133697 has finished for PR 31046 at commit
|
|
Although the last GitHub Action job is in the queue, the last commit (and its empty commits) passed three times already. |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #133707 has finished for PR 31046 at commit
|
|
Test build #133716 has finished for PR 31046 at commit
|
|
Test build #133718 has finished for PR 31046 at commit
|

What changes were proposed in this pull request?
Follow comment and fix. flaky test #30973 (comment).
This flaky test is similar as #30896
Some task's failed with root cause but in driver may return error without root cause , change. UT to check with status exit code since different root cause's exit code is not same.
Why are the changes needed?
Fix flaky test
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existed UT