Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 42 29 Jun 2026, 20:04

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:0.226 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.934
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.466
When I start Tails from USB drive "old" with network unplugged 56.014
Then the boot device has safe access rights 2.688
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.560
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.159
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 53.766
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 26.353
And I take note of which tps features are available 4.973
Then a Tails persistence partition exists on USB drive "old" 0.583
And I shutdown Tails and wait for the computer to power off 8.074
After features/support/hooks.rb:339 0.414
After features/support/hooks.rb:108 0.005
Tags: @product
1:38.103
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.263
Then Tails is running from USB drive "old" 0.250
And all tps features are active 5.574
When I write some files expected to persist 1.385
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 1.884
And I take note of which tps features are available 3.839
And I shutdown Tails and wait for the computer to power off 7.959
# 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.319
After features/support/hooks.rb:339 0.260
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.963
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 7.969
And I log in to a new session 13.292
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.562
Then the running Tails is installed on USB drive "to_upgrade" 14.829
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:339 1.278
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.694
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.160
Then all tps features from the old Tails version are active 0.928
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.326
And the expected persistent files created with the old Tails version are present in the filesystem 1.170
And all persistent directories from the old Tails version have safe access rights 1.831
After features/support/hooks.rb:339 0.647
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
3:49.718
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.423
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
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.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.023
And Tor is ready 12.363
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.837
Given I shutdown Tails and wait for the computer to power off 6.812
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.564
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.016
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
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.132
# 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.297
When the network is plugged 0.015
And Tor is ready 9.647
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.600
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.394
Given I shutdown Tails and wait for the computer to power off 4.110
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.974
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.254
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.015
And Tor is ready 10.014
Then the Upgrader considers the system as up-to-date 10.575
# 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.371
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.429
After features/support/hooks.rb:339 0.749
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.652
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.273
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.342
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.000