Project Number Date
test_Tails_ISO_21773-wait-for-appstream-before-snapshot 2 28 Oct 2026, 18:48

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:54.027 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:15.165
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 17.012
When I start Tails from USB drive "old" with network unplugged 53.736
Then the boot device has safe access rights 2.624
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 1.340
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.597
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login 51.783
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 23.937
And I take note of which tps features are available 9.342
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 4.615
After features/support/hooks.rb:339 0.246
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.839
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.434
Then Tails is running from USB drive "old" 0.227
And all tps features are active 9.601
When I write some files expected to persist 1.273
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.135
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.938
And I take note of which tps features are available 6.981
And I shutdown Tails and wait for the computer to power off 3.974
# 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.877
After features/support/hooks.rb:339 0.509
After features/support/hooks.rb:108 0.005
Tags: @product
2:17.768
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.863
And I log in to a new session 12.445
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.674
And I plug USB drive "to_upgrade" 2.294
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.039
Then the running Tails is installed on USB drive "to_upgrade" 19.184
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 1.852
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.990
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.116
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.987
Then all tps features from the old Tails version are active 1.301
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 1.918
And the expected persistent files created with the old Tails version are present in the filesystem 0.906
And all persistent directories from the old Tails version have safe access rights 1.528
After features/support/hooks.rb:339 0.793
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:38.148
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.176
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
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.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.322
When the network is plugged 0.046
And Tor is ready 12.358
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.930
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.795
Given I shutdown Tails and wait for the computer to power off 5.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.090
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.471
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.093
# 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.171
When the network is plugged 0.027
And Tor is ready 10.350
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.836
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.706
Given I shutdown Tails and wait for the computer to power off 3.928
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.075
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.579
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.029
And Tor is ready 10.900
Then the Upgrader considers the system as up-to-date 0.105
# 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.526
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.347
After features/support/hooks.rb:339 0.780
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.517
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.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
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.046
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.870
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.000