Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 11 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.100 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:26.675
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.618
When I start Tails from USB drive "old" with network unplugged 1:6.405
Then the boot device has safe access rights 3.672
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.129
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:335 1.811
After features/support/hooks.rb:104 0.009
Tags: @product
1:34.353
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 58.645
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 26.066
And I take note of which tps features are available 0.418
Then a Tails persistence partition exists on USB drive "old" 0.620
And I shutdown Tails and wait for the computer to power off 8.145
After features/support/hooks.rb:335 0.531
After features/support/hooks.rb:104 0.008
Tags: @product
1:34.198
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.492
Then Tails is running from USB drive "old" 0.260
And all tps features are active 1.295
When I write some files expected to persist 1.446
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 2.056
And I take note of which tps features are available 0.178
And I shutdown Tails and wait for the computer to power off 8.392
# 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.441
After features/support/hooks.rb:335 0.181
After features/support/hooks.rb:104 0.006
Tags: @product
2:17.312
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.877
And I log in to a new session 15.488
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.309
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.260
Then the running Tails is installed on USB drive "to_upgrade" 16.805
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:335 2.520
After features/support/hooks.rb:104 0.000
Tags: @product
1:16.880
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.086
Then all tps features from the old Tails version are active 1.267
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 2.908
And the expected persistent files created with the old Tails version are present in the filesystem 1.369
And all persistent directories from the old Tails version have safe access rights 1.851
After features/support/hooks.rb:335 0.908
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:47.486
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.556
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.019
And Tor is ready 13.472
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.961
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.461
Given I shutdown Tails and wait for the computer to power off 7.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.985
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 1.546
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
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.161
# 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.260
When the network is plugged 0.020
And Tor is ready 10.121
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.346
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.058
Given I shutdown Tails and wait for the computer to power off 4.352
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.183
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.098
And the file system changes introduced in version 6.3~testoverlayfs are present 0.356
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.019
And Tor is ready 10.320
Then the Upgrader considers the system as up-to-date 10.611
# 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.785
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.727
After features/support/hooks.rb:335 1.146
After features/support/hooks.rb:104 0.017
Tags: @product @automatic_upgrade
22.194
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.184
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.932
After features/support/hooks.rb:335 1.074
After features/support/hooks.rb:104 0.000