Project Number Date
test_Tails_ISO_21691-gitlab-triage-use-trusted-image 6 25 Jul 2026, 21:22

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.822 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.784
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.113
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.644
When I start Tails from USB drive "old" with network unplugged 53.789
Then the boot device has safe access rights 2.538
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.838
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.058
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 56.573
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 25.698
And I take note of which tps features are available 4.699
Then a Tails persistence partition exists on USB drive "old" 0.628
And I shutdown Tails and wait for the computer to power off 4.172
After features/support/hooks.rb:339 0.416
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.159
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.465
Then Tails is running from USB drive "old" 0.247
And all tps features are active 5.825
When I write some files expected to persist 1.464
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.336
And all persistent directories from the old Tails version have safe access rights 1.931
And I take note of which tps features are available 4.191
And I shutdown Tails and wait for the computer to power off 2.639
# 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.822
After features/support/hooks.rb:339 0.206
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.418
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 without a persistent partition and stopped at Tails Greeter's login screen 8.324
And I log in to a new session 14.405
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.744
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.079
Then the running Tails is installed on USB drive "to_upgrade" 15.360
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 2.667
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.791
Then all tps features from the old Tails version are active 1.062
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.547
And the expected persistent files created with the old Tails version are present in the filesystem 1.207
And all persistent directories from the old Tails version have safe access rights 1.965
After features/support/hooks.rb:339 0.909
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:54.219
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.286
And no SquashFS delta is installed 0.114
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.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.379
When the network is plugged 0.013
And Tor is ready 12.360
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.723
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.018
Given I shutdown Tails and wait for the computer to power off 7.048
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.525
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.040
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.225
When the network is plugged 0.012
And Tor is ready 10.497
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.554
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.610
Given I shutdown Tails and wait for the computer to power off 4.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.399
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.367
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.014
And Tor is ready 9.795
Then the Upgrader considers the system as up-to-date 10.618
# 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.313
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:339 0.674
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
21.331
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 with a persistent partition enabled and logged in 7.569
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
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.042
And Tor is ready 10.398
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.934
After features/support/hooks.rb:339 0.897
After features/support/hooks.rb:108 0.000