Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 38 25 Jun 2026, 20:02

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.035 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:7.595
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.272
When I start Tails from USB drive "old" with network unplugged 50.086
Then the boot device has safe access rights 2.506
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:339 3.509
After features/support/hooks.rb:108 0.027
Tags: @product
1:29.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 53.031
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 24.095
And I take note of which tps features are available 3.990
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 7.835
After features/support/hooks.rb:339 0.629
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.566
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.335
Then Tails is running from USB drive "old" 0.228
And all tps features are active 4.668
When I write some files expected to persist 1.299
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 1.828
And I take note of which tps features are available 3.591
And I shutdown Tails and wait for the computer to power off 8.231
# 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.739
After features/support/hooks.rb:339 0.266
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.932
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 without a persistent partition and stopped at Tails Greeter's login screen 8.369
And I log in to a new session 12.061
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.635
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.370
Then the running Tails is installed on USB drive "to_upgrade" 15.018
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 2.774
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.265
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.871
Then all tps features from the old Tails version are active 0.954
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.296
And the expected persistent files created with the old Tails version are present in the filesystem 1.066
And all persistent directories from the old Tails version have safe access rights 1.783
After features/support/hooks.rb:339 0.969
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:41.982
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.965
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
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.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.391
When the network is plugged 0.018
And Tor is ready 13.169
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.502
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.266
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.283
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.971
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.174
When the network is plugged 0.016
And Tor is ready 9.599
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.641
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.852
Given I shutdown Tails and wait for the computer to power off 4.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.055
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.890
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.049
# 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.161
When the network is plugged 0.013
And Tor is ready 10.917
Then the Upgrader considers the system as up-to-date 10.495
# 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.778
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.319
After features/support/hooks.rb:339 0.916
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.938
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.346
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 8.297
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.971
After features/support/hooks.rb:339 0.819
After features/support/hooks.rb:108 0.000