Project Number Date
test_Tails_ISO_21651-persist-gnome-software-dconf-state 7 26 Jul 2026, 03: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:30.594 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:15.865
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.813
When I start Tails from USB drive "old" with network unplugged 57.569
Then the boot device has safe access rights 2.747
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.565
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.778
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 57.333
Then Tails is running from USB drive "old" 0.222
And I create a persistent partition 26.613
And I take note of which tps features are available 4.698
Then a Tails persistence partition exists on USB drive "old" 0.590
And I shutdown Tails and wait for the computer to power off 4.267
After features/support/hooks.rb:339 0.606
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.873
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.488
Then Tails is running from USB drive "old" 0.238
And all tps features are active 6.139
When I write some files expected to persist 1.351
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.334
And all persistent directories from the old Tails version have safe access rights 2.335
And I take note of which tps features are available 4.266
And I shutdown Tails and wait for the computer to power off 4.141
# 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.332
After features/support/hooks.rb:339 0.507
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.955
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.766
And I log in to a new session 13.759
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.267
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.312
Then the running Tails is installed on USB drive "to_upgrade" 17.731
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.164
After features/support/hooks.rb:339 2.579
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.983
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.993
Then all tps features from the old Tails version are active 1.100
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.003
And the expected persistent files created with the old Tails version are present in the filesystem 1.182
And all persistent directories from the old Tails version have safe access rights 2.333
After features/support/hooks.rb:339 0.858
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
4:5.439
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.631
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.707
When the network is plugged 0.014
And Tor is ready 13.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.553
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.194
Given I shutdown Tails and wait for the computer to power off 7.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.860
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.223
And the file system changes introduced in version 6.2~testoverlayfs are present 0.249
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.168
# 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.294
When the network is plugged 0.035
And Tor is ready 10.260
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.130
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.003
Given I shutdown Tails and wait for the computer to power off 4.121
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.785
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.914
And the file system changes introduced in version 6.3~testoverlayfs are present 0.431
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.014
And Tor is ready 10.143
Then the Upgrader considers the system as up-to-date 10.737
# 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.246
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:339 1.031
After features/support/hooks.rb:108 0.086
Tags: @product @automatic_upgrade
19.697
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.503
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.800
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.028
After features/support/hooks.rb:339 1.088
After features/support/hooks.rb:108 0.000