Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 24 27 Aug 2026, 23:07

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:52.349 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:14.920
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 13.192
When I start Tails from USB drive "old" with network unplugged 57.958
Then the boot device has safe access rights 2.117
And Tails is running from USB drive "old" 0.143
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.145
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 1.273
After features/support/hooks.rb:108 0.006
Tags: @product
1:20.743
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 "old" with network unplugged and I login 47.073
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 23.724
And I take note of which tps features are available 6.532
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 2.618
After features/support/hooks.rb:339 0.561
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.011
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.396
Then Tails is running from USB drive "old" 0.227
And all tps features are active 7.596
When I write some files expected to persist 1.259
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.687
And I take note of which tps features are available 6.176
And I shutdown Tails and wait for the computer to power off 2.523
# 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" 11.580
After features/support/hooks.rb:339 0.324
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.935
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.406
And I log in to a new session 11.387
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.742
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.009
Then the running Tails is installed on USB drive "to_upgrade" 16.957
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 1.998
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.144
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:1.446
Then all tps features from the old Tails version are active 1.015
And Tails is running from USB drive "to_upgrade" 0.169
And the boot device has safe access rights 1.993
And the expected persistent files created with the old Tails version are present in the filesystem 0.909
And all persistent directories from the old Tails version have safe access rights 1.532
After features/support/hooks.rb:339 0.479
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:41.313
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 21.080
And no SquashFS delta is installed 0.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.271
When the network is plugged 0.036
And Tor is ready 11.832
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.454
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.812
Given I shutdown Tails and wait for the computer to power off 5.241
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.111
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.899
And the file system changes introduced in version 6.2~testoverlayfs are present 0.184
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.084
# 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.173
When the network is plugged 0.031
And Tor is ready 10.206
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.929
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.098
Given I shutdown Tails and wait for the computer to power off 2.524
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.142
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 9.427
And the file system changes introduced in version 6.3~testoverlayfs are present 0.290
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.073
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.141
When the network is plugged 0.023
And Tor is ready 10.173
Then the Upgrader considers the system as up-to-date 0.070
# 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.148
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.252
After features/support/hooks.rb:339 0.970
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
45.280
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 33.646
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.359
After features/support/hooks.rb:339 0.938
After features/support/hooks.rb:108 0.000