-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-39464][CORE][TESTS][FOLLOWUP] Use Utils.localHostNameForURI instead of Utils.localCanonicalHostName in tests #36876
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 Is the following steps of manually verifying SPARK-39464 correct?
I found the master branch still test failed with above commands. |
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.
I found the master branch still test failed with above commands.
For your question, as I wrote in #36868 , I verified it with the following commands.
$ SERIAL_SBT_TESTS=1 SPARK_LOCAL_HOSTNAME='[2600:.(omitted)..:60cd]' build/sbt "core/test" -Djava.net.preferIPv6Addresses=true -Dtest.exclude.tags=org.apache.spark.tags.ExtendedLevelDBTest
...
[info] Run completed in 18 minutes, 43 seconds.
[info] Total number of tests run: 2950
[info] Suites: completed 284, aborted 0
[info] Tests: succeeded 2950, failed 0, canceled 4, ignored 8, pending 0
[info] All tests passed.
[info] Passed: Total 3214, Failed 0, Errors 0, Passed 3214, Ignored 8, Canceled 4
[success] Total time: 1189 s (19:49), completed Jun 14, 2022, 4:45:55 PM
Thank you for your reply. Let me have a try |
|
|
||
| test("Kill one host") { | ||
| testKillWorkers(Seq("${Utils.localCanonicalHostName()}")) | ||
| testKillWorkers(Seq(s"${Utils.localHostNameForURI()}")) |
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.
Should this line be changed to Seq(s"${Utils.localCanonicalHostName()}")
|
For this PR, I'll revisit today, @LuciferYang . And, since you are interested in this work, here is the detail of my Jenkins conf on Java 17. The following modules are passed already.
|
|
@LuciferYang . Here is a doc PR for your question. |
|
BTW, if you are using Mac, please disable |
Thanks, fell asleep yesterday... I'll try this today |
|
Yes, using |
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.
Do we need this patch still, @LuciferYang ?
On master branch, could you confirm the following again? It works for me.
$ SPARK_LOCAL_IP=::1 SBT_OPTS=-Djava.net.preferIPv6Addresses=true build/sbt "core/testOnly org.apache.spark.deploy.master.MasterSuite"
[info] MasterSuite:
[info] - can use a custom recovery mode factory (524 milliseconds)
[info] - master correctly recover the application (56 milliseconds)
[info] - master/worker web ui available (392 milliseconds)
[info] - master/worker web ui available with reverseProxy (30 seconds, 160 milliseconds)
[info] - master/worker web ui available behind front-end reverseProxy (30 seconds, 127 milliseconds)
[info] - basic scheduling - spread out (22 milliseconds)
[info] - basic scheduling - no spread out (12 milliseconds)
[info] - basic scheduling with more memory - spread out (10 milliseconds)
[info] - basic scheduling with more memory - no spread out (9 milliseconds)
[info] - scheduling with max cores - spread out (9 milliseconds)
[info] - scheduling with max cores - no spread out (29 milliseconds)
[info] - scheduling with cores per executor - spread out (9 milliseconds)
[info] - scheduling with cores per executor - no spread out (9 milliseconds)
[info] - scheduling with cores per executor AND max cores - spread out (10 milliseconds)
[info] - scheduling with cores per executor AND max cores - no spread out (9 milliseconds)
[info] - scheduling with executor limit - spread out (9 milliseconds)
[info] - scheduling with executor limit - no spread out (8 milliseconds)
[info] - scheduling with executor limit AND max cores - spread out (8 milliseconds)
[info] - scheduling with executor limit AND max cores - no spread out (9 milliseconds)
[info] - scheduling with executor limit AND cores per executor - spread out (8 milliseconds)
[info] - scheduling with executor limit AND cores per executor - no spread out (8 milliseconds)
[info] - scheduling with executor limit AND cores per executor AND max cores - spread out (8 milliseconds)
[info] - scheduling with executor limit AND cores per executor AND max cores - no spread out (8 milliseconds)
[info] - SPARK-13604: Master should ask Worker kill unknown executors and drivers (23 milliseconds)
[info] - SPARK-20529: Master should reply the address received from worker (19 milliseconds)
[info] - SPARK-27510: Master should avoid dead loop while launching executor failed in Worker (46 milliseconds)
[info] - All workers on a host should be decommissioned (37 milliseconds)
[info] - No workers should be decommissioned with invalid host (33 milliseconds)
[info] - Only worker on host should be decommissioned (23 milliseconds)
[info] - SPARK-19900: there should be a corresponding driver for the app after relaunching driver (2 seconds, 50 milliseconds)
[info] - assign/recycle resources to/from driver (30 milliseconds)
[info] - assign/recycle resources to/from executor (29 milliseconds)
[info] Run completed in 1 minute, 5 seconds.
[info] Total number of tests run: 32
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 32, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.
[success] Total time: 71 s (01:11), completed Jun 17, 2022, 4:20:08 PM
|
@dongjoon-hyun with |
|
In addition, I have disabled firewall. If Maven fails is expected, I will close this pr first |
|
I'm going to revisit this later after stabilizing SBT first. |
|
Just allow me more time to validate your patch, @LuciferYang . Thank you for your patience. |
|
BTW, may I ask if you did try to use
|
Also fail. I am going to add some logs today to investigate the difference between maven and sbt |
|
Sorry for the too much delay . Let me merge this. Thanks, @LuciferYang . |
|
thanks @dongjoon-hyun |

What changes were proposed in this pull request?
This PR aims to use
Utils.localHostNameForURIinstead ofUtils.localCanonicalHostNamein the following suites which changed in #36866MasterSuiteMasterWebUISuiteRocksDBBackendHistoryServerSuiteWhy are the changes needed?
These test cases fails when we run with
SPARK_LOCAL_IP=::1and-Djava.net.preferIPv6Addresses=trueDoes this PR introduce any user-facing change?
No
How was this patch tested?
export SPARK_LOCAL_IP=::1-Djava.net.preferIPv6Addresses=trueto MAVEN_OPTS, for example:RocksDBBackendHistoryServerSuite,MasterSuiteandMasterWebUISuiteBefore
RocksDBBackendHistoryServerSuite:
MasterSuite:
MasterWebUISuite:
After
RocksDBBackendHistoryServerSuite:
MasterSuite:
MasterWebUISuite: