Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 14 09 Nov 2024, 11:55

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
8:23.906
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.834
And no SquashFS delta is installed 0.203
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.096
And Tor is ready 24.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.061
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.327
Given I shutdown Tails and wait for the computer to power off 13.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.858
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.631
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.077
And Tor is ready 21.333
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.407
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.236
Given I shutdown Tails and wait for the computer to power off 4.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:25.860
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:559:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:515:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:326 5.009 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:54:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/01:54:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/01:54:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/01:54:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/01:54:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.018
Feature: Tails persistence
Tags: @product
56.611
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.866
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 6.424
When I try to enable persistence 0.404
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 6.765
When I repair the filesystem of the Persistent Storage 1.307
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.248
And the filesystem of the Persistent Storage was repaired 0.069
When I close the filesystem repair dialog 1.277
Then persistence is successfully enabled 31.247
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:693:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/usb.rb:691:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
features/persistence.feature:181:in `Then persistence is successfully enabled'
After features/support/hooks.rb:326 5.564 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 03:36:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/03:36:35_Manual_filesystem_repair_is_successful.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/03:36:35_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/03:36:35_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/03:36:35_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000