Re: Question about ASDF test failure on ABCL
Mark Evenson <[email protected]> Tue, 24 Mar 2026 05:55:51 +1300
| Newsgroups | gmane.editors.j.devel |
|---|---|
| Message-ID | <b127c06b-e396-4578-a273-af43f9f1416d__43211.3823060476$1774286661$gmane$org@panix.com> |
On 3/23/26 10:06, Robert Goldman wrote:
> The ASDF test test-run-program-unix.script on ABCL 1.9.3 failed on linux
> (the test platform). The docker image used is |clfoundation/abcl:1.9.3-
> noble-jdk-21|. Here is the error message:
>
> |The following error was encountered: Java exception
> 'java.lang.reflect.InaccessibleObjectException: Unable to make field
> private final int java.lang.ProcessImpl.pid accessible: module java.base
> does not "opens java.lang" to unnamed module @6d59a85b'. |
I believe this error stems from the need for post-openjdj11 runtimes to
be invoked with specific runtime switches "unsealing" JVM modules to
allow ABCL to perform dynamic introspection.
In the case of "does not opens java.lang" the switch would be:
java --add-opens java.base/java.lang=ALL-UNNAMED [...]
The necessary switches are viewable in the [CI scripting used to test
ABCL][1].
[1]:
https://github.com/armedbear/abcl/blob/master/ci/create-abcl-properties.bash#L16
The ABCL Ant build system has targets of the form
"abcl.properties.autoconfigure.openjdk.N" where N denotes the integer of
the JDK version which are perhaps the most user-accessible portions
which can be used when building ABCL like
ant abcl.properties.autoconfigure.openjdk.21 abcl
Since I gather that you are encountering these errors in using Docker
images, you would unfortunately probably need to rebuild these Docker
images with these switches present in the ABCL invocation script.
--
"A screaming comes across the sky. It has happened before but there is
nothing to compare to it now."