Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 22 25 Aug 2026, 23:05

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:25.665 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:4.141
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.188
When I start Tails from USB drive "old" with network unplugged 47.053
Then the boot device has safe access rights 2.225
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.155
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 1.254
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.061
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 48.791
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 23.867
And I take note of which tps features are available 6.494
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 3.917
After features/support/hooks.rb:339 0.231
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.256
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.180
Then Tails is running from USB drive "old" 0.225
And all tps features are active 8.048
When I write some files expected to persist 1.281
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
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.875
And I take note of which tps features are available 5.760
And I shutdown Tails and wait for the computer to power off 2.554
# 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.805
After features/support/hooks.rb:339 0.546
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.966
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.348
And I log in to a new session 11.927
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.615
And I plug USB drive "to_upgrade" 2.185
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.870
Then the running Tails is installed on USB drive "to_upgrade" 17.790
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 1.907
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.989
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.089
Then all tps features from the old Tails version are active 1.118
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.005
And the expected persistent files created with the old Tails version are present in the filesystem 1.030
And all persistent directories from the old Tails version have safe access rights 1.415
After features/support/hooks.rb:339 0.630
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:42.622
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.128
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.172
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.322
When the network is plugged 0.054
And Tor is ready 13.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.689
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.942
Given I shutdown Tails and wait for the computer to power off 5.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.790
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 10.562
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.198
When the network is plugged 0.046
And Tor is ready 10.766
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.939
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.964
Given I shutdown Tails and wait for the computer to power off 2.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.873
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 10.341
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.034
And Tor is ready 10.752
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.191
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.317
After features/support/hooks.rb:339 0.784
After features/support/hooks.rb:108 0.042
Tags: @product @automatic_upgrade
19.626
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 with a persistent partition enabled and logged in 7.797
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.032
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.453
After features/support/hooks.rb:339 0.532
After features/support/hooks.rb:108 0.000