Tails

#1 Updated by bertagaz 2016-02-09 11:20:36

• Target version set to Tails_2.4

#2 Updated by intrigeri 2016-02-09 18:35:55

• Deliverable for set to 270

#3 Updated by intrigeri 2016-02-09 18:36:55

• Subject changed from Deal with April false positive scenarios to Deal with April 2016 false positive scenarios

#4 Updated by bertagaz 2016-05-03 05:55:01

• Assignee changed from intrigeri to bertagaz

Taking over this one. I’ve made a good part of it while doing Bug #11084, and I’ll try to finish this one before the CI meeting (which will probably just means implementing what we came up with on Bug #11083 and Bug #11084).

#6 Updated by bertagaz 2016-05-04 08:43:37

• Status changed from Confirmed to In Progress
• % Done changed from 0 to 50

So in April, we had 5 test suite run failures (for the stable and devel branch). Not much

• devel #281 with

cucumber features/i2p.feature:12 # Scenario: I2P is enabled when the "i2p" boot parameter is added
    Step failed while creating checkpoint: the Tails desktop is ready
    Given I have started Tails from DVD with I2P enabled and logged in # features/step_definitions/snapshots.rb:208
      FindFailed: can not find GnomeSystrayFlorence.png on the screen.

This is the only time in all of our test_Tails_ISO_* logs this bug happen. If you have a look at the screenshot, you’ll notice that indeed the Florence icon is a bit weird. Not sure we have to flag this as @fragile.

• stable #243 with the 3 usual suspects:

cucumber features/root_access_control.feature:25 # Scenario: If no administrative password is set in Tails Greeter the live user \
  should not be able to get administrative privileges through PolicyKit with the standard passwords.
cucumber features/encryption.feature:32 # Scenario: Symmetric encryption and decryption using OpenPGP Applet
cucumber features/evince.feature:24 # Scenario: I cannot view a PDF file stored in non-persistent /home/amnesia/.gnupg

One has already been tagged as @fragile. I’ll take care of the others tomorrow.

• stable #245, #253 and devel #287 which failed because of the main suspect already tagged as @fragile.

cucumber features/encryption.feature:32 # Scenario: Symmetric encryption and decryption using OpenPGP Applet

#9 Updated by bertagaz 2016-05-05 07:35:40

• Status changed from In Progress to Resolved
• Assignee deleted (bertagaz)
• % Done changed from 50 to 100
• QA Check deleted (Dev Needed)

intrigeri wrote:
> I bet it’s related to Bug #10576. If this happens so rarely, indeed let’s not mark it as fragile, but let’s keep an eye on it to see if it happens again.

Probably yes, let’s do that.

> OK. Let’s keep this ticket open until this has happened.

Done with Bug #11338, seems they share the same root cause. Closing this ticket then.

> So in summary, once we’ll have marked as fragile all those, we should get almost no false positives anymore!

yep, we’ll see with the May fragile pass, but hopefully we should be good.