Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 13 11 Aug 2026, 23:03

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:33.139 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.968
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.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.480
When I start Tails from USB drive "old" with network unplugged 57.511
Then the boot device has safe access rights 2.303
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.030
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.645
After features/support/hooks.rb:108 0.010
Tags: @product
1:22.669
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 48.804
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 22.858
And I take note of which tps features are available 6.137
Then a Tails persistence partition exists on USB drive "old" 0.534
And I shutdown Tails and wait for the computer to power off 4.012
After features/support/hooks.rb:339 0.174
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.832
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 1:0.624
Then Tails is running from USB drive "old" 0.267
And all tps features are active 7.334
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.175
And all persistence configuration files have safe access rights 0.328
And all persistent directories from the old Tails version have safe access rights 1.699
And I take note of which tps features are available 5.876
And I shutdown Tails and wait for the computer to power off 2.666
# 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.718
After features/support/hooks.rb:339 0.440
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.131
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.176
And I log in to a new session 12.271
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.617
And I plug USB drive "to_upgrade" 2.189
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.422
Then the running Tails is installed on USB drive "to_upgrade" 18.205
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 1.718
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.019
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.046
Then all tps features from the old Tails version are active 1.111
And Tails is running from USB drive "to_upgrade" 0.178
And the boot device has safe access rights 2.087
And the expected persistent files created with the old Tails version are present in the filesystem 0.910
And all persistent directories from the old Tails version have safe access rights 1.588
After features/support/hooks.rb:339 0.676
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:40.672
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.047
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.290
When the network is plugged 0.036
And Tor is ready 12.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.580
Given I shutdown Tails and wait for the computer to power off 6.613
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.203
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 10.774
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.089
# 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.186
When the network is plugged 0.038
And Tor is ready 10.453
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.370
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.828
Given I shutdown Tails and wait for the computer to power off 2.747
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.340
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.630
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.098
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.027
And Tor is ready 11.298
Then the Upgrader considers the system as up-to-date 0.095
# 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.329
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:339 0.683
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
19.846
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.294
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 10.305
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.831
After features/support/hooks.rb:339 0.836
After features/support/hooks.rb:108 0.000