One addition: Solr is affected on same way.

Am 12. November 2023 21:39:07 MEZ schrieb Uwe Schindler <u...@thetaphi.de>:
>Thanks.
>
>I have the feeling it is because of same major version. If Gradle JDK is 
>Eclipse Temurin and runtime JDK is same version but OpenJ9 it fails.
>
>Interestingly only in 11 (branch 9x). On main it worked for long time. Jdk17 
>as Gradle runtime by Temurin and openj9 as runtime.
>
>If runtime and Gradle VM is identical home dir it does not fork. Here is a 
>flight difference and that matters. The alternate VM info is printed, but it 
>looks like it f*cks up when providing options and something thinks it does not 
>fork, but it does.
>
>> Task :altJvmWarning
>NOTE: Alternative java toolchain will be used for compilation and tests:
>  Project will use 11 (IBM JDK 11.0.20.1+1, home at: 
> /home/jenkins/tools/java/64bit/openj9/jdk-11.0.20)
>  Gradle runs with 11 (Eclipse Temurin JDK 11.0.21+9, home at: 
> /home/jenkins/tools/java/64bit/hotspot/jdk-11.0.21)
>
>On main branch it works, no idea why:
>
>> Task :altJvmWarning
>NOTE: Alternative java toolchain will be used for compilation and tests:
>  Project will use 17 (IBM JDK 17.0.8.1+1, home at: 
> /home/jenkins/tools/java/64bit/openj9/jdk-17.0.8)
>  Gradle runs with 17 (Eclipse Temurin JDK 17.0.9+9, home at: 
> /home/jenkins/tools/java/64bit/hotspot/jdk-17.0.9)
>
>In case you ask, die to randomized jvms the Jenkins job Always runs with 
>default temurin minimum jdk for Gradle and just exchanges runtime for testing 
>(because Gradle itself can't run on all JDKs out there).
>
>One other thing: if you set OpenJ9 as default jdk and run Gradle with it, it 
>fails while building buildSrc: it can't compile the profiling stuff as flight 
>recorder module does not ship with OpenJ9. We should possibly fix this, maybe 
>by rewriting the code with pure Groovy class and not compile it at all.
>
>Uwe
>
>Am 12. November 2023 21:08:41 MEZ schrieb Dawid Weiss <dawid.we...@gmail.com>:
>>Hi Uwe,
>>
>>Will dig tomorrow. Maybe Dawid has an idea? It looks like the alternate
>>> runtime is correctly detected, but why is Gradle passing compiler runzine
>>> options without -J in just this case. In Main the same works where Gradle
>>> runs with Java17-Temurin and J9 is used as runtime.
>>>
>>
>>I think I know what this is - please let me verify and provide a PR, if
>>it's indeed that.
>>
>>Dawid
>
>--
>Uwe Schindler
>Achterdiek 19, 28357 Bremen
>https://www.thetaphi.de
--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de

Reply via email to