Open kohlschuetter opened 1 year ago
Thanks for the great bug report!
The warning is a leftover artifact. At some point, linking native methods was somehow brittle, but this is an non-issue these days.
Sadly the logging is too coarse-grained as it uses the context logger, instead of something more specific; but you can disable the logging with --log.java.level=OFF
or SEVERE
.
Describe GraalVM and your environment :
java -Xinternalversion
:Have you verified this issue still happens when using the latest snapshot? Yes, still happening with graalvm-espresso-community-openjdk-21+35.1
Describe the issue When running my project's selftest jar, I see the following error message in the output (twice)
The method in question is a JNI no-op (hence the name, "noop"):
Code snippet or code repository that reproduces the issue
selftest from https://github.com/kohlschutter/junixsocket/
Steps to reproduce the issue
wget https://github.com/kohlschutter/junixsocket/releases/download/junixsocket-2.7.2/junixsocket-selftest-2.7.2-jar-with-dependencies.jar
java -truffle -jar junixsocket-selftest-2.7.2-jar-with-dependencies.jar
Expected behavior A clear and concise description of what you expected to happen.
No "Failed to link native method" warning
Additional context
Other than the warning, the code seems to work as expected, but the warning line is unwarranted.