Project Number Date
test_Tails_ISO_drop-cloudfront-workaround 2 30 Sep 2026, 18:06

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 11:52.254 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:12.254
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.161
When I start Tails from USB drive "old" with network unplugged 53.810
Then the boot device has safe access rights 2.545
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.141
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.807
After features/support/hooks.rb:108 0.051
Tags: @product
1:29.970
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 52.629
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 24.555
And I take note of which tps features are available 9.266
Then a Tails persistence partition exists on USB drive "old" 0.578
And I shutdown Tails and wait for the computer to power off 2.620
After features/support/hooks.rb:339 0.334
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.217
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.760
Then Tails is running from USB drive "old" 0.266
And all tps features are active 7.751
When I write some files expected to persist 1.357
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.283
And all persistent directories from the old Tails version have safe access rights 2.001
And I take note of which tps features are available 6.720
And I shutdown Tails and wait for the computer to power off 2.628
# 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" 12.210
After features/support/hooks.rb:339 0.127
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.429
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.493
And I log in to a new session 12.777
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.601
And I plug USB drive "to_upgrade" 2.280
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.425
Then the running Tails is installed on USB drive "to_upgrade" 18.569
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:339 1.855
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.448
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.597
Then all tps features from the old Tails version are active 1.261
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.410
And the expected persistent files created with the old Tails version are present in the filesystem 0.930
And all persistent directories from the old Tails version have safe access rights 1.899
After features/support/hooks.rb:339 0.726
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:47.372
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.149
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.034
And Tor is ready 14.290
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.426
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.043
Given I shutdown Tails and wait for the computer to power off 5.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.791
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.707
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.194
When the network is plugged 0.038
And Tor is ready 10.957
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.233
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.150
Given I shutdown Tails and wait for the computer to power off 2.762
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.966
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 10.941
And the file system changes introduced in version 6.3~testoverlayfs are present 0.332
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.025
And Tor is ready 10.964
Then the Upgrader considers the system as up-to-date 0.118
# 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 3.757
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.426
After features/support/hooks.rb:339 1.092
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
19.561
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.483
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.108
After features/support/hooks.rb:339 0.713
After features/support/hooks.rb:108 0.000