Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 12 03 Jun 2026, 19:55

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:23.124 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:18.954
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
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.008
When I start Tails from USB drive "old" with network unplugged 1:1.407
Then the boot device has safe access rights 2.739
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:335 3.650
After features/support/hooks.rb:104 0.009
Tags: @product
1:26.355
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 52.498
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 24.319
And I take note of which tps features are available 0.435
Then a Tails persistence partition exists on USB drive "old" 0.549
And I shutdown Tails and wait for the computer to power off 8.249
After features/support/hooks.rb:335 0.524
After features/support/hooks.rb:104 0.007
Tags: @product
1:26.486
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.929
Then Tails is running from USB drive "old" 0.273
And all tps features are active 1.240
When I write some files expected to persist 1.188
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 2.127
And I take note of which tps features are available 0.136
And I shutdown Tails and wait for the computer to power off 8.016
# 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.055
After features/support/hooks.rb:335 0.349
After features/support/hooks.rb:104 0.008
Tags: @product
2:10.432
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.492
And I log in to a new session 12.462
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.888
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.111
Then the running Tails is installed on USB drive "to_upgrade" 14.996
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:335 2.214
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.935
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.723
Then all tps features from the old Tails version are active 0.968
And Tails is running from USB drive "to_upgrade" 0.274
And the boot device has safe access rights 2.482
And the expected persistent files created with the old Tails version are present in the filesystem 1.291
And all persistent directories from the old Tails version have safe access rights 2.141
After features/support/hooks.rb:335 0.814
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:32.850
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.011
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.014
And Tor is ready 13.402
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.379
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.617
Given I shutdown Tails and wait for the computer to power off 7.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.521
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.198
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.181
When the network is plugged 0.043
And Tor is ready 9.657
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.819
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.414
Given I shutdown Tails and wait for the computer to power off 3.991
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.599
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.171
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.174
When the network is plugged 0.015
And Tor is ready 11.627
Then the Upgrader considers the system as up-to-date 10.567
# 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.166
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.350
After features/support/hooks.rb:335 1.075
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.109
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 with a persistent partition enabled and logged in 7.651
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
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.036
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.431
After features/support/hooks.rb:335 0.639
After features/support/hooks.rb:104 0.000