Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 5 05 Aug 2026, 23:24

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:50.257 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:11.483
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.806
When I start Tails from USB drive "old" with network unplugged 53.316
Then the boot device has safe access rights 2.569
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 3.591
After features/support/hooks.rb:108 0.026
Tags: @product
1:26.790
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 49.184
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 24.722
And I take note of which tps features are available 7.562
Then a Tails persistence partition exists on USB drive "old" 0.685
And I shutdown Tails and wait for the computer to power off 4.322
After features/support/hooks.rb:339 0.583
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.043
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.600
Then Tails is running from USB drive "old" 0.283
And all tps features are active 7.398
When I write some files expected to persist 1.308
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 2.133
And I take note of which tps features are available 6.549
And I shutdown Tails and wait for the computer to power off 2.846
# 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.265
After features/support/hooks.rb:339 0.333
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.594
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.450
And I log in to a new session 12.957
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.721
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.193
Then the running Tails is installed on USB drive "to_upgrade" 18.796
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 0.668
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.999
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.148
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.965
Then all tps features from the old Tails version are active 1.148
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.347
And the expected persistent files created with the old Tails version are present in the filesystem 1.226
And all persistent directories from the old Tails version have safe access rights 1.945
After features/support/hooks.rb:339 0.708
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
3:42.582
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 with a persistent partition enabled and logged in 8.635
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.268
When the network is plugged 0.027
And Tor is ready 13.519
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.324
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.619
Given I shutdown Tails and wait for the computer to power off 5.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.488
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 10.939
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.188
When the network is plugged 0.025
And Tor is ready 10.496
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.611
Given I shutdown Tails and wait for the computer to power off 2.564
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.452
Then Tails is running version 6.3~testoverlayfs 0.046
And all tps features are active 11.010
And the file system changes introduced in version 6.3~testoverlayfs are present 0.337
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.083
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.144
When the network is plugged 0.034
And Tor is ready 10.736
Then the Upgrader considers the system as up-to-date 0.119
# 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.835
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:339 0.881
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.765
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.903
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.838
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.618
After features/support/hooks.rb:339 0.927
After features/support/hooks.rb:108 0.000