Project Number Date
test_Tails_ISO_21651-persist-gnome-software-dconf-state 2 23 Jul 2026, 03:46

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:37.314 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:7.920
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
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.120
When I start Tails from USB drive "old" with network unplugged 50.353
Then the boot device has safe access rights 2.731
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:339 3.638
After features/support/hooks.rb:108 0.066
Tags: @product
1:29.233
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 53.281
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 23.591
And I take note of which tps features are available 3.721
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 7.822
After features/support/hooks.rb:339 0.625
After features/support/hooks.rb:108 0.017
Tags: @product
1:35.145
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.971
Then Tails is running from USB drive "old" 0.243
And all tps features are active 4.601
When I write some files expected to persist 1.199
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.284
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.904
And I shutdown Tails and wait for the computer to power off 8.182
# 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.743
After features/support/hooks.rb:339 0.216
After features/support/hooks.rb:108 0.008
Tags: @product
2:10.774
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.137
And I log in to a new session 13.330
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.861
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.172
Then the running Tails is installed on USB drive "to_upgrade" 14.732
And I unplug USB drive "to_upgrade" 0.175
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 2.119
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.055
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.045
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.071
Then all tps features from the old Tails version are active 0.942
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.428
And the expected persistent files created with the old Tails version are present in the filesystem 1.065
And all persistent directories from the old Tails version have safe access rights 2.250
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:42.313
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.863
And no SquashFS delta is installed 0.062
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.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.016
And Tor is ready 12.419
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.515
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.374
Given I shutdown Tails and wait for the computer to power off 6.847
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.808
Then Tails is running version 6.2~testoverlayfs 0.027
And all tps features are active 4.524
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.188
When the network is plugged 0.012
And Tor is ready 9.671
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.907
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.964
Given I shutdown Tails and wait for the computer to power off 4.038
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.517
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.598
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.016
And Tor is ready 10.849
Then the Upgrader considers the system as up-to-date 10.504
# 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 4.170
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.408
After features/support/hooks.rb:339 0.582
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
21.870
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.312
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 11.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.435
After features/support/hooks.rb:339 0.853
After features/support/hooks.rb:108 0.000