Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 15 06 Jun 2026, 19:53

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 10:59.567 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:10.944
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" 12.889
When I start Tails from USB drive "old" with network unplugged 53.552
Then the boot device has safe access rights 2.797
And Tails is running from USB drive "old" 0.217
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:335 1.626
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.745
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 52.114
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 23.703
And I take note of which tps features are available 0.391
Then a Tails persistence partition exists on USB drive "old" 0.540
And I shutdown Tails and wait for the computer to power off 6.713
After features/support/hooks.rb:335 0.572
After features/support/hooks.rb:104 0.006
Tags: @product
1:22.525
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 with persistence enabled 57.529
Then Tails is running from USB drive "old" 0.272
And all tps features are active 1.149
When I write some files expected to persist 1.241
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 1.854
And I take note of which tps features are available 0.138
And I shutdown Tails and wait for the computer to power off 8.103
# 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" 11.668
After features/support/hooks.rb:335 0.302
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.517
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.162
And I log in to a new session 12.385
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.761
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.104
Then the running Tails is installed on USB drive "to_upgrade" 14.590
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:335 2.284
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.124
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:0.220
Then all tps features from the old Tails version are active 0.923
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.559
And the expected persistent files created with the old Tails version are present in the filesystem 1.105
And all persistent directories from the old Tails version have safe access rights 2.052
After features/support/hooks.rb:335 0.619
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:25.693
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.866
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.017
And Tor is ready 12.752
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.693
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.353
Given I shutdown Tails and wait for the computer to power off 6.819
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.843
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.146
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
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.144
# 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.274
When the network is plugged 0.015
And Tor is ready 10.616
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.746
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.732
Given I shutdown Tails and wait for the computer to power off 4.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.212
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 0.982
And the file system changes introduced in version 6.3~testoverlayfs are present 0.320
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.016
And Tor is ready 9.800
Then the Upgrader considers the system as up-to-date 10.520
# 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 3.775
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.312
After features/support/hooks.rb:335 0.750
After features/support/hooks.rb:104 0.024
Tags: @product @automatic_upgrade
20.016
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.534
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.714
After features/support/hooks.rb:335 0.757
After features/support/hooks.rb:104 0.000