Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 15 13 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:28.430 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:2.437
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.228
When I start Tails from USB drive "old" with network unplugged 45.362
Then the boot device has safe access rights 2.167
And Tails is running from USB drive "old" 0.169
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.159
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.585
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.837
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 49.614
Then Tails is running from USB drive "old" 0.180
And I create a persistent partition 23.480
And I take note of which tps features are available 6.756
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 4.159
After features/support/hooks.rb:339 0.463
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.407
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.245
Then Tails is running from USB drive "old" 0.193
And all tps features are active 7.306
When I write some files expected to persist 1.185
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.342
And all persistent directories from the old Tails version have safe access rights 1.737
And I take note of which tps features are available 6.731
And I shutdown Tails and wait for the computer to power off 3.935
# 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.501
After features/support/hooks.rb:339 0.400
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.728
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.460
And I log in to a new session 13.189
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.769
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.777
Then the running Tails is installed on USB drive "to_upgrade" 18.019
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:339 2.096
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.190
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.902
Then all tps features from the old Tails version are active 1.135
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.336
And the expected persistent files created with the old Tails version are present in the filesystem 0.954
And all persistent directories from the old Tails version have safe access rights 1.569
After features/support/hooks.rb:339 0.436
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:42.814
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 7.971
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.030
And Tor is ready 13.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.877
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.802
Given I shutdown Tails and wait for the computer to power off 5.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.299
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 10.440
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.242
When the network is plugged 0.031
And Tor is ready 10.319
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.935
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.694
Given I shutdown Tails and wait for the computer to power off 3.984
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.739
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 10.143
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.029
And Tor is ready 10.704
Then the Upgrader considers the system as up-to-date 0.103
# 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.120
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:339 0.730
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
20.013
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.312
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.786
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.516
After features/support/hooks.rb:339 0.657
After features/support/hooks.rb:108 0.000