Project Number Date
test_Tails_ISO_21733-dont-confirm-shutdown-unless-inhibited 1 08 Sep 2026, 12:34

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:10.232 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:10.934
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 14.140
When I start Tails from USB drive "old" with network unplugged 52.375
Then the boot device has safe access rights 2.567
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 1.170
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.341
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 50.840
Then Tails is running from USB drive "old" 0.204
And I create a persistent partition 24.124
And I take note of which tps features are available 6.653
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 3.917
After features/support/hooks.rb:339 0.503
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.076
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.728
Then Tails is running from USB drive "old" 0.224
And all tps features are active 8.178
When I write some files expected to persist 1.121
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.805
And I take note of which tps features are available 6.483
And I shutdown Tails and wait for the computer to power off 2.590
# 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.415
After features/support/hooks.rb:339 0.280
After features/support/hooks.rb:108 0.006
Tags: @product
2:29.842
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 without a persistent partition and stopped at Tails Greeter's login screen 23.354
And I log in to a new session 12.433
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.743
And I plug USB drive "to_upgrade" 2.300
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.816
Then the running Tails is installed on USB drive "to_upgrade" 18.929
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 1.858
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.702
Then all tps features from the old Tails version are active 1.050
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.253
And the expected persistent files created with the old Tails version are present in the filesystem 0.955
And all persistent directories from the old Tails version have safe access rights 1.700
After features/support/hooks.rb:339 0.698
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:54.165
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 with a persistent partition enabled and logged in 8.621
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.031
And Tor is ready 11.818
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.755
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.429
Given I shutdown Tails and wait for the computer to power off 5.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.974
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.895
And the file system changes introduced in version 6.2~testoverlayfs are present 0.189
And only the 6.2~testoverlayfs SquashFS delta is installed 0.029
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.192
When the network is plugged 0.040
And Tor is ready 10.667
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.994
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.276
Given I shutdown Tails and wait for the computer to power off 4.232
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.151
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.540
And the file system changes introduced in version 6.3~testoverlayfs are present 0.410
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.033
And Tor is ready 10.693
Then the Upgrader considers the system as up-to-date 10.483
# 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 3.509
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.339
After features/support/hooks.rb:339 0.817
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
19.829
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.254
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.022
After features/support/hooks.rb:339 0.883
After features/support/hooks.rb:108 0.000