Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 6 06 Aug 2026, 22:57

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:28.969 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:10.172
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.095
When I start Tails from USB drive "old" with network unplugged 53.569
Then the boot device has safe access rights 1.844
And Tails is running from USB drive "old" 0.166
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.163
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.418
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.284
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 46.933
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 22.602
And I take note of which tps features are available 5.963
Then a Tails persistence partition exists on USB drive "old" 0.476
And I shutdown Tails and wait for the computer to power off 4.003
After features/support/hooks.rb:339 0.548
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.505
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.469
Then Tails is running from USB drive "old" 0.246
And all tps features are active 6.602
When I write some files expected to persist 0.987
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.219
And all persistent directories from the old Tails version have safe access rights 1.548
And I take note of which tps features are available 5.935
And I shutdown Tails and wait for the computer to power off 2.519
# 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" 10.758
After features/support/hooks.rb:339 0.296
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.738
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.086
And I log in to a new session 11.046
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.596
And I plug USB drive "to_upgrade" 2.183
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.179
Then the running Tails is installed on USB drive "to_upgrade" 17.388
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.626
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.757
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.401
Then all tps features from the old Tails version are active 0.960
And Tails is running from USB drive "to_upgrade" 0.187
And the boot device has safe access rights 1.750
And the expected persistent files created with the old Tails version are present in the filesystem 0.903
And all persistent directories from the old Tails version have safe access rights 1.483
After features/support/hooks.rb:339 0.872
After features/support/hooks.rb:108 0.005
3:55.037
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.795
And no SquashFS delta is installed 0.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.162
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.034
And Tor is ready 13.606
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.292
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.997
Given I shutdown Tails and wait for the computer to power off 5.184
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.219
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.185
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.029
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.186
When the network is plugged 0.033
And Tor is ready 10.182
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.475
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.936
Given I shutdown Tails and wait for the computer to power off 2.522
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.117
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.912
And the file system changes introduced in version 6.3~testoverlayfs are present 0.292
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.028
And Tor is ready 9.873
Then the Upgrader considers the system as up-to-date 10.413
# 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 3.002
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.322
After features/support/hooks.rb:339 0.813
After features/support/hooks.rb:108 0.009
18.473
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.519
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 8.141
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.449
After features/support/hooks.rb:339 0.645
After features/support/hooks.rb:108 0.000