Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 47 04 Jul 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 12:9.502 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:22.212
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.600
When I start Tails from USB drive "old" with network unplugged 1:4.137
Then the boot device has safe access rights 2.686
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:339 1.570
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.078
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 54.573
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 25.201
And I take note of which tps features are available 5.241
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 4.220
After features/support/hooks.rb:339 0.322
After features/support/hooks.rb:108 0.007
Tags: @product
1:39.213
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.001
Then Tails is running from USB drive "old" 0.342
And all tps features are active 5.308
When I write some files expected to persist 1.320
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.721
And I take note of which tps features are available 3.827
And I shutdown Tails and wait for the computer to power off 8.073
# 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.128
After features/support/hooks.rb:339 0.147
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.592
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.309
And I log in to a new session 12.786
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.674
And I plug USB drive "to_upgrade" 2.315
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.528
Then the running Tails is installed on USB drive "to_upgrade" 15.691
And I unplug USB drive "to_upgrade" 0.163
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 2.092
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.660
Then all tps features from the old Tails version are active 1.057
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 3.213
And the expected persistent files created with the old Tails version are present in the filesystem 1.215
And all persistent directories from the old Tails version have safe access rights 1.934
After features/support/hooks.rb:339 0.850
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:51.603
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 8.157
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.347
When the network is plugged 0.016
And Tor is ready 13.847
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.735
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.422
Given I shutdown Tails and wait for the computer to power off 6.929
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.792
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.833
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# 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.322
When the network is plugged 0.055
And Tor is ready 11.533
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.428
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.788
Given I shutdown Tails and wait for the computer to power off 4.259
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.483
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 4.970
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.013
And Tor is ready 9.913
Then the Upgrader considers the system as up-to-date 10.532
# 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.093
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:339 0.898
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.427
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.744
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.047
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.364
After features/support/hooks.rb:339 0.854
After features/support/hooks.rb:108 0.000