Project Number Date
test_Tails_ISO_19913-remove-useless-udevadm-settle 1 10 Aug 2026, 16:23

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:24.967 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:16.900
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.216
When I start Tails from USB drive "old" with network unplugged 59.861
Then the boot device has safe access rights 2.155
And Tails is running from USB drive "old" 0.174
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.631
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.888
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 47.903
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 23.397
And I take note of which tps features are available 6.139
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 2.574
After features/support/hooks.rb:339 0.413
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.220
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.678
Then Tails is running from USB drive "old" 0.185
And all tps features are active 6.866
When I write some files expected to persist 1.449
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.261
And all persistent directories from the old Tails version have safe access rights 1.726
And I take note of which tps features are available 5.996
And I shutdown Tails and wait for the computer to power off 2.544
# 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.233
After features/support/hooks.rb:339 0.118
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.461
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.427
And I log in to a new session 11.684
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.639
And I plug USB drive "to_upgrade" 2.291
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.793
Then the running Tails is installed on USB drive "to_upgrade" 17.372
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 2.284
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.912
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.624
Then all tps features from the old Tails version are active 1.133
And Tails is running from USB drive "to_upgrade" 0.173
And the boot device has safe access rights 2.257
And the expected persistent files created with the old Tails version are present in the filesystem 1.099
And all persistent directories from the old Tails version have safe access rights 1.548
After features/support/hooks.rb:339 0.738
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:38.819
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 7.942
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.174
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.326
When the network is plugged 0.026
And Tor is ready 12.895
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.531
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.719
Given I shutdown Tails and wait for the computer to power off 5.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.434
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.669
And the file system changes introduced in version 6.2~testoverlayfs are present 0.166
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.154
When the network is plugged 0.025
And Tor is ready 10.537
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.984
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.730
Given I shutdown Tails and wait for the computer to power off 2.650
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.035
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.640
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.106
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.142
When the network is plugged 0.028
And Tor is ready 10.313
Then the Upgrader considers the system as up-to-date 10.399
# 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.646
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.311
After features/support/hooks.rb:339 0.951
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.764
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.821
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.039
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.586
After features/support/hooks.rb:339 0.918
After features/support/hooks.rb:108 0.000