Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 1 28 May 2026, 16:34

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:43.526 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.720
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.514
When I start Tails from USB drive "old" with network unplugged 55.372
Then the boot device has safe access rights 3.056
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 3.609
After features/support/hooks.rb:104 0.009
Tags: @product
1:29.650
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.127
And I start Tails from USB drive "old" with network unplugged and I login 54.853
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 25.087
And I take note of which tps features are available 0.383
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 8.340
After features/support/hooks.rb:335 0.286
After features/support/hooks.rb:104 0.007
Tags: @product
1:27.957
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.039
Then Tails is running from USB drive "old" 0.341
And all tps features are active 1.614
When I write some files expected to persist 1.514
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.341
And all persistent directories from the old Tails version have safe access rights 2.019
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 8.319
# 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.342
After features/support/hooks.rb:335 0.406
After features/support/hooks.rb:104 0.007
Tags: @product
2:15.095
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.593
And I log in to a new session 14.336
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.784
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.814
Then the running Tails is installed on USB drive "to_upgrade" 16.924
And I unplug USB drive "to_upgrade" 0.170
And I unplug USB drive "__internal" 0.253
After features/support/hooks.rb:335 2.484
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.594
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.922
Then all tps features from the old Tails version are active 1.011
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.846
And the expected persistent files created with the old Tails version are present in the filesystem 1.409
And all persistent directories from the old Tails version have safe access rights 2.088
After features/support/hooks.rb:335 0.709
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:42.254
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.586
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.020
And Tor is ready 14.269
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.110
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.086
Given I shutdown Tails and wait for the computer to power off 6.896
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.461
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.362
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.260
When the network is plugged 0.038
And Tor is ready 11.120
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.716
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.842
Given I shutdown Tails and wait for the computer to power off 4.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.527
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.217
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.016
And Tor is ready 11.576
Then the Upgrader considers the system as up-to-date 10.569
# 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.594
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.488
After features/support/hooks.rb:335 0.744
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
21.254
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 7.801
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.306
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.795
After features/support/hooks.rb:335 1.024
After features/support/hooks.rb:104 0.000