Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 17 08 Jun 2026, 18: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:33.168 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:13.866
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.919
When I start Tails from USB drive "old" with network unplugged 55.275
Then the boot device has safe access rights 2.883
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 1.537
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.179
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 54.441
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 25.051
And I take note of which tps features are available 0.342
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 8.516
After features/support/hooks.rb:335 0.164
After features/support/hooks.rb:104 0.009
Tags: @product
1:25.913
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.831
Then Tails is running from USB drive "old" 0.299
And all tps features are active 1.217
When I write some files expected to persist 1.211
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.104
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 3.990
# 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.465
After features/support/hooks.rb:335 0.404
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.541
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.701
And I log in to a new session 12.908
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.852
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.671
Then the running Tails is installed on USB drive "to_upgrade" 15.913
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.668
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.418
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.388
Then all tps features from the old Tails version are active 1.064
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.761
And the expected persistent files created with the old Tails version are present in the filesystem 1.056
And all persistent directories from the old Tails version have safe access rights 1.835
After features/support/hooks.rb:335 0.858
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:39.022
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.456
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.015
And Tor is ready 13.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.269
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.880
Given I shutdown Tails and wait for the computer to power off 6.862
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.286
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.497
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.190
When the network is plugged 0.016
And Tor is ready 10.292
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.228
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.586
Given I shutdown Tails and wait for the computer to power off 4.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.435
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.189
And the file system changes introduced in version 6.3~testoverlayfs are present 0.365
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.191
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.014
And Tor is ready 10.231
Then the Upgrader considers the system as up-to-date 10.580
# 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.277
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.424
After features/support/hooks.rb:335 1.007
After features/support/hooks.rb:104 0.026
Tags: @product @automatic_upgrade
21.226
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.674
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.560
After features/support/hooks.rb:335 1.016
After features/support/hooks.rb:104 0.000