Project Number Date
test_Tails_ISO_21615-debian-security-updates-supersede-custom-packages 1 25 May 2026, 15:09

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:37.122 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:11.623
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.623
When I start Tails from USB drive "old" with network unplugged 53.456
Then the boot device has safe access rights 2.751
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:335 3.477
After features/support/hooks.rb:104 0.010
Tags: @product
1:29.712
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 55.417
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 25.687
And I take note of which tps features are available 0.460
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 7.071
After features/support/hooks.rb:335 0.238
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.711
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.069
Then Tails is running from USB drive "old" 0.257
And all tps features are active 1.109
When I write some files expected to persist 1.157
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.824
And I take note of which tps features are available 0.161
And I shutdown Tails and wait for the computer to power off 8.223
# 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.368
After features/support/hooks.rb:335 0.127
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.930
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.978
And I log in to a new session 12.643
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.783
And I plug USB drive "to_upgrade" 2.321
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.070
Then the running Tails is installed on USB drive "to_upgrade" 15.836
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:335 2.388
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.896
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.027
Then all tps features from the old Tails version are active 0.889
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.431
And the expected persistent files created with the old Tails version are present in the filesystem 1.094
And all persistent directories from the old Tails version have safe access rights 2.135
After features/support/hooks.rb:335 0.804
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:43.376
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.248
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.379
When the network is plugged 0.021
And Tor is ready 13.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.711
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.688
Given I shutdown Tails and wait for the computer to power off 9.920
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.034
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.397
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.214
When the network is plugged 0.016
And Tor is ready 11.250
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.628
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.665
Given I shutdown Tails and wait for the computer to power off 8.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.679
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.103
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.015
And Tor is ready 10.429
Then the Upgrader considers the system as up-to-date 10.623
# 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.787
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.497
After features/support/hooks.rb:335 1.056
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.871
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.619
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.206
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.706
After features/support/hooks.rb:335 0.894
After features/support/hooks.rb:104 0.000