Project Number Date
test_Tails_ISO_late-patch-improvements 1 12 Nov 2026, 20:21

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:7.302 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:4.646
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.709
When I start Tails from USB drive "old" with network unplugged 47.052
Then the boot device has safe access rights 2.170
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.419
After features/support/hooks.rb:108 0.013
Tags: @product
1:22.368
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 48.066
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 23.200
And I take note of which tps features are available 6.156
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 4.153
After features/support/hooks.rb:339 0.467
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.333
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.134
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.087
Then Tails is running from USB drive "old" 0.181
And all tps features are active 7.023
When I write some files expected to persist 0.934
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.203
And all persistent directories from the old Tails version have safe access rights 1.416
And I take note of which tps features are available 5.908
And I shutdown Tails and wait for the computer to power off 4.161
# 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.133
After features/support/hooks.rb:339 0.475
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.567
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 without a persistent partition and stopped at Tails Greeter's login screen 8.467
And I log in to a new session 12.558
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.762
And I plug USB drive "to_upgrade" 2.181
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.142
Then the running Tails is installed on USB drive "to_upgrade" 18.188
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 1.783
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.452
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.659
Then all tps features from the old Tails version are active 1.178
And Tails is running from USB drive "to_upgrade" 0.194
And the boot device has safe access rights 2.026
And the expected persistent files created with the old Tails version are present in the filesystem 0.831
And all persistent directories from the old Tails version have safe access rights 1.491
After features/support/hooks.rb:339 0.780
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:28.779
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.445
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.290
When the network is plugged 0.023
And Tor is ready 12.709
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.996
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.441
Given I shutdown Tails and wait for the computer to power off 5.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.797
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.836
And the file system changes introduced in version 6.2~testoverlayfs are present 0.177
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.200
When the network is plugged 0.040
And Tor is ready 10.165
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.908
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.563
Given I shutdown Tails and wait for the computer to power off 2.801
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.557
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.751
And the file system changes introduced in version 6.3~testoverlayfs are present 0.289
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.080
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.173
When the network is plugged 0.038
And Tor is ready 10.438
Then the Upgrader considers the system as up-to-date 0.090
# 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.438
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:339 0.690
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.152
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 7.737
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.195
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.924
After features/support/hooks.rb:339 0.542
After features/support/hooks.rb:108 0.000