Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 29 15 Jun 2026, 20:07

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:26.813 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:4.869
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 12.871
When I start Tails from USB drive "old" with network unplugged 47.742
Then the boot device has safe access rights 2.431
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.084
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.404
After features/support/hooks.rb:108 0.016
Tags: @product
1:25.645
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.147
And I start Tails from USB drive "old" with network unplugged and I login 52.470
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 23.938
And I take note of which tps features are available 3.985
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 4.350
After features/support/hooks.rb:339 0.205
After features/support/hooks.rb:108 0.016
Tags: @product
1:31.711
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.136
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.435
Then Tails is running from USB drive "old" 0.239
And all tps features are active 4.702
When I write some files expected to persist 1.198
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.882
And I take note of which tps features are available 3.678
And I shutdown Tails and wait for the computer to power off 4.435
# 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.557
After features/support/hooks.rb:339 0.107
After features/support/hooks.rb:108 0.016
Tags: @product
2:9.357
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.965
And I log in to a new session 12.503
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.749
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.121
Then the running Tails is installed on USB drive "to_upgrade" 14.443
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:339 2.041
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.786
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.347
Then all tps features from the old Tails version are active 0.896
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.355
And the expected persistent files created with the old Tails version are present in the filesystem 1.058
And all persistent directories from the old Tails version have safe access rights 1.817
After features/support/hooks.rb:339 0.928
After features/support/hooks.rb:108 0.015
3:45.401
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 8.431
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.021
And Tor is ready 12.193
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.483
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.297
Given I shutdown Tails and wait for the computer to power off 6.832
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.374
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.679
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.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.212
When the network is plugged 0.014
And Tor is ready 10.523
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.761
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.859
Given I shutdown Tails and wait for the computer to power off 4.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.333
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.849
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.019
And Tor is ready 9.634
Then the Upgrader considers the system as up-to-date 10.560
# 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.295
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.408
After features/support/hooks.rb:339 0.917
After features/support/hooks.rb:108 0.029
19.040
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.561
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.045
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.356
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.792
After features/support/hooks.rb:339 0.720
After features/support/hooks.rb:108 0.000