Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 34 21 Jun 2026, 20:20

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:44.354 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:11.776
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.022
Given a computer 0.154
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.266
When I start Tails from USB drive "old" with network unplugged 54.076
Then the boot device has safe access rights 2.614
And Tails is running from USB drive "old" 0.193
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.999
After features/support/hooks.rb:108 0.026
Tags: @product
1:30.623
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.025
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 54.438
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 24.137
And I take note of which tps features are available 4.233
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 6.870
After features/support/hooks.rb:339 0.243
After features/support/hooks.rb:108 0.019
Tags: @product
1:37.219
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.135
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.071
Then Tails is running from USB drive "old" 0.199
And all tps features are active 4.817
When I write some files expected to persist 1.362
# 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.333
And all persistent directories from the old Tails version have safe access rights 1.940
And I take note of which tps features are available 3.940
And I shutdown Tails and wait for the computer to power off 8.309
# 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" 11.915
After features/support/hooks.rb:339 0.138
After features/support/hooks.rb:108 0.020
Tags: @product
2:9.950
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.717
And I log in to a new session 13.016
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.745
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.418
Then the running Tails is installed on USB drive "to_upgrade" 13.561
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:339 2.560
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.471
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.057
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.856
Then all tps features from the old Tails version are active 0.978
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.369
And the expected persistent files created with the old Tails version are present in the filesystem 1.077
And all persistent directories from the old Tails version have safe access rights 1.824
After features/support/hooks.rb:339 0.753
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
3:42.381
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.609
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.323
When the network is plugged 0.015
And Tor is ready 12.671
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.806
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.332
Given I shutdown Tails and wait for the computer to power off 5.664
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.250
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.913
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.191
When the network is plugged 0.014
And Tor is ready 9.614
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.669
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.882
Given I shutdown Tails and wait for the computer to power off 4.332
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.801
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.759
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.013
And Tor is ready 10.631
Then the Upgrader considers the system as up-to-date 10.472
# 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.245
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.366
After features/support/hooks.rb:339 0.988
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
20.931
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.012
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.433
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.176
After features/support/hooks.rb:339 0.828
After features/support/hooks.rb:108 0.000