Project Number Date
test_Tails_ISO_21651-persist-gnome-software-dconf-state 5 24 Jul 2026, 03:44

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:28.211 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:11.162
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.185
When I start Tails from USB drive "old" with network unplugged 53.662
Then the boot device has safe access rights 2.553
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.424
After features/support/hooks.rb:108 0.051
Tags: @product
1:25.164
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 53.656
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 23.019
And I take note of which tps features are available 3.671
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 4.003
After features/support/hooks.rb:339 0.293
After features/support/hooks.rb:108 0.008
Tags: @product
1:30.250
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.169
Then Tails is running from USB drive "old" 0.230
And all tps features are active 4.830
When I write some files expected to persist 1.188
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 1.822
And I take note of which tps features are available 3.527
And I shutdown Tails and wait for the computer to power off 4.002
# 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.952
After features/support/hooks.rb:339 0.589
After features/support/hooks.rb:108 0.007
Tags: @product
2:9.878
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 7.910
And I log in to a new session 12.477
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.660
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.418
Then the running Tails is installed on USB drive "to_upgrade" 14.922
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:339 2.196
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.016
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.695
Then all tps features from the old Tails version are active 0.959
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.390
And the expected persistent files created with the old Tails version are present in the filesystem 0.969
And all persistent directories from the old Tails version have safe access rights 1.700
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:41.484
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 8.057
And no SquashFS delta is installed 0.065
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.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.015
And Tor is ready 13.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.414
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.689
Given I shutdown Tails and wait for the computer to power off 6.687
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.878
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.798
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
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.148
# 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.202
When the network is plugged 0.018
And Tor is ready 10.852
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.342
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.756
Given I shutdown Tails and wait for the computer to power off 4.157
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.812
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.652
And the file system changes introduced in version 6.3~testoverlayfs are present 0.312
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.016
And Tor is ready 9.691
Then the Upgrader considers the system as up-to-date 10.519
# 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.805
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.303
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
20.255
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.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.767
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.062
After features/support/hooks.rb:339 0.958
After features/support/hooks.rb:108 0.000