Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 18 17 Aug 2026, 23:16

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:49.810 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:19.661
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.394
When I start Tails from USB drive "old" with network unplugged 1:2.313
Then the boot device has safe access rights 2.139
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.410
After features/support/hooks.rb:108 0.015
Tags: @product
1:24.012
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 48.379
Then Tails is running from USB drive "old" 0.256
And I create a persistent partition 24.328
And I take note of which tps features are available 6.602
Then a Tails persistence partition exists on USB drive "old" 0.461
And I shutdown Tails and wait for the computer to power off 3.908
After features/support/hooks.rb:339 0.322
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.183
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 1:0.105
Then Tails is running from USB drive "old" 0.166
And all tps features are active 7.294
When I write some files expected to persist 1.026
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.134
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.891
And I take note of which tps features are available 6.079
And I shutdown Tails and wait for the computer to power off 2.559
# 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.590
After features/support/hooks.rb:339 0.172
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.135
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 without a persistent partition and stopped at Tails Greeter's login screen 8.504
And I log in to a new session 12.753
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.647
And I plug USB drive "to_upgrade" 2.186
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.510
Then the running Tails is installed on USB drive "to_upgrade" 19.289
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 3.525
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.172
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.267
Then all tps features from the old Tails version are active 1.097
And Tails is running from USB drive "to_upgrade" 0.177
And the boot device has safe access rights 2.077
And the expected persistent files created with the old Tails version are present in the filesystem 0.934
And all persistent directories from the old Tails version have safe access rights 1.540
After features/support/hooks.rb:339 0.466
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:52.609
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 8.985
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.034
And Tor is ready 11.453
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.149
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.337
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:6.396
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 10.812
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.179
When the network is plugged 0.037
And Tor is ready 10.032
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.650
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.836
Given I shutdown Tails and wait for the computer to power off 2.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.777
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 10.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.154
When the network is plugged 0.034
And Tor is ready 10.284
Then the Upgrader considers the system as up-to-date 10.558
# 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.437
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.320
After features/support/hooks.rb:339 0.785
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.036
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 8.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
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.037
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.660
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.902
After features/support/hooks.rb:339 0.703
After features/support/hooks.rb:108 0.000