Bug #9140

ISO selection in test suite "Upgrade from ISO" is fragile

Added by intrigeri 2015-03-31 09:19:19 . Updated 2015-10-17 06:33:46 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Start date:
2015-03-31
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Installer
Deliverable for:

Description

I’ve seen it fail on isotester1.lizard:

  Scenario: Upgrading an old Tails USB installation from an ISO image, running on the new version # features/usb_install.feature:234
    Given a computer                                                                              # features/step_definitions/common_steps.rb:66
    And I clone USB drive "old" to a new USB drive "to_upgrade"                                   # features/step_definitions/usb.rb:51
    And I setup a filesystem share containing the Tails ISO                                       # features/step_definitions/usb.rb:139
    And I start Tails from DVD with network unplugged and I login                                 # features/step_definitions/common_steps.rb:147
    And I plug USB drive "to_upgrade"                                                             # features/step_definitions/common_steps.rb:92
    And I do a "Upgrade from ISO" on USB drive "to_upgrade"                                       # features/step_definitions/usb.rb:144
      FindFailed: can not find USBCreateLiveUSB.png on the screen.

… so it seems that the code was already in usb_install_helper, while the previous steps (that select the ISO) have failed, as the attached screenshot shows. This should not happen.


Files


Subtasks


History

#1 Updated by intrigeri 2015-03-31 09:19:52

  • blocks #8538 added

#2 Updated by intrigeri 2015-03-31 09:20:21

anonym, kytv: this ticket wants an assignee.

#3 Updated by anonym 2015-03-31 14:14:51

  • Assignee set to anonym

#4 Updated by intrigeri 2015-05-09 03:36:33

  • Target version changed from Tails_1.4 to Tails_1.4.1

Postponing. This was added after (lots of) test suite work was organized for this cycle anyway.
So, who’ll take care of this one? Kill Your TV did quite some test writing for the Installer recently, right?

#5 Updated by intrigeri 2015-06-29 00:49:40

  • Target version changed from Tails_1.4.1 to Tails_1.5

#6 Updated by anonym 2015-08-03 10:58:34

  • Target version changed from Tails_1.5 to Tails_1.6

I’ve only tried solving this while procrastinating, but it seems to require more attention than that. I’ll have to postpone it, though. Also, I’ve never seen it myself, not even on lizard.

#7 Updated by anonym 2015-09-22 15:02:54

  • Target version changed from Tails_1.6 to Tails_1.7

#8 Updated by anonym 2015-10-17 06:33:46

  • Status changed from Confirmed to Rejected
  • Assignee deleted (anonym)

There’s been seven months, and I’ve wasted time looking into this several times without any result. I have yet to see it myself. I’m closing it to not waste more time on this. If we see it again we’re in a better position to get usable debugging info (debug log, video etc.) for a new ticket.