Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 50 07 Jul 2026, 20:09

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 12:4.493 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:22.407
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.705
When I start Tails from USB drive "old" with network unplugged 1:4.043
Then the boot device has safe access rights 2.684
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.370
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:339 1.733
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.014
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 54.158
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 24.951
And I take note of which tps features are available 4.658
Then a Tails persistence partition exists on USB drive "old" 0.608
And I shutdown Tails and wait for the computer to power off 4.328
After features/support/hooks.rb:339 0.401
After features/support/hooks.rb:108 0.007
Tags: @product
1:33.899
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.181
Then Tails is running from USB drive "old" 0.319
And all tps features are active 5.046
When I write some files expected to persist 1.409
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 2.047
And I take note of which tps features are available 4.007
And I shutdown Tails and wait for the computer to power off 3.995
# 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.366
After features/support/hooks.rb:339 0.461
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.619
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.758
And I log in to a new session 13.476
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.792
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.148
Then the running Tails is installed on USB drive "to_upgrade" 14.919
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 3.565
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.738
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.196
Then all tps features from the old Tails version are active 1.012
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.368
And the expected persistent files created with the old Tails version are present in the filesystem 1.135
And all persistent directories from the old Tails version have safe access rights 1.749
After features/support/hooks.rb:339 0.558
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:53.481
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.115
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.017
And Tor is ready 13.576
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.702
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.123
Given I shutdown Tails and wait for the computer to power off 6.914
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.154
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.451
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.203
When the network is plugged 0.014
And Tor is ready 11.186
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.845
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.826
Given I shutdown Tails and wait for the computer to power off 4.247
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.782
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.652
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.016
And Tor is ready 10.078
Then the Upgrader considers the system as up-to-date 10.564
# 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.275
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.385
After features/support/hooks.rb:339 0.883
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.333
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.236
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.137
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.590
After features/support/hooks.rb:339 0.883
After features/support/hooks.rb:108 0.000