Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 14 12 Aug 2026, 23:01

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:21.701 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.239
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.168
When I start Tails from USB drive "old" with network unplugged 54.247
Then the boot device has safe access rights 2.104
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 1.525
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.524
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 47.541
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 21.578
And I take note of which tps features are available 6.043
Then a Tails persistence partition exists on USB drive "old" 0.496
And I shutdown Tails and wait for the computer to power off 2.568
After features/support/hooks.rb:339 0.313
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.831
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.692
Then Tails is running from USB drive "old" 0.156
And all tps features are active 6.410
When I write some files expected to persist 1.063
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.238
And all persistent directories from the old Tails version have safe access rights 1.685
And I take note of which tps features are available 5.773
And I shutdown Tails and wait for the computer to power off 2.554
# 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.027
After features/support/hooks.rb:339 0.439
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.607
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.378
And I log in to a new session 10.783
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.662
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.601
Then the running Tails is installed on USB drive "to_upgrade" 17.707
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.638
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.154
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.360
Then all tps features from the old Tails version are active 1.032
And Tails is running from USB drive "to_upgrade" 0.189
And the boot device has safe access rights 1.964
And the expected persistent files created with the old Tails version are present in the filesystem 0.881
And all persistent directories from the old Tails version have safe access rights 1.652
After features/support/hooks.rb:339 0.497
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:47.052
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.192
And no SquashFS delta is installed 0.075
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.030
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.347
When the network is plugged 0.040
And Tor is ready 19.094
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.386
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.028
Given I shutdown Tails and wait for the computer to power off 5.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.561
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.677
And the file system changes introduced in version 6.2~testoverlayfs are present 0.171
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.106
# 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.142
When the network is plugged 0.034
And Tor is ready 10.234
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.479
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.618
Given I shutdown Tails and wait for the computer to power off 2.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.133
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.688
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.048
# 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.091
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.148
When the network is plugged 0.033
And Tor is ready 10.117
Then the Upgrader considers the system as up-to-date 10.471
# 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.142
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.324
After features/support/hooks.rb:339 0.789
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.293
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.795
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.635
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.469
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.000