otterc opened a new pull request #30349:
URL: https://github.com/apache/spark/pull/30349


   ### 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 
https://github.com/apache/spark/pull/30062. The tests from here should be moved 
to 
   
`resource-managers/yarn/src/test/scala/org/apache/spark/network/yarn/YarnShuffleServiceSuite.scala`
   
   ### 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`
   ```
   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.
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to