Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 17 15 Aug 2026, 23:08

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:44.892 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.090
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.661
When I start Tails from USB drive "old" with network unplugged 56.637
Then the boot device has safe access rights 2.105
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.637
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.594
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 48.200
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 22.792
And I take note of which tps features are available 6.154
Then a Tails persistence partition exists on USB drive "old" 0.495
And I shutdown Tails and wait for the computer to power off 2.609
After features/support/hooks.rb:339 0.233
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.858
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:0.700
Then Tails is running from USB drive "old" 0.199
And all tps features are active 7.342
When I write some files expected to persist 1.183
# 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.291
And all persistent directories from the old Tails version have safe access rights 1.683
And I take note of which tps features are available 5.769
And I shutdown Tails and wait for the computer to power off 2.617
# 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.798
After features/support/hooks.rb:339 0.480
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.965
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 without a persistent partition and stopped at Tails Greeter's login screen 8.410
And I log in to a new session 12.228
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.608
And I plug USB drive "to_upgrade" 2.179
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.907
Then the running Tails is installed on USB drive "to_upgrade" 19.326
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:339 1.761
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.703
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.840
Then all tps features from the old Tails version are active 1.024
And Tails is running from USB drive "to_upgrade" 0.197
And the boot device has safe access rights 2.020
And the expected persistent files created with the old Tails version are present in the filesystem 0.916
And all persistent directories from the old Tails version have safe access rights 1.604
After features/support/hooks.rb:339 0.473
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:53.581
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 21.101
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.175
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.256
When the network is plugged 0.038
And Tor is ready 11.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.044
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.119
Given I shutdown Tails and wait for the computer to power off 5.410
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.529
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 10.032
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.212
When the network is plugged 0.036
And Tor is ready 10.339
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.826
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.466
Given I shutdown Tails and wait for the computer to power off 2.670
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.655
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.163
When the network is plugged 0.025
And Tor is ready 10.512
Then the Upgrader considers the system as up-to-date 0.089
# 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.550
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 0.767
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.097
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.643
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 10.593
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.555
After features/support/hooks.rb:339 0.575
After features/support/hooks.rb:108 0.000