Tails

#1 Updated by intrigeri 2014-05-12 07:46:24

• blocks Feature #6400: Add Rjb support to ruby-sikuli added

#2 Updated by intrigeri 2014-05-12 07:47:15

• Assignee set to anonym
• Target version set to Sustainability_M1

As discussed on tails-dev, making sure our test suite’s dependencies won’t break to often is definitely an important sustainability matter. Then, we can make a decision about Feature #6400.

#3 Updated by intrigeri 2014-05-12 07:50:07

• Priority changed from Normal to Elevated

Blocks a ticket that has priority = elevated => raising priority accordingly.

#4 Updated by intrigeri 2014-08-26 23:23:46

• Target version changed from Sustainability_M1 to Tails_1.2

Doing this after 1.2 will be too late.

#5 Updated by intrigeri 2014-09-27 09:12:38

• Assignee changed from anonym to intrigeri

I’ll take care of that one (being bold, and just upgrading my current testing VM to Jessie — fingers crossed).

#6 Updated by intrigeri 2014-09-27 11:12:53

• Status changed from Confirmed to In Progress
• Assignee changed from intrigeri to anonym
• % Done changed from 0 to 10

OK, tried it, and the xprop command that checks that virt-viewer is started always failed. With this change, it successes:

--- a/features/support/helpers/display_helper.rb
+++ b/features/support/helpers/display_helper.rb
@@ -1,3 +1,4 @@
+# -*- coding: undecided -*-

 class Display

@@ -38,11 +39,8 @@ class Display
   end

   def active?
-    p = IO.popen("xprop -display #{@x_display} " +
-                 "-name '#{@domain} (1) - Virt Viewer' 2>/dev/null")
-    Process.wait(p.pid)
-    p.close
-    $? == 0
+    system "xprop -display #{@x_display} " +
+           "-name '#{@domain} (1) - Virt Viewer' >/dev/null 2>&1"
   end

   def stop_virtviewer

… but then, FindFailed: can not find TailsBootSplash.png on the screen.

If I run the xprop command by hand, it works fine and confirms that virt-viewer is running.

anonym, can you reproduce this? It looks like a problem in the way sikuli talks to the display.

#7 Updated by intrigeri 2014-10-02 06:53:05

• Priority changed from Elevated to High

Note that it would be good to see this fixed before the Jessie freeze, in case that’s a bug in Debian. Fixed packages must be uploaded by October 20, which leaves us 2 weeks to diagnose whether the bug is in Debian or in our stuff, and if the former, to get a fixed package uploaded => raising priority.

#8 Updated by anonym 2014-10-16 08:11:06

• Target version changed from Tails_1.2 to Tails_1.2.1

#9 Updated by intrigeri 2014-10-20 14:57:53

• blocks #8117 added

#10 Updated by intrigeri 2014-10-20 15:00:06

• blocks Feature #8165: Make our automated test suite run in a Jessie environment added

#11 Updated by anonym 2014-11-06 14:05:25

• Status changed from In Progress to Resolved
• Assignee deleted (anonym)
• % Done changed from 10 to 100

The automated test suite runs fine in Jessie after some adjustments (will post what I discovered to Feature #8165). To be clear, AFAICT, nothing is wrong with the state of the packages in Jessie.