The automated test suite harcodes the expected jvm to use
We explicitly export
run_test_suite) effectively hardcoding that Java 7 should be used. This breaks the automated test suite in current Debian Sid, which has Java 8.
There are two fixes, either to use
/usr/lib/jvm/default-java, or to not set it at all, and rely on the Debian specific
0005-Fill-JAVA_HOME-with-a-sensible-value-if-not-set-when.patch which I think I am partial to. Both fixes the issue on Sid for me.
Let ruby-rjb guess JAVA_HOME instead fixing on one jvm version.
The appropriate jvm to use differs between Debian versions, so setting
a specific one is not convenient when supporting multiple Debian
versions. For instance, the current hardcoded value, which fixes on
the Java 7 jvm, breaks rjb in Debian Sid, so the automated test suite
cannot be run at all.
Let's instead not set it explicitly, and rely on the Debian-specific
jvm guessing mechanism.
#2 Updated by anonym over 3 years ago
- Status changed from Confirmed to In Progress
- Assignee deleted (
- % Done changed from 0 to 50
- Feature Branch set to test/11190-guess-JAVA_HOME
A review would be welcome, in particular if someone could try this on Debian Jessie. But if this doesn't break the test suite on Jenkins' isotesters I'll probably merge it myself any way.