Project Number Date
test_Tails_ISO_21762-fix-htpdate-pool 1 02 Sep 2026, 22:25

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:7.516 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:18.741
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.114
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.325
When I start Tails from USB drive "old" with network unplugged 1:0.095
Then the boot device has safe access rights 2.499
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 4.036
After features/support/hooks.rb:108 0.009
Tags: @product
1:30.145
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login 52.326
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 25.307
And I take note of which tps features are available 7.351
Then a Tails persistence partition exists on USB drive "old" 0.610
And I shutdown Tails and wait for the computer to power off 4.221
After features/support/hooks.rb:339 0.230
After features/support/hooks.rb:108 0.005
Tags: @product
1:40.712
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.314
Then Tails is running from USB drive "old" 0.262
And all tps features are active 8.819
When I write some files expected to persist 1.241
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 1.997
And I take note of which tps features are available 6.369
And I shutdown Tails and wait for the computer to power off 4.099
# 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.996
After features/support/hooks.rb:339 0.094
After features/support/hooks.rb:108 0.008
Tags: @product
2:16.438
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.043
And I log in to a new session 14.288
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.822
And I plug USB drive "to_upgrade" 2.190
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.878
Then the running Tails is installed on USB drive "to_upgrade" 18.961
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.910
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.192
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.487
Then all tps features from the old Tails version are active 1.074
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.200
And the expected persistent files created with the old Tails version are present in the filesystem 0.970
And all persistent directories from the old Tails version have safe access rights 2.149
After features/support/hooks.rb:339 0.492
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
3:50.684
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.522
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.025
And Tor is ready 11.968
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.804
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.965
Given I shutdown Tails and wait for the computer to power off 5.455
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.388
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 8.338
And the file system changes introduced in version 6.2~testoverlayfs are present 0.172
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.173
When the network is plugged 0.028
And Tor is ready 10.882
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.949
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.042
Given I shutdown Tails and wait for the computer to power off 3.943
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.824
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.969
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.028
And Tor is ready 10.735
Then the Upgrader considers the system as up-to-date 10.444
# 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.873
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:339 0.690
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.602
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.231
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 9.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.004
After features/support/hooks.rb:339 0.549
After features/support/hooks.rb:108 0.000