Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 2 28 May 2026, 19:54

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:39.669 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:12.828
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.792
When I start Tails from USB drive "old" with network unplugged 54.033
Then the boot device has safe access rights 3.089
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:335 1.900
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.805
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 54.386
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 26.005
And I take note of which tps features are available 0.384
Then a Tails persistence partition exists on USB drive "old" 0.525
And I shutdown Tails and wait for the computer to power off 8.190
After features/support/hooks.rb:335 0.512
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.269
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.004
Then Tails is running from USB drive "old" 0.235
And all tps features are active 1.262
When I write some files expected to persist 1.259
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 2.197
And I take note of which tps features are available 0.186
And I shutdown Tails and wait for the computer to power off 8.113
# 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.427
After features/support/hooks.rb:335 0.557
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.578
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.676
And I log in to a new session 12.851
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.988
And I plug USB drive "to_upgrade" 2.309
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.355
Then the running Tails is installed on USB drive "to_upgrade" 16.118
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:335 2.311
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.175
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.423
Then all tps features from the old Tails version are active 1.405
And Tails is running from USB drive "to_upgrade" 0.267
And the boot device has safe access rights 2.643
And the expected persistent files created with the old Tails version are present in the filesystem 1.155
And all persistent directories from the old Tails version have safe access rights 2.207
After features/support/hooks.rb:335 0.603
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:37.064
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.196
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.016
And Tor is ready 13.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.027
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.784
Given I shutdown Tails and wait for the computer to power off 8.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.478
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.077
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.199
When the network is plugged 0.019
And Tor is ready 11.353
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.579
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.730
Given I shutdown Tails and wait for the computer to power off 3.972
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.531
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.324
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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.014
And Tor is ready 9.795
Then the Upgrader considers the system as up-to-date 10.681
# 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.686
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:335 0.926
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
29.946
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.537
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.934
After features/support/hooks.rb:335 1.281
After features/support/hooks.rb:104 0.000