Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 10 09 Aug 2026, 19:15

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:9.734 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:5.722
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.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.209
When I start Tails from USB drive "old" with network unplugged 48.650
Then the boot device has safe access rights 2.192
And Tails is running from USB drive "old" 0.204
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.153
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 1.263
After features/support/hooks.rb:108 0.015
Tags: @product
1:20.062
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 45.855
Then Tails is running from USB drive "old" 0.192
And I create a persistent partition 22.540
And I take note of which tps features are available 5.863
Then a Tails persistence partition exists on USB drive "old" 0.453
And I shutdown Tails and wait for the computer to power off 5.078
After features/support/hooks.rb:339 0.227
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.383
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.584
Then Tails is running from USB drive "old" 0.197
And all tps features are active 6.876
When I write some files expected to persist 1.094
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.276
And all persistent directories from the old Tails version have safe access rights 1.545
And I take note of which tps features are available 5.825
And I shutdown Tails and wait for the computer to power off 2.585
# 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.184
After features/support/hooks.rb:339 0.417
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.043
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.314
And I log in to a new session 11.576
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.699
And I plug USB drive "to_upgrade" 2.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.016
Then the running Tails is installed on USB drive "to_upgrade" 16.974
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 3.575
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.422
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.680
Then all tps features from the old Tails version are active 1.039
And Tails is running from USB drive "to_upgrade" 0.202
And the boot device has safe access rights 2.037
And the expected persistent files created with the old Tails version are present in the filesystem 0.847
And all persistent directories from the old Tails version have safe access rights 1.540
After features/support/hooks.rb:339 0.728
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:39.795
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.879
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.323
When the network is plugged 0.033
And Tor is ready 10.857
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.010
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.790
Given I shutdown Tails and wait for the computer to power off 5.354
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.424
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.738
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.091
# 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.204
When the network is plugged 0.032
And Tor is ready 10.099
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.355
Given I shutdown Tails and wait for the computer to power off 2.537
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.395
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.068
And the file system changes introduced in version 6.3~testoverlayfs are present 0.270
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.027
And Tor is ready 10.026
Then the Upgrader considers the system as up-to-date 10.413
# 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.091
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.247
After features/support/hooks.rb:339 0.963
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.304
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.544
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 9.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.860
After features/support/hooks.rb:339 0.819
After features/support/hooks.rb:108 0.000