Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 25 28 Aug 2026, 23:09

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:54.083 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:20.178
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.210
When I start Tails from USB drive "old" with network unplugged 1:3.309
Then the boot device has safe access rights 1.908
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.370
After features/support/hooks.rb:108 0.041
Tags: @product
1:26.428
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.115
And I start Tails from USB drive "old" with network unplugged and I login 48.289
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 23.334
And I take note of which tps features are available 5.984
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 7.880
After features/support/hooks.rb:339 0.422
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.697
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.988
Then Tails is running from USB drive "old" 0.294
And all tps features are active 7.527
When I write some files expected to persist 0.990
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.125
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 1.479
And I take note of which tps features are available 6.822
And I shutdown Tails and wait for the computer to power off 3.960
# 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.119
After features/support/hooks.rb:339 0.118
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.235
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.618
And I log in to a new session 12.832
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.595
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.302
Then the running Tails is installed on USB drive "to_upgrade" 18.395
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.936
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.149
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.637
Then all tps features from the old Tails version are active 1.117
And Tails is running from USB drive "to_upgrade" 0.181
And the boot device has safe access rights 2.100
And the expected persistent files created with the old Tails version are present in the filesystem 1.181
And all persistent directories from the old Tails version have safe access rights 1.836
After features/support/hooks.rb:339 0.464
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:39.494
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.253
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.294
When the network is plugged 0.042
And Tor is ready 12.145
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.580
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.028
Given I shutdown Tails and wait for the computer to power off 6.570
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.380
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 10.117
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# 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.196
When the network is plugged 0.039
And Tor is ready 10.808
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.336
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.654
Given I shutdown Tails and wait for the computer to power off 2.515
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.358
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 10.402
And the file system changes introduced in version 6.3~testoverlayfs are present 0.254
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.026
And Tor is ready 10.131
Then the Upgrader considers the system as up-to-date 0.104
# 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.590
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:339 0.883
After features/support/hooks.rb:108 0.032
Tags: @product @automatic_upgrade
31.898
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.973
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.128
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 8.393
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.096
After features/support/hooks.rb:339 0.792
After features/support/hooks.rb:108 0.000