Project Number Date
test_Tails_ISO_21720-less-error-prone-emergency-release 6 23 Aug 2026, 13:35

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:40.680 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:6.019
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.134
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.792
When I start Tails from USB drive "old" with network unplugged 47.507
Then the boot device has safe access rights 2.764
And Tails is running from USB drive "old" 0.278
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:339 1.325
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.887
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 51.655
Then Tails is running from USB drive "old" 0.196
And I create a persistent partition 25.242
And I take note of which tps features are available 7.062
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 4.110
After features/support/hooks.rb:339 0.423
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.251
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.178
Then Tails is running from USB drive "old" 0.195
And all tps features are active 8.445
When I write some files expected to persist 1.285
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.965
And I take note of which tps features are available 6.508
And I shutdown Tails and wait for the computer to power off 4.250
# 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.875
After features/support/hooks.rb:339 0.092
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.770
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.634
And I log in to a new session 11.670
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.694
And I plug USB drive "to_upgrade" 2.349
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.631
Then the running Tails is installed on USB drive "to_upgrade" 19.533
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 3.953
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.739
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.019
Then all tps features from the old Tails version are active 1.357
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 2.846
And the expected persistent files created with the old Tails version are present in the filesystem 1.119
And all persistent directories from the old Tails version have safe access rights 1.992
After features/support/hooks.rb:339 0.960
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:38.840
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 8.647
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.297
When the network is plugged 0.027
And Tor is ready 12.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.529
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.954
Given I shutdown Tails and wait for the computer to power off 5.481
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.356
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 7.704
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.209
When the network is plugged 0.038
And Tor is ready 10.380
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.573
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.644
Given I shutdown Tails and wait for the computer to power off 4.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.611
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.764
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.167
When the network is plugged 0.025
And Tor is ready 11.222
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.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:339 1.069
After features/support/hooks.rb:108 0.037
Tags: @product @automatic_upgrade
19.169
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.991
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 8.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.200
After features/support/hooks.rb:339 0.547
After features/support/hooks.rb:108 0.000