Bug #11190

The automated test suite harcodes the expected jvm to use

Added by anonym 2016-03-04 21:57:50 . Updated 2016-03-08 19:02:33 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Test suite
Target version:
Tails_2.2
Start date:
2016-03-04
Due date:
% Done:

100%

Feature Branch:
test/11190-guess-JAVA_HOME
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

We explicitly export JAVA_HOME="/usr/lib/jvm/java-7-openjdk-amd64" (in 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.

Subtasks

History

#1 Updated by anonym 2016-03-04 21:58:38

  • Priority changed from Normal to High

Raising priority, cause this is very inconvenient for me this close to a release.

#2 Updated by anonym 2016-03-04 22:07:28

  • Status changed from Confirmed to In Progress
  • Assignee deleted (anonym)
  • % 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.

#3 Updated by anonym 2016-03-06 19:12:09

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:e06d57e8ef76b6dfd426a718907a850f5794dded.

#4 Updated by anonym 2016-03-06 19:56:24

Edit: removed the previous comment, which was meant for Bug #11176.

Any way, I’ve seen this branch pass on Jenkins, and so merged this to make my Sid system happy.

#5 Updated by anonym 2016-03-06 19:58:16

  • QA Check set to Pass

#6 Updated by anonym 2016-03-08 19:02:33

  • Status changed from Fix committed to Resolved