Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 45 02 Jul 2026, 20:12

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:36.811 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:16.064
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 14.371
When I start Tails from USB drive "old" with network unplugged 56.625
Then the boot device has safe access rights 3.170
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.168
After features/support/hooks.rb:339 3.737
After features/support/hooks.rb:108 0.008
Tags: @product
1:35.647
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 57.199
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 24.964
And I take note of which tps features are available 4.018
Then a Tails persistence partition exists on USB drive "old" 0.679
And I shutdown Tails and wait for the computer to power off 8.467
After features/support/hooks.rb:339 0.239
After features/support/hooks.rb:108 0.007
Tags: @product
1:45.709
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.987
Then Tails is running from USB drive "old" 0.341
And all tps features are active 5.750
When I write some files expected to persist 1.685
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.278
And I take note of which tps features are available 4.684
And I shutdown Tails and wait for the computer to power off 8.486
# 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.802
After features/support/hooks.rb:339 0.115
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.002
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 8.080
And I log in to a new session 14.199
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.830
And I plug USB drive "to_upgrade" 2.278
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.024
Then the running Tails is installed on USB drive "to_upgrade" 17.273
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 2.330
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.930
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:9.093
Then all tps features from the old Tails version are active 1.049
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.909
And the expected persistent files created with the old Tails version are present in the filesystem 1.310
And all persistent directories from the old Tails version have safe access rights 2.296
After features/support/hooks.rb:339 0.885
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
4:5.724
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.678
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.027
And Tor is ready 13.149
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.397
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.745
Given I shutdown Tails and wait for the computer to power off 7.400
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.725
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.601
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.181
# 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.305
When the network is plugged 0.016
And Tor is ready 10.266
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.444
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.990
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:10.701
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.956
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.086
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.022
And Tor is ready 11.629
Then the Upgrader considers the system as up-to-date 10.633
# 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.758
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.435
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
21.731
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 7.751
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.112
After features/support/hooks.rb:339 1.031
After features/support/hooks.rb:108 0.000