Project Number Date
test_Tails_ISO_21882-reproduce-omni-ja 2 02 Nov 2026, 19:41

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:50.147 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:24.119
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.304
When I start Tails from USB drive "old" with network unplugged 1:5.462
Then the boot device has safe access rights 2.587
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 1.532
After features/support/hooks.rb:108 0.010
Tags: @product
1:26.917
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 50.770
Then Tails is running from USB drive "old" 0.212
And I create a persistent partition 24.417
And I take note of which tps features are available 6.798
Then a Tails persistence partition exists on USB drive "old" 0.616
And I shutdown Tails and wait for the computer to power off 4.002
After features/support/hooks.rb:339 0.414
After features/support/hooks.rb:108 0.007
Tags: @product
1:37.095
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.783
Then Tails is running from USB drive "old" 0.203
And all tps features are active 7.382
When I write some files expected to persist 1.189
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 1.944
And I take note of which tps features are available 6.250
And I shutdown Tails and wait for the computer to power off 2.597
# 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.112
After features/support/hooks.rb:339 0.179
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.371
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.554
And I log in to a new session 11.839
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.951
And I plug USB drive "to_upgrade" 2.326
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.073
Then the running Tails is installed on USB drive "to_upgrade" 18.374
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.168
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.095
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.146
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.041
Then all tps features from the old Tails version are active 1.223
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.545
And the expected persistent files created with the old Tails version are present in the filesystem 0.967
And all persistent directories from the old Tails version have safe access rights 1.898
After features/support/hooks.rb:339 0.599
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.108
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.526
And no SquashFS delta is installed 0.200
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.311
When the network is plugged 0.025
And Tor is ready 12.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.034
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.163
Given I shutdown Tails and wait for the computer to power off 5.707
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.633
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.735
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.205
When the network is plugged 0.041
And Tor is ready 10.559
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.407
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.886
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.673
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 7.916
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.168
When the network is plugged 0.033
And Tor is ready 10.507
Then the Upgrader considers the system as up-to-date 0.092
# 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.572
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.306
After features/support/hooks.rb:339 0.739
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
19.439
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.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
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.033
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.045
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.874
After features/support/hooks.rb:339 0.719
After features/support/hooks.rb:108 0.000