Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 8 08 Aug 2026, 23:00

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:21.872 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:18.125
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.051
When I start Tails from USB drive "old" with network unplugged 1:1.529
Then the boot device has safe access rights 1.809
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.405
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.629
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 46.929
Then Tails is running from USB drive "old" 0.196
And I create a persistent partition 22.486
And I take note of which tps features are available 6.312
Then a Tails persistence partition exists on USB drive "old" 0.454
And I shutdown Tails and wait for the computer to power off 5.180
After features/support/hooks.rb:339 0.211
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.920
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 56.260
Then Tails is running from USB drive "old" 0.162
And all tps features are active 6.599
When I write some files expected to persist 0.871
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.105
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.378
And I take note of which tps features are available 5.750
And I shutdown Tails and wait for the computer to power off 2.529
# 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" 10.920
After features/support/hooks.rb:339 0.435
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.116
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.123
And I log in to a new session 11.911
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.713
And I plug USB drive "to_upgrade" 2.177
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.842
Then the running Tails is installed on USB drive "to_upgrade" 17.115
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 1.988
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.231
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.052
Then all tps features from the old Tails version are active 0.898
And Tails is running from USB drive "to_upgrade" 0.151
And the boot device has safe access rights 1.805
And the expected persistent files created with the old Tails version are present in the filesystem 0.770
And all persistent directories from the old Tails version have safe access rights 1.449
After features/support/hooks.rb:339 0.924
After features/support/hooks.rb:108 0.013
3:42.609
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.000
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.170
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.263
When the network is plugged 0.027
And Tor is ready 11.193
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.014
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.186
Given I shutdown Tails and wait for the computer to power off 5.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.134
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 9.560
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.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.178
When the network is plugged 0.034
And Tor is ready 10.926
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.295
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.457
Given I shutdown Tails and wait for the computer to power off 5.201
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.617
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.863
And the file system changes introduced in version 6.3~testoverlayfs are present 0.277
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.087
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.161
When the network is plugged 0.041
And Tor is ready 10.130
Then the Upgrader considers the system as up-to-date 10.397
# 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.052
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.322
After features/support/hooks.rb:339 0.656
After features/support/hooks.rb:108 0.020
18.238
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.764
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.044
And the signing key used by the Upgrader is outdated 0.031
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 8.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.040
After features/support/hooks.rb:339 0.869
After features/support/hooks.rb:108 0.000