Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 19 19 Aug 2026, 22:59

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:0.119 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:6.000
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.070
When I start Tails from USB drive "old" with network unplugged 49.296
Then the boot device has safe access rights 1.979
And Tails is running from USB drive "old" 0.181
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.141
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:339 1.669
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.183
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 46.997
Then Tails is running from USB drive "old" 0.194
And I create a persistent partition 22.125
And I take note of which tps features are available 5.815
Then a Tails persistence partition exists on USB drive "old" 0.426
And I shutdown Tails and wait for the computer to power off 2.549
After features/support/hooks.rb:339 0.154
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.924
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.208
Then Tails is running from USB drive "old" 0.192
And all tps features are active 6.998
When I write some files expected to persist 1.030
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.246
And all persistent directories from the old Tails version have safe access rights 1.615
And I take note of which tps features are available 5.864
And I shutdown Tails and wait for the computer to power off 5.332
# 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.189
After features/support/hooks.rb:339 0.343
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.381
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.010
And I log in to a new session 11.899
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.561
And I plug USB drive "to_upgrade" 2.164
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.788
Then the running Tails is installed on USB drive "to_upgrade" 16.694
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 1.907
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.557
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:0.665
Then all tps features from the old Tails version are active 1.065
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.117
And the expected persistent files created with the old Tails version are present in the filesystem 0.896
And all persistent directories from the old Tails version have safe access rights 1.529
After features/support/hooks.rb:339 0.592
After features/support/hooks.rb:108 0.005
3:29.426
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.740
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.166
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.024
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.289
When the network is plugged 0.034
And Tor is ready 11.784
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.927
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.648
Given I shutdown Tails and wait for the computer to power off 5.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.716
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 9.791
And the file system changes introduced in version 6.2~testoverlayfs are present 0.159
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.090
# 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.175
When the network is plugged 0.036
And Tor is ready 10.118
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.887
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.485
Given I shutdown Tails and wait for the computer to power off 2.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.386
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.657
And the file system changes introduced in version 6.3~testoverlayfs are present 0.263
And only the 6.3~testoverlayfs SquashFS delta is installed 0.027
# 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.075
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.154
When the network is plugged 0.042
And Tor is ready 10.105
Then the Upgrader considers the system as up-to-date 0.082
# 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.108
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.283
After features/support/hooks.rb:339 0.868
After features/support/hooks.rb:108 0.015
18.644
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.841
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.025
And Tor is ready 7.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.503
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.000