Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 9 02 Jun 2026, 20:07

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:32.949 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.975
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.825
When I start Tails from USB drive "old" with network unplugged 1:6.411
Then the boot device has safe access rights 2.968
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:335 1.833
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.607
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 56.220
Then Tails is running from USB drive "old" 0.269
And I create a persistent partition 25.782
And I take note of which tps features are available 0.388
Then a Tails persistence partition exists on USB drive "old" 0.613
And I shutdown Tails and wait for the computer to power off 8.247
After features/support/hooks.rb:335 0.272
After features/support/hooks.rb:104 0.007
Tags: @product
1:30.730
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:4.568
Then Tails is running from USB drive "old" 0.289
And all tps features are active 1.085
When I write some files expected to persist 1.720
# 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.305
And all persistent directories from the old Tails version have safe access rights 1.955
And I take note of which tps features are available 0.170
And I shutdown Tails and wait for the computer to power off 8.239
# 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.160
After features/support/hooks.rb:335 0.101
After features/support/hooks.rb:104 0.007
Tags: @product
2:9.548
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.417
And I log in to a new session 12.040
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.835
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.254
Then the running Tails is installed on USB drive "to_upgrade" 14.509
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:335 2.450
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.373
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.276
Then all tps features from the old Tails version are active 0.977
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.567
And the expected persistent files created with the old Tails version are present in the filesystem 1.247
And all persistent directories from the old Tails version have safe access rights 1.981
After features/support/hooks.rb:335 0.897
After features/support/hooks.rb:104 0.048
3:28.727
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 8.113
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.333
When the network is plugged 0.013
And Tor is ready 13.229
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.431
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.048
Given I shutdown Tails and wait for the computer to power off 6.726
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.684
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.113
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
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.138
# 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.019
And Tor is ready 9.711
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.248
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.395
Given I shutdown Tails and wait for the computer to power off 4.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.989
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.049
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.014
And Tor is ready 10.550
Then the Upgrader considers the system as up-to-date 10.517
# 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.218
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:335 0.679
After features/support/hooks.rb:104 0.010
19.986
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.432
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.764
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.418
After features/support/hooks.rb:335 0.781
After features/support/hooks.rb:104 0.000