Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 31 18 Jun 2026, 20:12

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:46.066 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:9.639
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.335
When I start Tails from USB drive "old" with network unplugged 51.635
Then the boot device has safe access rights 2.722
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:339 1.526
After features/support/hooks.rb:108 0.019
Tags: @product
1:28.945
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.131
And I start Tails from USB drive "old" with network unplugged and I login 52.365
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 24.832
And I take note of which tps features are available 3.970
Then a Tails persistence partition exists on USB drive "old" 0.563
And I shutdown Tails and wait for the computer to power off 6.849
After features/support/hooks.rb:339 0.454
After features/support/hooks.rb:108 0.015
Tags: @product
1:37.197
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.976
Then Tails is running from USB drive "old" 0.266
And all tps features are active 4.953
When I write some files expected to persist 1.390
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 1.838
And I take note of which tps features are available 3.724
And I shutdown Tails and wait for the computer to power off 8.330
# 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.119
After features/support/hooks.rb:339 0.183
After features/support/hooks.rb:108 0.017
Tags: @product
2:9.436
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.072
And I log in to a new session 12.533
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.679
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.196
Then the running Tails is installed on USB drive "to_upgrade" 14.445
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:339 2.639
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.843
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.374
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.340
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 1.733
After features/support/hooks.rb:339 0.839
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:49.207
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.257
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.016
And Tor is ready 13.150
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.105
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.287
Given I shutdown Tails and wait for the computer to power off 7.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.688
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.220
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.259
When the network is plugged 0.021
And Tor is ready 11.050
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.803
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.296
Given I shutdown Tails and wait for the computer to power off 4.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.193
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.858
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.016
And Tor is ready 9.771
Then the Upgrader considers the system as up-to-date 10.524
# 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 4.304
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.312
After features/support/hooks.rb:339 0.857
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
19.797
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.527
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.735
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.144
After features/support/hooks.rb:339 0.945
After features/support/hooks.rb:108 0.000