Bug #7175

Sikuli is broken with openjdk 6b31-1.13.3-1~deb7u1

Added by anonym 2014-05-08 14:12:27 . Updated 2014-07-22 22:51:39 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Test suite
Target version:
Tails_1.1
Start date:
2014-06-21
Due date:
% Done:

100%

Feature Branch:
bugfix/7175-openjdk-7
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

After upgrading (on Wheezy) openjdk from 6b27-1.12.6-1~deb7u1 to 6b31-1.13.3-1~deb7u1 (to fix DSA-2912-1) sikuli cannot initialize in our automated test suite. I get the following error:

no VisionProxy in java.library.path (UnsatisfiedLinkError)
/home/anonym/src/tails-master/features/support/helpers/sikuli_helper.rb:24:in `import'
[...]

Reverting back to the following packages and versions fixes the issue:

  • icedtea-6-jre-cacao:amd64 6b27-1.12.6-1~deb7u1
  • openjdk-6-jre-lib:amd64 6b27-1.12.6-1~deb7u1
  • openjdk-6-jre-headless:amd64 6b27-1.12.6-1~deb7u1
  • icedtea-6-jre-jamvm:amd64 6b27-1.12.6-1~deb7u1
  • openjdk-6-jdk:amd64 6b27-1.12.6-1~deb7u1
  • openjdk-6-jre:amd64 6b27-1.12.6-1~deb7u1

The following launchpad bug may be relevant, but offer little in terms of details and solutions (at least it indicates that it’s a general issue not related to e.g. us using ruby-rjb): https://answers.launchpad.net/sikuli/+question/242313

Can someone else please confirm this (optimistically assigning to intrigeri since I know he’s got a working test suite setup)? Then I suppose we should at least file a Debian bug.

Subtasks

Feature #7428: Reproduce test suite problem with openjdk 6b31-1.13.3-1~deb7u1 Resolved intrigeri

100

History

#1 Updated by intrigeri 2014-05-08 15:03:54

> Can someone else please confirm this (optimistically assigning to intrigeri since
> I know he’s got a working test suite setup)? Then I suppose we should at least file
> a Debian bug.

Please file a Debian bug first: a regression in stable is a serious
matter, and the relevant maintainers should be made aware of it ASAP.

Then, I’ll try to reproduce this (no idea if this can happen before
1.1, and we should definitely not be blocking on this to report a bug
to the right people).

#2 Updated by intrigeri 2014-05-09 12:07:07

  • Assignee changed from intrigeri to anonym
  • Priority changed from Normal to Elevated

#3 Updated by intrigeri 2014-05-09 13:29:55

  • Status changed from New to Confirmed
  • Parent task set to Feature #6315

#4 Updated by anonym 2014-05-09 13:53:31

Filed as Debian bug #747506.

#5 Updated by intrigeri 2014-05-15 01:32:16

  • Type of work changed from Upstream to Debian

#6 Updated by BitingBird 2014-06-21 13:30:53

  • Target version set to Hole in the Roof

parent ticket is hole in the roof -> target version for the subtasks :)

#7 Updated by intrigeri 2014-06-30 11:39:42

I could reproduce this bug, and workaround it by using openjdk-7 instead of openjdk-6:

--- a/run_test_suite
+++ b/run_test_suite
@@ -180,7 +180,7 @@ if [ -n "${VNC_VIEWER}" ]; then
     start_vnc_viewer
 fi

-export JAVA_HOME="/usr/lib/jvm/java-6-openjdk-amd64"
+export JAVA_HOME="/usr/lib/jvm/java-7-openjdk-amd64"
 export SIKULI_HOME="/usr/share/java"
 export DISPLAY=${TARGET_DISPLAY}
 check_dependency cucumber

I think that’s the way to go, and will be a nice first step on the road to Feature #7212.
This also requires updating the test suite setup instructions.

#8 Updated by intrigeri 2014-07-18 13:00:31

  • Assignee changed from anonym to intrigeri
  • Type of work changed from Debian to Code

#9 Updated by intrigeri 2014-07-18 13:02:37

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to anonym
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/7175-openjdk-7

#10 Updated by anonym 2014-07-20 19:04:38

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • Target version changed from Hole in the Roof to Tails_1.1
  • QA Check changed from Ready for QA to Pass

#11 Updated by BitingBird 2014-07-22 22:51:40

  • Status changed from Fix committed to Resolved