Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 43 30 Jun 2026, 20:02

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.053 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:10.421
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.335
When I start Tails from USB drive "old" with network unplugged 52.582
Then the boot device has safe access rights 2.719
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.673
After features/support/hooks.rb:108 0.048
Tags: @product
1:28.179
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 50.911
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 24.234
And I take note of which tps features are available 4.172
Then a Tails persistence partition exists on USB drive "old" 0.493
And I shutdown Tails and wait for the computer to power off 8.059
After features/support/hooks.rb:339 0.172
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.187
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.793
Then Tails is running from USB drive "old" 0.301
And all tps features are active 4.741
When I write some files expected to persist 1.222
# 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.894
And I take note of which tps features are available 3.659
And I shutdown Tails and wait for the computer to power off 4.106
# 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.950
After features/support/hooks.rb:339 0.131
After features/support/hooks.rb:108 0.008
Tags: @product
2:12.446
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.093
And I log in to a new session 14.438
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.783
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.320
Then the running Tails is installed on USB drive "to_upgrade" 15.305
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 3.649
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.469
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.031
Then all tps features from the old Tails version are active 0.934
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.446
And the expected persistent files created with the old Tails version are present in the filesystem 1.046
And all persistent directories from the old Tails version have safe access rights 1.738
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:42.083
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.031
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.016
And Tor is ready 12.064
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.144
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.042
Given I shutdown Tails and wait for the computer to power off 6.791
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.017
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.746
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.197
When the network is plugged 0.036
And Tor is ready 9.707
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.941
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.749
Given I shutdown Tails and wait for the computer to power off 4.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.196
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.543
And the file system changes introduced in version 6.3~testoverlayfs are present 0.319
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.126
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 9.761
Then the Upgrader considers the system as up-to-date 10.495
# 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.773
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.309
After features/support/hooks.rb:339 0.869
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
20.266
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.568
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.277
After features/support/hooks.rb:339 0.925
After features/support/hooks.rb:108 0.000