022203a471
Replace the Gerrit 3.9 test job with one for 3.10 (what OpenDev is currently using). Also update to the latest available OpenJDK in preparation for adding a 3.11 job later. For now leave the 3.4 default job as-is, but we'll likely need to update this when we drop support for additional Python versions. It appears that Gerrit startup may be finding itself in an infinite loop looking for the Java installation (as evidenced strace reporting gerrit.sh calling dirname over and over which happens in a loop to find JAVA_HOME). The golden site does set the javaHome value so we can avoid this discovery loop entirely if we preserve that configuration. Do so. It is curious that this doesn't happen with Java 17 but does seem to happen with 21. Must be some difference in the packaging that impacts gerrit.sh's lookup function? Also capture Gerrit's startup output and attach it to test cases. May be useful for debugging Gerrit startup problems before Gerrit is able to write its own log files, as it was for figuring out the javaHome problem above. Change-Id: Id74cf11dfee00a7635dd9ab39dda3a4e54ae5370 Co-Authored-By: Clark Boylan <cboylan@sapwetik.org>
7 lines
259 B
Plaintext
7 lines
259 B
Plaintext
# This is a cross-platform list tracking distribution packages needed for
|
|
# install and tests; see http://docs.opendev.org/opendev/bindep/ for additional
|
|
# information.
|
|
|
|
openjdk-11-jdk [test platform:ubuntu-bionic]
|
|
openjdk-21-jdk [test platform:ubuntu-noble]
|