Project Number Date
test_Tails_ISO_devel 4629 19 Sep 2026, 11:10

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 81 1 5 0 0 87 6 1 7 11:18.101 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
1:15.251
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 12.841
When I start Tails from USB drive "old" with network unplugged 58.906
Then the boot device has safe access rights 1.713
And Tails is running from USB drive "old" 0.180
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.807
After features/support/hooks.rb:108 0.021
Tags: @product
1:20.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 47.151
Then Tails is running from USB drive "old" 0.178
And I create a persistent partition 22.074
And I take note of which tps features are available 5.851
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 4.204
After features/support/hooks.rb:339 0.199
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.655
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.449
Then Tails is running from USB drive "old" 0.221
And all tps features are active 6.614
When I write some files expected to persist 0.998
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.196
And all persistent directories from the old Tails version have safe access rights 1.329
And I take note of which tps features are available 5.506
And I shutdown Tails and wait for the computer to power off 5.061
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.032
After features/support/hooks.rb:339 0.153
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.662
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.326
And I log in to a new session 12.219
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.603
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.507
Then the running Tails is installed on USB drive "to_upgrade" 17.480
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.850
After features/support/hooks.rb:108 0.000
Tags: @product
1:23.436
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:23.358
can 
can not find any of the patterns ["TailsGreeter.png", "PlymouthGraphicsCardFailureMessage.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:446:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:238: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:339 4.985 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:12:22)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:12:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:12:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:12:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:12:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:19.845
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.049
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.324
When the network is plugged 0.029
And Tor is ready 11.690
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.997
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.874
Given I shutdown Tails and wait for the computer to power off 5.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.405
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.263
And the file system changes introduced in version 6.2~testoverlayfs are present 0.169
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.088
# 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.163
When the network is plugged 0.032
And Tor is ready 10.119
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.860
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.397
Given I shutdown Tails and wait for the computer to power off 2.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.436
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.430
And the file system changes introduced in version 6.3~testoverlayfs are present 0.349
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.084
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.023
And Tor is ready 10.117
Then the Upgrader considers the system as up-to-date 0.077
# 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 2.967
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.307
After features/support/hooks.rb:339 0.980
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.134
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.741
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.022
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.759
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.350
After features/support/hooks.rb:339 0.532
After features/support/hooks.rb:108 0.000