Project Number Date
test_Tails_ISO_drop-cloudfront-workaround 1 30 Sep 2026, 15:10

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:45.436 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:7.782
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.512
When I start Tails from USB drive "old" with network unplugged 49.910
Then the boot device has safe access rights 2.574
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.938
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.766
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 51.050
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 24.159
And I take note of which tps features are available 7.339
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 5.304
After features/support/hooks.rb:339 0.642
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.746
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.001
Then Tails is running from USB drive "old" 0.443
And all tps features are active 8.537
When I write some files expected to persist 1.294
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.035
And I take note of which tps features are available 6.569
And I shutdown Tails and wait for the computer to power off 3.974
# 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.239
After features/support/hooks.rb:339 0.536
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.830
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 9.174
And I log in to a new session 12.205
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.762
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.271
Then the running Tails is installed on USB drive "to_upgrade" 20.919
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:339 1.945
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.779
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.108
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.359
Then all tps features from the old Tails version are active 1.208
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 2.589
And the expected persistent files created with the old Tails version are present in the filesystem 1.052
And all persistent directories from the old Tails version have safe access rights 2.141
After features/support/hooks.rb:339 0.876
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
3:36.629
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.479
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.029
And Tor is ready 12.519
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.671
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.658
Given I shutdown Tails and wait for the computer to power off 5.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.303
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.496
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# 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.211
When the network is plugged 0.022
And Tor is ready 11.117
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.396
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.962
Given I shutdown Tails and wait for the computer to power off 4.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.563
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.044
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.032
And Tor is ready 12.420
Then the Upgrader considers the system as up-to-date 0.111
# 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.598
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:339 0.685
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
19.902
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 10.413
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.916
After features/support/hooks.rb:339 0.995
After features/support/hooks.rb:108 0.000