-
Notifications
You must be signed in to change notification settings - Fork 29.1k
[SPARK-31235][FOLLOWUP][TESTS][test-hadoop3.2] Fix test "specify a more specific type for the ap… #28456
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
|
test this please |
|
ok to test |
|
Test build #122330 has finished for PR 28456 at commit
|
|
Test build #122331 has finished for PR 28456 at commit
|
|
Test build #122337 has finished for PR 28456 at commit
|
|
Test build #122361 has finished for PR 28456 at commit
|
|
@viirya @tgravescs How to specify "Hadoop profile hadoop3.2" to perform the test |
|
test this please |
|
Test build #122365 has finished for PR 28456 at commit
|
jiangxb1987
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.
LGTM
|
test this please |
|
Test build #122408 has finished for PR 28456 at commit
|
|
Retest this please. |
|
Test build #122412 has finished for PR 28456 at commit
|
|
Hi, @tgravescs . Could you review this PR? |
tgravescs
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.
changes look fine to me, I was running the tests multiple times since this seemed to be intermittent failure
|
merging this to master |
|
Thank you so much, @tgravescs ! |
|
Ur, in
It seems that this have a side effect. |
|
Although this is the first one hitting them, this may not be the root cause. |
|
Thank you @dongjoon-hyun , it may be caused by me, I will investigate this reason |
|
Thank you so much, @wang-zhun . |
|
Unfortunately, this test case follow-up broadens the failure surface to the other test suites, Definitely, this seems that some uncleaned YarnClient issue, but it's not clear to me. I'll revert this first to narrow down the failure this specific test case only. After that, if the original test case, Sorry guys. |
|
For the follow-up PR, please use |
|
that's fine, if its causing problems lets revert the test. We can do some other more basic tests just to make sure value passed as expected and perhaps add something in the Cluster Suite |
|
Hi, All. I made a follow-up PR. Until now, it looks promising. |
|
Inevitably, the test case will be disabled temporarily on Hadoop 3.2 profile only. We will keep this test coverage in Hadoop 2.7. |
…ific type` in Hadoop-3.2 ### 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. - #28456 - #28550 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the Jenkins with SBT/Maven. Closes #28552 from dongjoon-hyun/SPARK-31235-2. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
|
Thank you @dongjoon-hyun |
What changes were proposed in this pull request?
Update the input parameters for instantiating
RMAppManagerandClientRMServiceWhy are the changes needed?
For hadoop3.2, if
RMAppManageris not created correctly, the following exception will occur:How was this patch tested?
UTs