Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 35 22 Jun 2026, 19:59

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:46.710 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:16.760
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 12.964
When I start Tails from USB drive "old" with network unplugged 59.321
Then the boot device has safe access rights 2.744
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.854
After features/support/hooks.rb:108 0.037
Tags: @product
1:29.911
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login 51.855
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 24.834
And I take note of which tps features are available 4.224
Then a Tails persistence partition exists on USB drive "old" 0.525
And I shutdown Tails and wait for the computer to power off 8.141
After features/support/hooks.rb:339 0.482
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.200
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.951
Then Tails is running from USB drive "old" 0.278
And all tps features are active 4.904
When I write some files expected to persist 1.179
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 1.856
And I take note of which tps features are available 3.658
And I shutdown Tails and wait for the computer to power off 7.796
# 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.079
After features/support/hooks.rb:339 0.164
After features/support/hooks.rb:108 0.007
Tags: @product
2:11.918
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.327
And I log in to a new session 13.382
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.737
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.738
Then the running Tails is installed on USB drive "to_upgrade" 15.262
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 2.404
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.124
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.768
Then all tps features from the old Tails version are active 0.874
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.292
And the expected persistent files created with the old Tails version are present in the filesystem 1.001
And all persistent directories from the old Tails version have safe access rights 1.905
After features/support/hooks.rb:339 0.589
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:43.510
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.157
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.016
And Tor is ready 13.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.545
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.363
Given I shutdown Tails and wait for the computer to power off 6.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.249
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 4.751
And the file system changes introduced in version 6.2~testoverlayfs are present 0.188
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.198
When the network is plugged 0.013
And Tor is ready 9.874
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.019
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.878
Given I shutdown Tails and wait for the computer to power off 2.757
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.409
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.736
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.018
And Tor is ready 11.189
Then the Upgrader considers the system as up-to-date 10.493
# 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.411
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:339 0.970
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.284
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 7.390
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 8.343
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.151
After features/support/hooks.rb:339 0.933
After features/support/hooks.rb:108 0.000