Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 40 27 Jun 2026, 19:58

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.357 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:9.157
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.133
When I start Tails from USB drive "old" with network unplugged 51.876
Then the boot device has safe access rights 2.471
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.412
After features/support/hooks.rb:108 0.052
Tags: @product
1:30.060
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 53.100
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 24.007
And I take note of which tps features are available 3.983
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 8.142
After features/support/hooks.rb:339 0.342
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.062
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.332
Then Tails is running from USB drive "old" 0.216
And all tps features are active 4.903
When I write some files expected to persist 1.424
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.271
And all persistent directories from the old Tails version have safe access rights 1.888
And I take note of which tps features are available 3.894
And I shutdown Tails and wait for the computer to power off 7.810
# 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.079
After features/support/hooks.rb:339 0.226
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.214
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.096
And I log in to a new session 12.446
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.681
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.266
Then the running Tails is installed on USB drive "to_upgrade" 15.189
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 2.258
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.400
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.848
Then all tps features from the old Tails version are active 0.962
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.343
And the expected persistent files created with the old Tails version are present in the filesystem 1.054
And all persistent directories from the old Tails version have safe access rights 1.911
After features/support/hooks.rb:339 0.844
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:41.169
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.072
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.016
And Tor is ready 12.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.730
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.594
Given I shutdown Tails and wait for the computer to power off 6.849
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.936
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.755
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
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.148
# 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.276
When the network is plugged 0.048
And Tor is ready 10.543
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.247
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.813
Given I shutdown Tails and wait for the computer to power off 3.984
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.770
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.895
And the file system changes introduced in version 6.3~testoverlayfs are present 0.306
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.120
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.013
And Tor is ready 9.868
Then the Upgrader considers the system as up-to-date 10.463
# 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.133
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:339 0.754
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.292
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.281
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
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.057
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.214
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.425
After features/support/hooks.rb:339 0.926
After features/support/hooks.rb:108 0.000