Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 37 24 Jun 2026, 20:13

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 12:15.735 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:21.097
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.775
When I start Tails from USB drive "old" with network unplugged 1:2.464
Then the boot device has safe access rights 3.002
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.265
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 1.618
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.952
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 54.099
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 24.804
And I take note of which tps features are available 4.024
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 4.110
After features/support/hooks.rb:339 0.620
After features/support/hooks.rb:108 0.007
Tags: @product
1:41.951
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.768
Then Tails is running from USB drive "old" 0.242
And all tps features are active 4.981
When I write some files expected to persist 1.268
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 2.065
And I take note of which tps features are available 4.529
And I shutdown Tails and wait for the computer to power off 8.273
# 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.177
After features/support/hooks.rb:339 0.459
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.440
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 without a persistent partition and stopped at Tails Greeter's login screen 9.020
And I log in to a new session 13.737
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.803
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.693
Then the running Tails is installed on USB drive "to_upgrade" 14.679
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.793
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.320
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.396
Then all tps features from the old Tails version are active 1.050
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.687
And the expected persistent files created with the old Tails version are present in the filesystem 1.161
And all persistent directories from the old Tails version have safe access rights 1.724
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:55.499
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.372
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.015
And Tor is ready 13.413
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.154
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.889
Given I shutdown Tails and wait for the computer to power off 6.929
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.206
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.895
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.276
When the network is plugged 0.017
And Tor is ready 10.926
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.902
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.911
Given I shutdown Tails and wait for the computer to power off 4.099
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.691
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.319
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.014
And Tor is ready 10.021
Then the Upgrader considers the system as up-to-date 10.540
# 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.206
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:339 1.015
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.474
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 7.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.624
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.339
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.000