Project Number Date
test_Tails_ISO_feature-trixie 40 27 Jun 2025, 08:20

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 53 3 31 0 0 87 4 3 7 1:4:19.173 Failed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
3:16.268
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.239
When I start Tails from USB drive "old" with network unplugged 2:42.472
Then the boot device has safe access rights 3.268
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:330 3.508
After features/support/hooks.rb:100 0.030
Tags: @product
3:26.310
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 2:36.652
Then Tails is running from USB drive "old" 0.789
And I create a persistent partition 32.706
And I take note of which tps features are available 2.647
Then a Tails persistence partition exists on USB drive "old" 0.937
And I shutdown Tails and wait for the computer to power off 12.367
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
3:56.735
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:12.111
Then Tails is running from USB drive "old" 1.093
And all tps features are active 2.154
When I write some files expected to persist 2.056
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.641
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 9.503
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.848
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.029
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.165
And I log in to a new session 32.749
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.508
And I plug USB drive "to_upgrade" 3.695
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.592
Then the running Tails is installed on USB drive "to_upgrade" 21.884
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 2.779
After features/support/hooks.rb:100 0.000
Tags: @product
5:12.341
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 5:12.131
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:600:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:541: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:287: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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 6.079 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:41:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/02:41:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/02:41:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/02:41:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/02:41:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
22:51.711
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.452
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.450
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.066
And Tor is ready 25.277
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:12.549
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
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:330 5.816 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:04:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/03:04:52_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_feature-trixie/40/artifact/build-artifacts/03:04:52_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/03:04:52_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/03:04:52_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
22:49.775
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.187
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.169
And Tor is ready 24.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.205
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:330 5.268 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:27:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/03:27:48_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/03:27:48_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/03:27:48_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/40/artifact/build-artifacts/03:27:48_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000