Project Number Date
test_Tails_ISO_21720-less-error-prone-emergency-release 4 21 Aug 2026, 16:16

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:47.538 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:18.700
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 14.036
When I start Tails from USB drive "old" with network unplugged 1:0.137
Then the boot device has safe access rights 2.627
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.244
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.396
After features/support/hooks.rb:108 0.050
Tags: @product
1:24.104
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 48.576
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 24.129
And I take note of which tps features are available 6.741
Then a Tails persistence partition exists on USB drive "old" 0.485
And I shutdown Tails and wait for the computer to power off 3.864
After features/support/hooks.rb:339 0.216
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.376
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.523
Then Tails is running from USB drive "old" 0.302
And all tps features are active 7.314
When I write some files expected to persist 1.132
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 1.637
And I take note of which tps features are available 6.843
And I shutdown Tails and wait for the computer to power off 2.599
# 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.501
After features/support/hooks.rb:339 0.431
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.022
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.755
And I log in to a new session 11.004
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.677
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.537
Then the running Tails is installed on USB drive "to_upgrade" 19.587
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 3.557
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.677
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.726
Then all tps features from the old Tails version are active 1.122
And Tails is running from USB drive "to_upgrade" 0.203
And the boot device has safe access rights 2.579
And the expected persistent files created with the old Tails version are present in the filesystem 1.100
And all persistent directories from the old Tails version have safe access rights 1.870
After features/support/hooks.rb:339 0.545
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
3:43.180
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.851
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.029
And Tor is ready 12.747
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.116
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.523
Given I shutdown Tails and wait for the computer to power off 5.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.170
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.242
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.166
When the network is plugged 0.023
And Tor is ready 10.542
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.973
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.754
Given I shutdown Tails and wait for the computer to power off 4.057
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.933
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 7.925
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.027
And Tor is ready 10.451
Then the Upgrader considers the system as up-to-date 0.160
# 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.645
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.317
After features/support/hooks.rb:339 0.707
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
19.477
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.022
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.921
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.000