Project Number Date
test_Tails_ISO_21756-better-support-build-machine 2 30 Sep 2026, 19:54

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:33.985 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.012
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.261
When I start Tails from USB drive "old" with network unplugged 47.900
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:339 3.630
After features/support/hooks.rb:108 0.037
Tags: @product
1:25.183
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login 49.815
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 24.816
And I take note of which tps features are available 6.871
Then a Tails persistence partition exists on USB drive "old" 0.708
And I shutdown Tails and wait for the computer to power off 2.645
After features/support/hooks.rb:339 0.131
After features/support/hooks.rb:108 0.008
Tags: @product
1:37.395
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.956
Then Tails is running from USB drive "old" 0.224
And all tps features are active 7.920
When I write some files expected to persist 1.221
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.318
And all persistent directories from the old Tails version have safe access rights 2.082
And I take note of which tps features are available 6.208
And I shutdown Tails and wait for the computer to power off 4.068
# 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.138
After features/support/hooks.rb:339 0.415
After features/support/hooks.rb:108 0.005
Tags: @product
2:17.101
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.551
And I log in to a new session 13.498
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.672
And I plug USB drive "to_upgrade" 2.628
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.183
Then the running Tails is installed on USB drive "to_upgrade" 19.335
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.109
After features/support/hooks.rb:339 0.643
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.286
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.398
Then all tps features from the old Tails version are active 1.150
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.457
And the expected persistent files created with the old Tails version are present in the filesystem 0.958
And all persistent directories from the old Tails version have safe access rights 1.987
After features/support/hooks.rb:339 1.060
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:35.108
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.526
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.037
And Tor is ready 13.478
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.332
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.763
Given I shutdown Tails and wait for the computer to power off 5.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.995
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.532
And the file system changes introduced in version 6.2~testoverlayfs are present 0.171
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.132
# 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.170
When the network is plugged 0.024
And Tor is ready 11.155
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.321
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.830
Given I shutdown Tails and wait for the computer to power off 2.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.829
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.019
And the file system changes introduced in version 6.3~testoverlayfs are present 0.361
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.036
And Tor is ready 10.230
Then the Upgrader considers the system as up-to-date 0.077
# 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.264
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.425
After features/support/hooks.rb:339 0.753
After features/support/hooks.rb:108 0.055
Tags: @product @automatic_upgrade
19.897
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.635
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
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.037
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 9.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.918
After features/support/hooks.rb:339 0.788
After features/support/hooks.rb:108 0.000