Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 16 14 Aug 2026, 23:04

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 12:5.722 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:21.907
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 13.345
When I start Tails from USB drive "old" with network unplugged 1:4.226
Then the boot device has safe access rights 2.437
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 1.261
After features/support/hooks.rb:108 0.010
Tags: @product
1:26.233
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 50.490
Then Tails is running from USB drive "old" 0.199
And I create a persistent partition 24.175
And I take note of which tps features are available 6.628
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 4.126
After features/support/hooks.rb:339 0.654
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.019
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 "old" with network unplugged and I login with persistence enabled 1:1.989
Then Tails is running from USB drive "old" 0.204
And all tps features are active 7.243
When I write some files expected to persist 1.454
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.551
And I take note of which tps features are available 6.244
And I shutdown Tails and wait for the computer to power off 2.525
# 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.308
After features/support/hooks.rb:339 0.373
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.469
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.531
And I log in to a new session 11.202
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 2.195
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.815
Then the running Tails is installed on USB drive "to_upgrade" 17.850
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 3.587
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.184
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.803
Then all tps features from the old Tails version are active 1.151
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 2.187
And the expected persistent files created with the old Tails version are present in the filesystem 1.178
And all persistent directories from the old Tails version have safe access rights 1.546
After features/support/hooks.rb:339 0.470
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:49.639
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.090
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.168
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.027
And Tor is ready 12.812
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.375
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.276
Given I shutdown Tails and wait for the computer to power off 5.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.639
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 10.121
And the file system changes introduced in version 6.2~testoverlayfs are present 0.195
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.169
When the network is plugged 0.023
And Tor is ready 11.387
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.326
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.399
Given I shutdown Tails and wait for the computer to power off 5.198
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.932
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 10.648
And the file system changes introduced in version 6.3~testoverlayfs are present 0.233
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.156
When the network is plugged 0.034
And Tor is ready 10.164
Then the Upgrader considers the system as up-to-date 10.420
# 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.158
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.305
After features/support/hooks.rb:339 0.725
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
33.269
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 21.543
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.383
After features/support/hooks.rb:339 0.884
After features/support/hooks.rb:108 0.000