Project Number Date
test_Tails_ISO_21651-persist-gnome-software-dconf-state 8 27 Jul 2026, 03:45

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 12:11.578 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:12.705
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.012
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.923
When I start Tails from USB drive "old" with network unplugged 53.899
Then the boot device has safe access rights 2.896
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:339 3.997
After features/support/hooks.rb:108 0.014
Tags: @product
1:30.397
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 56.271
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 24.722
And I take note of which tps features are available 4.505
Then a Tails persistence partition exists on USB drive "old" 0.542
And I shutdown Tails and wait for the computer to power off 4.014
After features/support/hooks.rb:339 0.473
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.857
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.500
Then Tails is running from USB drive "old" 0.260
And all tps features are active 5.738
When I write some files expected to persist 1.523
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 1.999
And I take note of which tps features are available 4.219
And I shutdown Tails and wait for the computer to power off 4.447
# 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" 12.618
After features/support/hooks.rb:339 0.591
After features/support/hooks.rb:108 0.047
Tags: @product
2:14.268
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.317
And I log in to a new session 13.611
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.812
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.367
Then the running Tails is installed on USB drive "to_upgrade" 16.620
And I unplug USB drive "to_upgrade" 0.161
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 2.417
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.544
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.718
Then all tps features from the old Tails version are active 1.236
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.753
And the expected persistent files created with the old Tails version are present in the filesystem 1.268
And all persistent directories from the old Tails version have safe access rights 2.245
After features/support/hooks.rb:339 0.766
After features/support/hooks.rb:108 0.052
Tags: @product @automatic_upgrade
3:57.263
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.115
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.360
When the network is plugged 0.017
And Tor is ready 13.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.172
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.590
Given I shutdown Tails and wait for the computer to power off 7.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.324
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.802
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.177
# 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.221
When the network is plugged 0.015
And Tor is ready 9.789
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.316
Given I shutdown Tails and wait for the computer to power off 4.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.551
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.225
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.041
And Tor is ready 10.871
Then the Upgrader considers the system as up-to-date 10.522
# 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.370
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:339 0.867
After features/support/hooks.rb:108 0.052
Tags: @product @automatic_upgrade
20.540
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.414
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.034
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.715
After features/support/hooks.rb:339 0.728
After features/support/hooks.rb:108 0.000