Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 21 24 Aug 2026, 23:09

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.683 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:6.287
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.392
When I start Tails from USB drive "old" with network unplugged 48.860
Then the boot device has safe access rights 2.362
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.147
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.763
After features/support/hooks.rb:108 0.012
Tags: @product
1:18.423
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 46.676
Then Tails is running from USB drive "old" 0.174
And I create a persistent partition 22.617
And I take note of which tps features are available 5.800
Then a Tails persistence partition exists on USB drive "old" 0.472
And I shutdown Tails and wait for the computer to power off 2.575
After features/support/hooks.rb:339 0.436
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.486
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 with persistence enabled 58.503
Then Tails is running from USB drive "old" 0.193
And all tps features are active 6.867
When I write some files expected to persist 1.014
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.120
And all persistence configuration files have safe access rights 0.193
And all persistent directories from the old Tails version have safe access rights 1.385
And I take note of which tps features are available 5.682
And I shutdown Tails and wait for the computer to power off 2.580
# 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.868
After features/support/hooks.rb:339 0.318
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.978
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.081
And I log in to a new session 11.196
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.565
And I plug USB drive "to_upgrade" 2.193
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.676
Then the running Tails is installed on USB drive "to_upgrade" 17.019
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.832
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.081
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.460
Then all tps features from the old Tails version are active 0.986
And Tails is running from USB drive "to_upgrade" 0.201
And the boot device has safe access rights 2.050
And the expected persistent files created with the old Tails version are present in the filesystem 0.841
And all persistent directories from the old Tails version have safe access rights 1.441
After features/support/hooks.rb:339 0.547
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:41.163
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.773
And no SquashFS delta is installed 0.042
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.299
When the network is plugged 0.027
And Tor is ready 11.318
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.885
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.133
Given I shutdown Tails and wait for the computer to power off 5.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.111
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 9.511
And the file system changes introduced in version 6.2~testoverlayfs are present 0.155
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.036
And Tor is ready 10.105
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.435
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.794
Given I shutdown Tails and wait for the computer to power off 2.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.353
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.929
And the file system changes introduced in version 6.3~testoverlayfs are present 0.272
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.181
When the network is plugged 0.031
And Tor is ready 9.983
Then the Upgrader considers the system as up-to-date 10.451
# 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.067
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.660
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.262
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.610
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
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.037
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 8.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.857
After features/support/hooks.rb:339 0.844
After features/support/hooks.rb:108 0.000