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
[SPARK-31235][TESTS][FOLLOWUP] Disable test case specify a more specific type
in Hadoop-3.2
#28552
Conversation
…ific type` in Hadoop-3.2
specify a more specific type
in Hadoop-3.2
specify a more specific type
in Hadoop-3.2specify a more specific type
in Hadoop-3.2
Retest this please. |
Test build #122730 has finished for PR 28552 at commit
|
Test build #122731 has finished for PR 28552 at commit
|
Test build #122732 has finished for PR 28552 at commit
|
specify a more specific type
in Hadoop-3.2specify a more specific type
in Hadoop-3.2
cc @wang-zhun , @tgravescs , @jiangxb1987 , @srowen , @HyukjinKwon |
Thank you for review and approval, @srowen . |
Test build #122733 has finished for PR 28552 at commit
|
Merged to master. |
specify a more specific type
in Hadoop-3.2specify a more specific type
in Hadoop-3.2
LGTM |
Thank you, @HyukjinKwon . |
What changes were proposed in this pull request?
This PR aims to recover Hadoop-3.2 profile jobs on
master
branch by disabling a UT added by SPARK-31235 in Hadoop 3.2 temporarily. The target UT is not a flaky test. It always fail on Hadoop-3.2 profile currently although it works in Hadoop 2.7 profile. So, in this PR, we keep the test coverage in Hadoop 2.7 and ignore the test in Hadoop 3.2 temporarily to unblock the other PRs.Why are the changes needed?
SPARK-31235 added a test case which is breaking Hadoop 3.2 and there are two follow-up to fix it. Although two follow-ups can fix the UT in Hadoop 3.2 environment. The side-effect on Hadoop classes cause some random UT failures in the other suites.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the Jenkins with SBT/Maven.