Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 68 20 Jun 2026, 14:52

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:3.599 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:11.364
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.113
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.843
When I start Tails from USB drive "old" with network unplugged 52.643
Then the boot device has safe access rights 2.886
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 3.743
After features/support/hooks.rb:108 0.042
Tags: @product
1:33.547
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.145
And I start Tails from USB drive "old" with network unplugged and I login 55.651
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 25.744
And I take note of which tps features are available 4.171
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 7.002
After features/support/hooks.rb:339 0.346
After features/support/hooks.rb:108 0.017
Tags: @product
1:37.172
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.149
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.730
Then Tails is running from USB drive "old" 0.239
And all tps features are active 4.937
When I write some files expected to persist 1.331
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.344
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.087
And I take note of which tps features are available 4.273
And I shutdown Tails and wait for the computer to power off 4.133
# 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.504
After features/support/hooks.rb:339 0.185
After features/support/hooks.rb:108 0.042
Tags: @product
2:11.600
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.396
And I log in to a new session 13.515
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.833
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.674
Then the running Tails is installed on USB drive "to_upgrade" 14.619
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:339 2.194
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.381
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.119
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.120
Then all tps features from the old Tails version are active 1.119
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.693
And the expected persistent files created with the old Tails version are present in the filesystem 1.230
And all persistent directories from the old Tails version have safe access rights 1.845
After features/support/hooks.rb:339 0.841
After features/support/hooks.rb:108 0.017
3:54.588
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.181
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.014
And Tor is ready 13.568
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.905
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.885
Given I shutdown Tails and wait for the computer to power off 9.741
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.490
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.086
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.253
When the network is plugged 0.033
And Tor is ready 9.731
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.661
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.146
Given I shutdown Tails and wait for the computer to power off 4.498
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.912
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.421
And the file system changes introduced in version 6.3~testoverlayfs are present 0.356
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.017
And Tor is ready 10.114
Then the Upgrader considers the system as up-to-date 10.682
# 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.412
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.395
After features/support/hooks.rb:339 0.924
After features/support/hooks.rb:108 0.068
20.943
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.897
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
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.035
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.855
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.789
After features/support/hooks.rb:339 0.804
After features/support/hooks.rb:108 0.000