attilapiros commented on PR #55720: URL: https://github.com/apache/spark/pull/55720#issuecomment-4493664189
The `--sun-misc-unsafe-memory-access=allow` flag solves the problem: ``` [INFO] --- scalatest:2.2.0:test (test) @ spark-connect-client-jvm_2.13 --- [INFO] ScalaTest report directory: /Users/apiros/git/attilapiros/spark3_II/sql/connect/client/jvm/target/surefire-reports WARNING: Using incubator modules: jdk.incubator.vector WARNING: package sun.security.action not in java.base Discovery starting. Discovery completed in 110 milliseconds. Run starting. Expected test count is: 1 AmmoniteReplE2ESuite: WARNING: Using incubator modules: jdk.incubator.vector WARNING: package sun.security.action not in java.base WARNING: A terminally deprecated method in sun.misc.Unsafe has been called WARNING: sun.misc.Unsafe::allocateMemory has been called by io.netty.util.internal.PlatformDependent0$2 (file:/Users/apiros/.m2/repository/io/netty/netty-common/4.2.13.Final/netty-common-4.2.13.Final.jar) WARNING: Please consider reporting this to the maintainers of class io.netty.util.internal.PlatformDependent0$2 WARNING: sun.misc.Unsafe::allocateMemory will be removed in a future release Ready for client connections. - SPARK-56448: restarting spark-shell --remote does not throw NPE Run completed in 19 seconds, 109 milliseconds. Total number of tests run: 1 Suites: completed 1, aborted 0 Tests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0 All tests passed. No more client connections. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 33.246 s [INFO] Finished at: 2026-05-19T18:21:40-07:00 [INFO] ------------------------------------------------------------------------ ➜ spark3_II git:(bd8872a0cc7) ✗ java -version openjdk version "25.0.3" 2026-04-21 LTS OpenJDK Runtime Environment Temurin-25.0.3+9 (build 25.0.3+9-LTS) ``` -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
