Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 12 10 Aug 2026, 22:58

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.246 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:8.519
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.212
When I start Tails from USB drive "old" with network unplugged 51.681
Then the boot device has safe access rights 1.948
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.144
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 3.531
After features/support/hooks.rb:108 0.040
Tags: @product
1:18.788
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 45.834
Then Tails is running from USB drive "old" 0.216
And I create a persistent partition 22.436
And I take note of which tps features are available 5.819
Then a Tails persistence partition exists on USB drive "old" 0.467
And I shutdown Tails and wait for the computer to power off 3.929
After features/support/hooks.rb:339 0.538
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.559
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.856
Then Tails is running from USB drive "old" 0.263
And all tps features are active 7.200
When I write some files expected to persist 1.088
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.119
And all persistence configuration files have safe access rights 0.213
And all persistent directories from the old Tails version have safe access rights 1.601
And I take note of which tps features are available 5.519
And I shutdown Tails and wait for the computer to power off 2.495
# 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.124
After features/support/hooks.rb:339 0.244
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.510
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.130
And I log in to a new session 12.125
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.563
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.637
Then the running Tails is installed on USB drive "to_upgrade" 17.516
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.803
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.564
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.622
Then all tps features from the old Tails version are active 1.124
And Tails is running from USB drive "to_upgrade" 0.182
And the boot device has safe access rights 2.214
And the expected persistent files created with the old Tails version are present in the filesystem 0.801
And all persistent directories from the old Tails version have safe access rights 1.543
After features/support/hooks.rb:339 0.606
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:30.161
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.854
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.299
When the network is plugged 0.036
And Tor is ready 10.890
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.411
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.517
Given I shutdown Tails and wait for the computer to power off 5.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.303
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.646
And the file system changes introduced in version 6.2~testoverlayfs are present 0.172
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.160
When the network is plugged 0.033
And Tor is ready 10.346
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.878
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.323
Given I shutdown Tails and wait for the computer to power off 2.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.500
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.763
And the file system changes introduced in version 6.3~testoverlayfs are present 0.303
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.096
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.032
And Tor is ready 10.087
Then the Upgrader considers the system as up-to-date 0.104
# 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.210
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.644
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
18.142
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.769
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.987
After features/support/hooks.rb:339 0.520
After features/support/hooks.rb:108 0.000