-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-35785][SS][FOLLOWUP] Ignore concurrent update and cleanup test #33195
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
left a comment
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.
If that is a test only issue, I'm +1.
BTW, let's keep the issue open although we merge this.
|
Thanks @dongjoon-hyun! Yea, I reuse original JIRA with followup only. @xuanyuanking will address SPARK-35993 by fixing the test later. And yes, this is test only issue. |
|
Oh, perfect, @viirya !
|
### What changes were proposed in this pull request? This patch ignores the test "ensure that concurrent update and cleanup consistent versions" in #32933. The test is currently flaky and we will address it later. ### Why are the changes needed? Unblock other developments. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Existing tests. Closes #33195 from viirya/ignore-rocksdb-test. Authored-by: Liang-Chi Hsieh <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit a6e00ee) Signed-off-by: Dongjoon Hyun <[email protected]>
|
Merged to master/3.1. |
|
Kubernetes integration test starting |
|
Thanks @dongjoon-hyun |
|
Kubernetes integration test status success |
|
Test build #140590 has finished for PR 33195 at commit
|
What changes were proposed in this pull request?
This patch ignores the test "ensure that concurrent update and cleanup consistent versions" in #32933. The test is currently flaky and we will address it later.
Why are the changes needed?
Unblock other developments.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests.