-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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-32916][SHUFFLE][test-maven][test-hadoop2.7] Remove the newly added YarnShuffleServiceSuite.java #30349
Conversation
… to older YarnShuffleServiceSuite.scala
@mridulm Please take a look |
ok to test |
Test build #130985 has finished for PR 30349 at commit
|
Kubernetes integration test starting |
Kubernetes integration test status failure |
it would be nice to add description as to why they need to be moved. or why moving them fixes whatever the failure is. |
Big +1 for @tgravescs advice. |
@tgravescs @HyukjinKwon I am not entirely sure why these tests would fail with the errors below only for hadoop-2.7 profile. The reason I am deleting this I can dig deeper into why this happened but that would require more time. In the meantime just wanted to fix the failures with hadoop-2.7 build.
|
Retest this please |
Let's see if this recovers |
Kubernetes integration test starting |
Kubernetes integration test status success |
Test build #131019 has finished for PR 30349 at commit
|
Hi, @otterc , @mridulm , @tgravescs , @HyukjinKwon . |
I'm fine to get something checked in quickly to fix the build but would like to understand it as well. I kicked the build again as failure didn't look related. |
yeah I didn't realize that Suite was in different module, it makes sense it put it all in one place. |
test this please |
Kubernetes integration test starting |
Kubernetes integration test status success |
failures look unrelated, I'm honestly not sure what they are: @dongjoon-hyun have you been this before? Maybe I'm missing something in the logs |
Test build #131071 has finished for PR 30349 at commit
|
I'm not sure what is going on with GitHub Action tests, but based on the Jenkins ones passing, I'm going to merge this. If we find it makes things worse we can revert it. |
merged to master |
Thank you, @tgravescs and all! |
Thanks for merging it @tgravescs. |
…dded YarnShuffleServiceSuite.java This is a follow-up fix for the failing tests in `YarnShuffleServiceSuite.java`. This java class was introduced in #30062. The tests in the class fail when run with hadoop-2.7 profile: ``` [ERROR] testCreateDefaultMergedShuffleFileManagerInstance(org.apache.spark.network.yarn.YarnShuffleServiceSuite) Time elapsed: 0.627 s <<< ERROR! java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.apache.spark.network.yarn.YarnShuffleServiceSuite.testCreateDefaultMergedShuffleFileManagerInstance(YarnShuffleServiceSuite.java:37) Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory at org.apache.spark.network.yarn.YarnShuffleServiceSuite.testCreateDefaultMergedShuffleFileManagerInstance(YarnShuffleServiceSuite.java:37) [ERROR] testCreateRemoteBlockPushResolverInstance(org.apache.spark.network.yarn.YarnShuffleServiceSuite) Time elapsed: 0 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.apache.spark.network.yarn.YarnShuffleService at org.apache.spark.network.yarn.YarnShuffleServiceSuite.testCreateRemoteBlockPushResolverInstance(YarnShuffleServiceSuite.java:47) [ERROR] testInvalidClassNameOfMergeManagerWillUseNoOpInstance(org.apache.spark.network.yarn.YarnShuffleServiceSuite) Time elapsed: 0.001 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.apache.spark.network.yarn.YarnShuffleService at org.apache.spark.network.yarn.YarnShuffleServiceSuite.testInvalidClassNameOfMergeManagerWillUseNoOpInstance(YarnShuffleServiceSuite.java:57) ``` A test suit for `YarnShuffleService` did exist here: `resource-managers/yarn/src/test/scala/org/apache/spark/network/yarn/YarnShuffleServiceSuite.scala` I missed this when I created `common/network-yarn/src/test/java/org/apache/spark/network/yarn/YarnShuffleServiceSuite.java`. Moving all the new tests to the earlier test suite fixes the failures with hadoop-2.7 even though why this happened is not clear. The newly added tests are failing when run with hadoop profile 2.7 No Ran the unit tests with the default profile as well as hadoop 2.7 profile. `build/mvn test -Dtest=none -DwildcardSuites=org.apache.spark.network.yarn.YarnShuffleServiceSuite -Phadoop-2.7 -Pyarn` ``` Run starting. Expected test count is: 11 YarnShuffleServiceSuite: - executor state kept across NM restart - removed applications should not be in registered executor file - shuffle service should be robust to corrupt registered executor file - get correct recovery path - moving recovery file from NM local dir to recovery path - service throws error if cannot start - recovery db should not be created if NM recovery is not enabled - SPARK-31646: metrics should be registered into Node Manager's metrics system - create default merged shuffle file manager instance - create remote block push resolver instance - invalid class name of merge manager will use noop instance Run completed in 2 seconds, 572 milliseconds. Total number of tests run: 11 Suites: completed 2, aborted 0 Tests: succeeded 11, failed 0, canceled 0, ignored 0, pending 0 All tests passed. ``` Closes #30349 from otterc/SPARK-32916-followup. Authored-by: Chandni Singh <singh.chandni@gmail.com> Signed-off-by: Thomas Graves <tgraves@apache.org>
What changes were proposed in this pull request?
This is a follow-up fix for the failing tests in
YarnShuffleServiceSuite.java
. This java class was introduced in #30062. The tests in the class fail when run with hadoop-2.7 profile:A test suit for
YarnShuffleService
did exist here:resource-managers/yarn/src/test/scala/org/apache/spark/network/yarn/YarnShuffleServiceSuite.scala
I missed this when I created
common/network-yarn/src/test/java/org/apache/spark/network/yarn/YarnShuffleServiceSuite.java
. Moving all the new tests to the earlier test suite fixes the failures with hadoop-2.7 even though why this happened is not clear.Why are the changes needed?
The newly added tests are failing when run with hadoop profile 2.7
Does this PR introduce any user-facing change?
No
How was this patch tested?
Ran the unit tests with the default profile as well as hadoop 2.7 profile.
build/mvn test -Dtest=none -DwildcardSuites=org.apache.spark.network.yarn.YarnShuffleServiceSuite -Phadoop-2.7 -Pyarn