Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 41 28 Jun 2026, 20:03

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:32.455 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:6.949
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.177
When I start Tails from USB drive "old" with network unplugged 49.396
Then the boot device has safe access rights 2.611
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.423
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.244
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 52.333
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 23.907
And I take note of which tps features are available 3.856
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 4.358
After features/support/hooks.rb:339 0.629
After features/support/hooks.rb:108 0.007
Tags: @product
1:35.311
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.248
Then Tails is running from USB drive "old" 0.249
And all tps features are active 4.490
When I write some files expected to persist 1.168
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.320
And all persistent directories from the old Tails version have safe access rights 1.837
And I take note of which tps features are available 3.711
And I shutdown Tails and wait for the computer to power off 8.331
# 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.720
After features/support/hooks.rb:339 0.517
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.994
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.525
And I log in to a new session 12.660
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.812
And I plug USB drive "to_upgrade" 2.286
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.409
Then the running Tails is installed on USB drive "to_upgrade" 15.039
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.225
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.873
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.030
Then all tps features from the old Tails version are active 0.997
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.654
And the expected persistent files created with the old Tails version are present in the filesystem 1.222
And all persistent directories from the old Tails version have safe access rights 1.690
After features/support/hooks.rb:339 0.825
After features/support/hooks.rb:108 0.031
Tags: @product @automatic_upgrade
3:43.414
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.924
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.181
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.014
And Tor is ready 12.432
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.900
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.052
Given I shutdown Tails and wait for the computer to power off 6.711
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.759
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.889
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.197
When the network is plugged 0.016
And Tor is ready 11.376
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.510
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.278
Given I shutdown Tails and wait for the computer to power off 4.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.813
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.949
And the file system changes introduced in version 6.3~testoverlayfs are present 0.282
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.016
And Tor is ready 10.227
Then the Upgrader considers the system as up-to-date 10.519
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:339 1.035
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
19.667
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.276
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 8.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.745
After features/support/hooks.rb:339 0.566
After features/support/hooks.rb:108 0.000