www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler" <uschind...@apache.org>
Subject Lucene jenkins slave no longer has "latest1.8" JDK version - all builds fail
Date Sat, 19 Mar 2016 09:02:03 GMT
Hi,

Our Jobs on the "lucene" Jenkins Slave use the "latest1.8" setting for the JDK in the build.
This now fails and falls back to the Ubuntu-provided default JDK (Java 7). The log output
shows everything:

Started by user uschindler
[EnvInject] - Loading node environment variables.
Building remotely on lucene in workspace /home/jenkins/jenkins-slave/workspace/Solr-Artifacts-6.x
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/lucene-solr.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/lucene-solr.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress git://git.apache.org/lucene-solr.git
+refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch_6x^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch_6x^{commit} # timeout=10
Checking out Revision 5c50124246805e11fed94dac16095a145074f096 (refs/remotes/origin/branch_6x)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 5c50124246805e11fed94dac16095a145074f096
 > git rev-list 5c50124246805e11fed94dac16095a145074f096 # timeout=10
No emails were triggered.
Invalid tool ID 
[solr] $ /home/jenkins/jenkins-slave/tools/hudson.tasks.Ant_AntInstallation/ant-1.8.2/bin/ant
-file build.xml -Dlucene.javadoc.url=https://builds.apache.org/job/Lucene-Artifacts-trunk/javadoc/
-Dversion.suffix=19 prepare-release-no-sign
Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-7-openjdk-amd64/lib/tools.jar
Buildfile: /x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-6.x/solr/build.xml

BUILD FAILED
/x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-6.x/solr/build.xml:39: The following error
occurred while executing this line:
/x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-6.x/solr/common-build.xml:55: The following
error occurred while executing this line:
/x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-6.x/lucene/module-build.xml:27: The following
error occurred while executing this line:
/x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-6.x/lucene/common-build.xml:302: Minimum
supported Java version is 1.8.


You see two things: "Invalid tool ID" - it looks like "latest1.8" is no longer a valid tool.
But it is still in the config list for the jobs. It would also be a major problem for us if
we have to change it for like hundred Jobs :)
Because of this JAVA_HOME is not set, so Apache Ant (used by build) falls back to the JVM
that ran slave.jar and was in path - but this is an JRE and Java 7 only: " Unable to locate
tools.jar. Expected to find it in /usr/lib/jvm/java-7-openjdk-amd64/lib/tools.jar"

This started at some time yesterday. Would it be possible to fix this as soon as possible,
because the Lucene mailing lists are flooded by failed job notifications? For now I can just
disable all jobs.

This could also be related to the problem Lukasz Lenart has seen with his builds.

Uwe

-----
Uwe Schindler
uschindler@apache.org 
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
http://lucene.apache.org/



Mime
View raw message