Project Number Date
test_Tails_ISO_21651-persist-gnome-software-dconf-state 4 23 Jul 2026, 14:26

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:22.130 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:13.027
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.294
When I start Tails from USB drive "old" with network unplugged 54.243
Then the boot device has safe access rights 2.671
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:339 1.456
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.908
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 57.612
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 25.926
And I take note of which tps features are available 5.101
Then a Tails persistence partition exists on USB drive "old" 0.635
And I shutdown Tails and wait for the computer to power off 4.307
After features/support/hooks.rb:339 0.432
After features/support/hooks.rb:108 0.006
Tags: @product
1:42.047
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.276
Then Tails is running from USB drive "old" 0.386
And all tps features are active 6.210
When I write some files expected to persist 1.458
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.292
And all persistent directories from the old Tails version have safe access rights 2.091
And I take note of which tps features are available 4.379
And I shutdown Tails and wait for the computer to power off 4.148
# 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.521
After features/support/hooks.rb:339 0.326
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.141
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.791
And I log in to a new session 12.945
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.882
And I plug USB drive "to_upgrade" 2.257
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.198
Then the running Tails is installed on USB drive "to_upgrade" 16.590
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.262
After features/support/hooks.rb:339 2.342
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.957
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.102
Then all tps features from the old Tails version are active 1.392
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.860
And the expected persistent files created with the old Tails version are present in the filesystem 1.176
And all persistent directories from the old Tails version have safe access rights 2.094
After features/support/hooks.rb:339 0.761
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
4:0.392
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.642
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.018
And Tor is ready 13.770
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.641
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.465
Given I shutdown Tails and wait for the computer to power off 5.582
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.806
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.869
And the file system changes introduced in version 6.2~testoverlayfs are present 0.281
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.228
When the network is plugged 0.018
And Tor is ready 10.245
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.253
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.121
Given I shutdown Tails and wait for the computer to power off 4.222
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.605
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.580
And the file system changes introduced in version 6.3~testoverlayfs are present 0.389
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.018
And Tor is ready 10.121
Then the Upgrader considers the system as up-to-date 10.585
# 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.637
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.471
After features/support/hooks.rb:339 1.047
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
20.656
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.574
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.667
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.014
After features/support/hooks.rb:339 0.608
After features/support/hooks.rb:108 0.000