Feature #10900

"I should be able to install a package using Synaptic" step is fragile

Added by intrigeri 2016-01-12 10:33:13 . Updated 2016-09-20 16:50:04 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_2.6
Start date:
2016-01-12
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

  Scenario: Install packages using Synaptic                                                                        # features/apt.feature:23
    When I start Synaptic                                                                                          # features/step_definitions/apt.rb:52
    And I update APT using Synaptic                                                                                # features/step_definitions/apt.rb:31
    Then I should be able to install a package using Synaptic                                                      # features/step_definitions/apt.rb:37
      FindFailed: can not find SynapticChangesAppliedPrompt.png on the screen.
      Line ?, in File ? (RuntimeError)
      features/apt.feature:26:in `Then I should be able to install a package using Synaptic'

… while the screenshot does show the “Changes applied” dialog. Timeout bump?

Subtasks

Related issues

Blocked by Tails - Bug #10441: Synaptic test is fragile Resolved 2015-10-28

History

#1 Updated by anonym 2016-01-27 14:36:49

  • Target version changed from Tails_2.0 to Tails_2.2

#2 Updated by intrigeri 2016-02-05 13:34:40

  • Parent task deleted (Feature #7563)
  • Deliverable for changed from 268 to 270

#3 Updated by intrigeri 2016-02-05 13:34:51

#4 Updated by intrigeri 2016-02-05 13:35:00

  • Subject changed from "I should be able to install a package using Synaptic" step is fragile on Jessie to "I should be able to install a package using Synaptic" step is fragile

#5 Updated by anonym 2016-02-20 13:28:03

  • blocked by Bug #10441: Synaptic test is fragile added

#6 Updated by anonym 2016-02-20 13:29:25

  • Assignee changed from anonym to kytv
  • Target version changed from Tails_2.2 to Tails_2.4

Given that you have Bug #10441 alrady, I assign this one to you since it’s in the same scenario.

#7 Updated by anonym 2016-03-03 15:52:21

  • Assignee changed from kytv to anonym

I’ll try to improve this with Chutney (Feature #9521) and/or dogtail (Feature #7729) depending on exactly what the problem is.

#8 Updated by anonym 2016-06-02 15:28:25

  • Feature Branch set to test/10441-synaptic-test-is-fragile

Let’s fix everything related to synaptic in the same branch.

It’s worth noting that despite the fact that synaptic runs as root dogtail can deal with it! Wow! Is this due to /usr/bin/synaptic-pkexec? It would be amazing if that is the case, and we can use that for the chroot browser and other applications run as non-amnesia in the X session.

#9 Updated by intrigeri 2016-06-05 13:09:34

  • Target version changed from Tails_2.4 to Tails_2.6
  • Deliverable for deleted (270)

#10 Updated by intrigeri 2016-07-13 14:09:34

  • Assignee changed from anonym to bertagaz
  • Target version changed from Tails_2.6 to Tails_2.5
  • QA Check set to Info Needed

Is the branch you proposed on Bug #10441 supposed to address this problem as well? It seems that we need to fix that, before we un-fragilize this scenario.

#11 Updated by bertagaz 2016-07-15 08:44:00

  • Assignee changed from bertagaz to intrigeri

intrigeri wrote:
> Is the branch you proposed on Bug #10441 supposed to address this problem as well? It seems that we need to fix that, before we un-fragilize this scenario.

To be honest I’ve never seen this bug in my many runs (nor in Jenkins short memory). Note that it seems to have been created before Tails Jessie, might as well have disappeared this way. Maybe we can consider that the retry_for logic is helping here already?

#12 Updated by intrigeri 2016-07-15 08:55:45

  • Assignee changed from intrigeri to anonym

> To be honest I’ve never seen this bug in my many runs (nor in Jenkins short memory).

Cool.

> Note that it seems to have been created before Tails Jessie, might as well have disappeared this way.

It initially had Feature #7563 as its parent, so I doubt it comes from the Wheezy area. Anyway, let’s try and see. As long as we’re good enough at marking stuff as fragile again if needed, we should be good.

> Maybe we can consider that the retry_for logic is helping here already?

Perhaps.

I’ll let anonym decide.

#13 Updated by intrigeri 2016-07-21 06:37:15

  • Assignee changed from anonym to intrigeri

#14 Updated by intrigeri 2016-07-21 06:38:10

  • Assignee changed from intrigeri to anonym
  • Target version changed from Tails_2.5 to Tails_2.6

#15 Updated by anonym 2016-08-31 04:15:33

  • Status changed from Confirmed to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • QA Check changed from Info Needed to Pass
  • Feature Branch deleted (test/10441-synaptic-test-is-fragile)

Given that Bug #10441 removed the @fragile tag from the only scenario using this step, let’s try closing this branch, and reopen it if the problem reappears.

#16 Updated by anonym 2016-09-20 16:50:04

  • Status changed from Fix committed to Resolved