Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 23 26 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:2.101 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:10.462
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.901
When I start Tails from USB drive "old" with network unplugged 53.694
Then the boot device has safe access rights 2.158
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.142
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 1.458
After features/support/hooks.rb:108 0.006
Tags: @product
1:17.969
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 47.093
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 21.680
And I take note of which tps features are available 5.752
Then a Tails persistence partition exists on USB drive "old" 0.457
And I shutdown Tails and wait for the computer to power off 2.693
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.520
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.575
Then Tails is running from USB drive "old" 0.213
And all tps features are active 6.978
When I write some files expected to persist 0.995
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.235
And all persistent directories from the old Tails version have safe access rights 1.541
And I take note of which tps features are available 5.785
And I shutdown Tails and wait for the computer to power off 2.589
# 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.357
After features/support/hooks.rb:339 0.279
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.122
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.175
And I log in to a new session 11.839
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.539
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.690
Then the running Tails is installed on USB drive "to_upgrade" 17.429
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.779
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.390
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.840
Then all tps features from the old Tails version are active 0.973
And Tails is running from USB drive "to_upgrade" 0.192
And the boot device has safe access rights 1.962
And the expected persistent files created with the old Tails version are present in the filesystem 0.893
And all persistent directories from the old Tails version have safe access rights 1.453
After features/support/hooks.rb:339 0.772
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:28.456
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.806
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.173
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.260
When the network is plugged 0.046
And Tor is ready 11.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.407
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.660
Given I shutdown Tails and wait for the computer to power off 5.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.759
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.596
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.110
# 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.154
When the network is plugged 0.035
And Tor is ready 10.132
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.425
Given I shutdown Tails and wait for the computer to power off 2.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.753
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 9.795
And the file system changes introduced in version 6.3~testoverlayfs are present 0.262
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.024
And Tor is ready 10.028
Then the Upgrader considers the system as up-to-date 0.090
# 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.100
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.268
After features/support/hooks.rb:339 0.992
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.179
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.799
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
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.041
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.155
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.902
After features/support/hooks.rb:339 0.925
After features/support/hooks.rb:108 0.000