Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 20 23 Aug 2026, 23:00

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:17.223 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:12.103
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 12.942
When I start Tails from USB drive "old" with network unplugged 55.662
Then the boot device has safe access rights 1.863
And Tails is running from USB drive "old" 0.182
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.118
And I unplug USB drive "old" 0.105
After features/support/hooks.rb:339 1.684
After features/support/hooks.rb:108 0.004
Tags: @product
1:19.043
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 46.785
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 23.007
And I take note of which tps features are available 5.862
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 2.567
After features/support/hooks.rb:339 0.274
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.384
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.170
Then Tails is running from USB drive "old" 0.220
And all tps features are active 6.737
When I write some files expected to persist 0.993
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.485
And I take note of which tps features are available 5.939
And I shutdown Tails and wait for the computer to power off 2.511
# 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.830
After features/support/hooks.rb:339 0.421
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.368
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.351
And I log in to a new session 12.107
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.675
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.552
Then the running Tails is installed on USB drive "to_upgrade" 17.220
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 2.034
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.444
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.931
Then all tps features from the old Tails version are active 0.952
And Tails is running from USB drive "to_upgrade" 0.185
And the boot device has safe access rights 1.989
And the expected persistent files created with the old Tails version are present in the filesystem 0.883
And all persistent directories from the old Tails version have safe access rights 1.430
After features/support/hooks.rb:339 0.666
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:43.370
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.187
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
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.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.265
When the network is plugged 0.034
And Tor is ready 12.621
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.140
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.782
Given I shutdown Tails and wait for the computer to power off 5.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.947
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.956
And the file system changes introduced in version 6.2~testoverlayfs are present 0.163
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.117
# 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.131
When the network is plugged 0.025
And Tor is ready 10.241
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.833
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.703
Given I shutdown Tails and wait for the computer to power off 4.151
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.302
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.403
And the file system changes introduced in version 6.3~testoverlayfs are present 0.229
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.075
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.153
When the network is plugged 0.033
And Tor is ready 10.066
Then the Upgrader considers the system as up-to-date 10.406
# 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.095
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.383
After features/support/hooks.rb:339 0.929
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.507
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.667
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 10.253
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.284
After features/support/hooks.rb:339 0.648
After features/support/hooks.rb:108 0.000