Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 22 09 Jun 2026, 19:01

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:38.387 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:15.979
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.596
When I start Tails from USB drive "old" with network unplugged 57.918
Then the boot device has safe access rights 2.716
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:335 3.582
After features/support/hooks.rb:104 0.020
Tags: @product
1:29.431
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 55.922
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 25.522
And I take note of which tps features are available 0.344
Then a Tails persistence partition exists on USB drive "old" 0.515
And I shutdown Tails and wait for the computer to power off 6.825
After features/support/hooks.rb:335 0.448
After features/support/hooks.rb:104 0.008
Tags: @product
1:26.487
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.256
Then Tails is running from USB drive "old" 0.276
And all tps features are active 1.116
When I write some files expected to persist 1.332
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.311
And all persistent directories from the old Tails version have safe access rights 2.205
And I take note of which tps features are available 0.161
And I shutdown Tails and wait for the computer to power off 4.412
# 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.178
After features/support/hooks.rb:335 0.411
After features/support/hooks.rb:104 0.006
Tags: @product
2:13.420
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.603
And I log in to a new session 13.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.822
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.917
Then the running Tails is installed on USB drive "to_upgrade" 16.466
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:335 2.359
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.981
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.068
Then all tps features from the old Tails version are active 0.937
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.473
And the expected persistent files created with the old Tails version are present in the filesystem 1.158
And all persistent directories from the old Tails version have safe access rights 2.032
After features/support/hooks.rb:335 0.751
After features/support/hooks.rb:104 0.017
Tags: @product @automatic_upgrade
3:41.708
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.445
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.015
And Tor is ready 12.582
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.709
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.974
Given I shutdown Tails and wait for the computer to power off 6.690
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.659
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.241
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.338
When the network is plugged 0.052
And Tor is ready 10.170
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.757
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.512
Given I shutdown Tails and wait for the computer to power off 4.210
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.466
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.180
And the file system changes introduced in version 6.3~testoverlayfs are present 0.385
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.014
And Tor is ready 10.603
Then the Upgrader considers the system as up-to-date 10.499
# 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.645
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.659
After features/support/hooks.rb:335 0.784
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
21.377
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 7.635
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 9.773
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.596
After features/support/hooks.rb:335 0.895
After features/support/hooks.rb:104 0.000