Project Number Date
test_Tails_ISO_21773-wait-for-appstream-before-snapshot 3 29 Oct 2026, 02:15

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 10:48.230 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:1.514
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.110
When I start Tails from USB drive "old" with network unplugged 44.983
Then the boot device has safe access rights 1.820
And Tails is running from USB drive "old" 0.168
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.025
And udev-watchdog is monitoring the correct device 0.128
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.557
After features/support/hooks.rb:108 0.042
Tags: @product
1:19.588
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login 46.347
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 22.204
And I take note of which tps features are available 6.214
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 3.973
After features/support/hooks.rb:339 0.273
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.437
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.536
Then Tails is running from USB drive "old" 0.254
And all tps features are active 6.956
When I write some files expected to persist 1.105
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.222
And all persistent directories from the old Tails version have safe access rights 1.606
And I take note of which tps features are available 5.801
And I shutdown Tails and wait for the computer to power off 2.513
# 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.190
After features/support/hooks.rb:339 0.371
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.871
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.433
And I log in to a new session 12.553
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.683
And I plug USB drive "to_upgrade" 2.167
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.599
Then the running Tails is installed on USB drive "to_upgrade" 17.209
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 1.728
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.310
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.167
Then all tps features from the old Tails version are active 0.955
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.266
And the expected persistent files created with the old Tails version are present in the filesystem 0.994
And all persistent directories from the old Tails version have safe access rights 1.632
After features/support/hooks.rb:339 0.870
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
3:20.867
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.047
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
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.165
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.282
When the network is plugged 0.034
And Tor is ready 11.228
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.910
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.260
Given I shutdown Tails and wait for the computer to power off 5.226
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.810
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.600
And the file system changes introduced in version 6.2~testoverlayfs are present 0.179
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.183
When the network is plugged 0.024
And Tor is ready 10.021
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.869
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.632
Given I shutdown Tails and wait for the computer to power off 4.011
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.432
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.351
And the file system changes introduced in version 6.3~testoverlayfs are present 0.240
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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.148
When the network is plugged 0.036
And Tor is ready 9.996
Then the Upgrader considers the system as up-to-date 0.118
# 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.090
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.305
After features/support/hooks.rb:339 0.890
After features/support/hooks.rb:108 0.053
Tags: @product @automatic_upgrade
19.641
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.795
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.476
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.033
After features/support/hooks.rb:339 0.498
After features/support/hooks.rb:108 0.000