Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 6 02 May 2026, 14:36

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:25.504 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:3.880
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.360
When I start Tails from USB drive "old" with network unplugged 46.156
Then the boot device has safe access rights 2.678
And Tails is running from USB drive "old" 0.189
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 1.331
After features/support/hooks.rb:100 0.010
Tags: @product
1:25.183
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 52.839
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 23.716
And I take note of which tps features are available 0.739
Then a Tails persistence partition exists on USB drive "old" 0.565
And I shutdown Tails and wait for the computer to power off 7.025
After features/support/hooks.rb:331 0.220
After features/support/hooks.rb:100 0.013
Tags: @product
1:23.626
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.093
Then Tails is running from USB drive "old" 0.290
And all tps features are active 1.187
When I write some files expected to persist 1.334
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.528
And all persistent directories from the old Tails version have safe access rights 2.162
And I take note of which tps features are available 0.182
And I shutdown Tails and wait for the computer to power off 4.259
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.358
After features/support/hooks.rb:331 0.206
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.427
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.736
And I log in to a new session 12.430
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.861
And I plug USB drive "to_upgrade" 2.301
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.632
Then the running Tails is installed on USB drive "to_upgrade" 16.164
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:331 0.857
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.398
Then all tps features from the old Tails version are active 1.053
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 2.746
And the expected persistent files created with the old Tails version are present in the filesystem 1.173
And all persistent directories from the old Tails version have safe access rights 1.924
After features/support/hooks.rb:331 0.630
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
4:41.546
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.022
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
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.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.038
And Tor is ready 22.285
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.397
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.284
Given I shutdown Tails and wait for the computer to power off 19.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.695
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.292
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.278
When the network is plugged 0.016
And Tor is ready 21.089
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.413
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.625
Given I shutdown Tails and wait for the computer to power off 17.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.942
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.090
And the file system changes introduced in version 6.3~testoverlayfs are present 0.421
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.017
And Tor is ready 21.112
Then the Upgrader considers the system as up-to-date 0.172
# 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.292
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.398
After features/support/hooks.rb:331 1.037
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
28.163
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.433
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.471
After features/support/hooks.rb:331 0.618
After features/support/hooks.rb:100 0.000