Sergey Nuyanzin created FLINK-39803:
---------------------------------------
Summary: E2E tests fail due to native access and deprecated method
warnings on JDK 25
Key: FLINK-39803
URL: https://issues.apache.org/jira/browse/FLINK-39803
Project: Flink
Issue Type: Sub-task
Components: Build System / CI, Test Infrastructure
Reporter: Sergey Nuyanzin
Assignee: Sergey Nuyanzin
When using restricted or terminally deprecated methods, the JVM prints
warnings on JDK 25 like below:
{noformat}
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: java.lang.System::setSecurityManager has been called by
org.apache.flink.runtime.security.NoOpSecurityManager
WARNING: A restricted method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by
org.apache.flink.core.memory.MemorySegment
WARNING: Use --enable-native-access to avoid a warning for callers in this
module
WARNING: Restricted methods will be blocked in a future release unless native
access is enabled
{noformat}
These are printed into the .out file of the processes, and cause e2e tests to
fail since we check for empty .out files.
These warnings cannot be suppressed without {{--enable-native-access}}, which
would require changes across the entire module structure. They also occur in
third-party libraries (e.g. Netty, Kryo), so we cannot simply
Additionally, empty lines appearing in .out files can cause false positives
and should also be excluded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
