Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 1 04 Aug 2026, 17:31

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:8.332 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:16.226
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
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" 12.899
When I start Tails from USB drive "old" with network unplugged 59.536
Then the boot device has safe access rights 2.077
And Tails is running from USB drive "old" 0.179
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.159
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:339 3.835
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.424
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 47.750
Then Tails is running from USB drive "old" 0.187
And I create a persistent partition 22.042
And I take note of which tps features are available 6.174
Then a Tails persistence partition exists on USB drive "old" 0.574
And I shutdown Tails and wait for the computer to power off 2.620
After features/support/hooks.rb:339 0.439
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.836
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.579
Then Tails is running from USB drive "old" 0.276
And all tps features are active 6.903
When I write some files expected to persist 0.867
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.095
And all persistence configuration files have safe access rights 0.247
And all persistent directories from the old Tails version have safe access rights 1.491
And I take note of which tps features are available 5.874
And I shutdown Tails and wait for the computer to power off 2.497
# 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.908
After features/support/hooks.rb:339 0.435
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.659
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 7.956
And I log in to a new session 11.406
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.648
And I plug USB drive "to_upgrade" 2.185
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.611
Then the running Tails is installed on USB drive "to_upgrade" 17.622
And I unplug USB drive "to_upgrade" 0.106
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 6.702
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.870
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.427
Then all tps features from the old Tails version are active 0.960
And Tails is running from USB drive "to_upgrade" 0.148
And the boot device has safe access rights 1.854
And the expected persistent files created with the old Tails version are present in the filesystem 0.847
And all persistent directories from the old Tails version have safe access rights 1.552
After features/support/hooks.rb:339 0.752
After features/support/hooks.rb:108 0.005
3:30.476
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 8.080
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.025
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.239
When the network is plugged 0.025
And Tor is ready 11.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.923
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.842
Given I shutdown Tails and wait for the computer to power off 5.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.990
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.457
And the file system changes introduced in version 6.2~testoverlayfs are present 0.153
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.169
When the network is plugged 0.023
And Tor is ready 9.991
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.347
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.028
Given I shutdown Tails and wait for the computer to power off 2.692
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.200
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 9.301
And the file system changes introduced in version 6.3~testoverlayfs are present 0.275
And only the 6.3~testoverlayfs SquashFS delta is installed 0.033
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.021
And Tor is ready 10.218
Then the Upgrader considers the system as up-to-date 0.128
# 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.017
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.334
After features/support/hooks.rb:339 0.837
After features/support/hooks.rb:108 0.009
17.839
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.776
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 8.867
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.865
After features/support/hooks.rb:339 0.859
After features/support/hooks.rb:108 0.000