Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 10 02 Jun 2026, 20:53

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:19.496 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:27.984
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.678
When I start Tails from USB drive "old" with network unplugged 1:8.113
Then the boot device has safe access rights 3.212
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 1.705
After features/support/hooks.rb:104 0.010
Tags: @product
1:33.657
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 1:0.394
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 25.007
And I take note of which tps features are available 0.409
Then a Tails persistence partition exists on USB drive "old" 0.541
And I shutdown Tails and wait for the computer to power off 6.902
After features/support/hooks.rb:335 0.214
After features/support/hooks.rb:104 0.008
Tags: @product
1:30.722
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.861
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.249
When I write some files expected to persist 1.433
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 1.875
And I take note of which tps features are available 0.177
And I shutdown Tails and wait for the computer to power off 4.142
# 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" 13.067
After features/support/hooks.rb:335 0.134
After features/support/hooks.rb:104 0.009
Tags: @product
2:17.286
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.971
And I log in to a new session 15.093
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.755
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.667
Then the running Tails is installed on USB drive "to_upgrade" 17.106
And I unplug USB drive "to_upgrade" 0.167
And I unplug USB drive "__internal" 0.278
After features/support/hooks.rb:335 2.851
After features/support/hooks.rb:104 0.000
Tags: @product
1:17.205
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.543
Then all tps features from the old Tails version are active 1.195
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 3.434
And the expected persistent files created with the old Tails version are present in the filesystem 1.303
And all persistent directories from the old Tails version have safe access rights 2.364
After features/support/hooks.rb:335 0.616
After features/support/hooks.rb:104 0.037
Tags: @product @automatic_upgrade
3:51.099
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.539
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.017
And Tor is ready 13.954
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.391
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.848
Given I shutdown Tails and wait for the computer to power off 7.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.098
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.320
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.212
When the network is plugged 0.017
And Tor is ready 12.102
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.390
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.656
Given I shutdown Tails and wait for the computer to power off 4.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.940
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.196
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.016
And Tor is ready 10.994
Then the Upgrader considers the system as up-to-date 10.610
# 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.348
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:335 0.887
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
21.539
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.528
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.585
After features/support/hooks.rb:335 0.703
After features/support/hooks.rb:104 0.000