Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 57 10 Jun 2026, 14:27

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:41.822 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:22.220
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.675
When I start Tails from USB drive "old" with network unplugged 1:3.940
Then the boot device has safe access rights 2.767
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:335 1.607
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.277
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 54.444
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 24.161
And I take note of which tps features are available 0.409
Then a Tails persistence partition exists on USB drive "old" 0.549
And I shutdown Tails and wait for the computer to power off 8.394
After features/support/hooks.rb:335 0.591
After features/support/hooks.rb:104 0.009
Tags: @product
1:29.931
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.162
Then Tails is running from USB drive "old" 0.300
And all tps features are active 1.325
When I write some files expected to persist 1.402
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.099
And I take note of which tps features are available 0.209
And I shutdown Tails and wait for the computer to power off 8.255
# 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.576
After features/support/hooks.rb:335 0.431
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.616
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 7.909
And I log in to a new session 14.293
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.707
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.416
Then the running Tails is installed on USB drive "to_upgrade" 14.779
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:335 2.456
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.343
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.226
Then all tps features from the old Tails version are active 1.007
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.752
And the expected persistent files created with the old Tails version are present in the filesystem 1.164
And all persistent directories from the old Tails version have safe access rights 1.920
After features/support/hooks.rb:335 0.905
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:41.546
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 7.788
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.032
And Tor is ready 13.263
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.597
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.320
Given I shutdown Tails and wait for the computer to power off 9.540
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.222
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.264
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.250
When the network is plugged 0.017
And Tor is ready 11.591
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.337
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.053
Given I shutdown Tails and wait for the computer to power off 4.453
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.335
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.222
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.018
And Tor is ready 10.687
Then the Upgrader considers the system as up-to-date 10.551
# 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.117
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.377
After features/support/hooks.rb:335 0.840
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
19.885
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 7.733
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.355
After features/support/hooks.rb:335 0.937
After features/support/hooks.rb:104 0.000