Closed spoon-bot closed 1 month ago
Build was fixed!
Build was fixed!
Build was fixed!
Build was fixed!
Build was fixed!
Build was fixed!
Many of our jenkins builds are failling with
Unknown host repo.maven.apache.org: Temporary failure in name resolution
Build was fixed!
Build was fixed!
Build was fixed!
Build was fixed!
Not a regression, this is caused by gumtree-spoon bumping the Java version to 11 (https://github.com/SpoonLabs/gumtree-spoon-ast-diff/commit/6f9ca09e93c53c91f54f51464aba3dd484762106), while the Jenkins job is running JDK8.
Thanks for the diagnostic, would you be able to fix the Jenkins job?
I think so, I'll have a look at it this afternoon.
Cool!
There's a problem here I'm not sure what to do about. Both nodes run Ubuntu (one runs Ubuntu 16 the other 18) and OpenJDK8. The openJDK-native-plugin that's installed makes it seem like we can just select JDK 11, but the documentation for that plugin makes it clear that it's only compatible with distros that use RPM packages (which Ubuntu does not).
Curiously, the Ubuntu 18 node is labeled with java11
, but it doesn't appear to actually have JDK 11 installed, it uses JDK 8. Should we perhaps reconfigure that node to actually run with OpenJDK 11?
Done! just installed openjdk11 on executor sos-builder02, in /usr/lib/jvm/java-11-openjdk-amd64/
So I've been trying to get this working for an hour now, and I'm pretty sure you actually installed OpenJDK 10 into that path. I ran this Groovy script on the node:
def sout = new StringBuilder(), serr = new StringBuilder()
def proc = '/usr/lib/jvm/java-11-openjdk-amd64/bin/java -version'.execute()
proc.consumeProcessOutput(sout, serr)
proc.waitForOrKill(1000)
println serr
And got this back:
openjdk version "10.0.1" 2018-04-17
OpenJDK Runtime Environment (build 10.0.1+10-Ubuntu-3ubuntu1)
OpenJDK 64-Bit Server VM (build 10.0.1+10-Ubuntu-3ubuntu1, mixed mode)
Is it possible you made a mistake in installing the JDK?
Ps. I've learned a ton about Jenkins today from fiddling around with it, so it hasn't been a waste of time even if this turns out to be the problem :)
openjdk version "10.0.1" 2018-04-17
Confirmed on the machine with /usr/lib/jvm/java-11-openjdk-amd64/bin/java -version
Is it possible you made a mistake in installing the JDK?
No. I did aptitude install openjdk-11-jdk-headless
Let me aptitude update
and aptitude full-upgrade
Let me aptitude update and aptitude full-upgrade
Did so, nothing changes.
This is a known issue: https://askubuntu.com/questions/1037646/why-is-openjdk-10-packaged-as-openjdk-11
But it should be resolved? The top answer states that as of the 19th of April 2019, the version is correct. Have you updated the package index (apt update
, I think it is)?
Problem fixed:
# /usr/lib/jvm/java-11-openjdk-amd64/bin/java -version
openjdk version "11.0.9.1" 2020-11-04
The fix was to change the update channel from bionic
to bionic-updates
. Sigh.
Build was fixed!
GREAT SUCCESS! :)
Nice, thanks Simon for the debugging.
Build was fixed!
@monperrus The ubuntu18 node has no storage space left. Could you set up an auto-clean of /tmp
or alternatively an auto-reboot of the node?
Build was fixed!
Build was fixed!
@monperrus Out of space again: https://ci.inria.fr/sos/job/gumtree-spoon-ast-diff/1771/console
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 970M 0 970M 0% /dev
tmpfs 200M 21M 179M 11% /run
/dev/sda1 18G 12G 5.6G 67% /
Did somebody clean anything?
All of the builds on the Ubuntu 18 node fail with this error:
java.io.IOException: No space left on device
But I agree, it sure looks like there is space left...
Build was fixed!
See https://ci.inria.fr/sos/job/gumtree-spoon-ast-diff/