[jira] [Commented] (BIGTOP-3631) Gradlew failing while starting on new docker workers

["Luca Toscano (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476588#comment-17476588 ] 

Luca Toscano commented on BIGTOP-3631:
--------------------------------------

Moved worker-{2,3,6,7} in the new AWS account to jre8 (Corretto), and updated alternatives to point to it.

> Gradlew failing while starting on new docker workers
> ----------------------------------------------------
>
>                 Key: BIGTOP-3631
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3631
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Luca Toscano
>            Priority: Major
>
> Hi everybody,
> I am seeing failures in trunk package builds, all of them when starting gradlew:
> {code}
> + ./gradlew realclean -Pnexus=true -POS=fedora-33 -Pprefix=trunk zookeeper-pkg-ind --info
> Initialized native services in: /home/jenkins/.gradle/native
> Removing 0 daemon stop events from registry
> Previous Daemon (5844) stopped at Sat Jan 08 05:37:29 UTC 2022 by user or operating system
> Starting a Gradle Daemon, 1 stopped Daemon could not be reused, use --status for details
> Starting process 'Gradle build daemon'. Working directory: /home/jenkins/.gradle/daemon/5.6.4 Command: /usr/lib/jvm/java-17-amazon-corretto.x86_64/bin/java --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED -XX:MaxMetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xms256m -Xmx512m -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /home/jenkins/.gradle/wrapper/dists/gradle-5.6.4-bin/c9880aa85176bf8c458862eb99f7e0a9/gradle-5.6.4/lib/gradle-launcher-5.6.4.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 5.6.4
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 1.686 secs.
> The client will now receive all logging from the daemon (pid: 9326). The daemon log file: /home/jenkins/.gradle/daemon/5.6.4/daemon-9326.out.log
> Starting build in new daemon [memory: 536.9 MB]
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Using 4 worker leases.
> Starting Build
> java.lang.NoClassDefFoundError: Could not initialize class org.codehaus.groovy.vmplugin.v7.Java7
> 	at org.codehaus.groovy.vmplugin.VMPluginFactory.<clinit>(VMPluginFactory.java:43)
> 	at org.codehaus.groovy.reflection.GroovyClassValueFactory.<clinit>(GroovyClassValueFactory.java:35)
> 	at org.codehaus.groovy.reflection.ClassInfo.<clinit>(ClassInfo.java:109)
> 	at org.codehaus.groovy.reflection.ReflectionCache.getCachedClass(ReflectionCache.java:95)
> {code}
> https://ci.bigtop.apache.org/job/Bigtop-trunk-packages/COMPONENTS=zookeeper,OS=fedora-33/lastBuild/console
> In the new docker nodes there seems to me a more up-to-date jdk version, java-17-amazon-corretto, that doesn't seem to be compatible with the gradle version set in the bigtop repository (see https://docs.gradle.org/current/userguide/compatibility.html).
> We could follow this guide to install java8:
> https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/amazon-linux-install.html
> The alternative is to upgrade gradle but it seems more invasive.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)