Project Number Date
test_Tails_ISO_21546-release-process-fix-isos-git 2 07 May 2026, 23:36

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 12:32.735 Passed
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:5.224
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.729
When I start Tails from USB drive "old" with network unplugged 47.030
Then the boot device has safe access rights 2.712
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.936
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.695
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 54.674
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 25.224
And I take note of which tps features are available 0.830
Then a Tails persistence partition exists on USB drive "old" 0.571
And I shutdown Tails and wait for the computer to power off 8.064
After features/support/hooks.rb:331 0.250
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.635
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.575
Then Tails is running from USB drive "old" 0.237
And all tps features are active 1.251
When I write some files expected to persist 1.390
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.505
And all persistent directories from the old Tails version have safe access rights 2.404
And I take note of which tps features are available 0.178
And I shutdown Tails and wait for the computer to power off 8.416
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.426
After features/support/hooks.rb:331 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.655
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.579
And I log in to a new session 12.338
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.057
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.148
Then the running Tails is installed on USB drive "to_upgrade" 16.006
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:331 2.035
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.356
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.353
Then all tps features from the old Tails version are active 0.978
And Tails is running from USB drive "to_upgrade" 0.436
And the boot device has safe access rights 3.091
And the expected persistent files created with the old Tails version are present in the filesystem 1.176
And all persistent directories from the old Tails version have safe access rights 2.250
After features/support/hooks.rb:331 0.927
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:42.116
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.357
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.020
And Tor is ready 22.172
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.650
Given I shutdown Tails and wait for the computer to power off 19.145
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.087
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 1.315
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.185
# 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.245
When the network is plugged 0.018
And Tor is ready 20.419
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.482
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.421
Given I shutdown Tails and wait for the computer to power off 17.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.534
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.368
And the file system changes introduced in version 6.3~testoverlayfs are present 0.378
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.014
And Tor is ready 20.634
Then the Upgrader considers the system as up-to-date 0.119
# 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 4.673
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.436
After features/support/hooks.rb:331 0.802
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
25.051
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.656
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 16.686
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.366
After features/support/hooks.rb:331 0.814
After features/support/hooks.rb:100 0.000