Project Number Date
test_Tails_ISO_19913-remove-useless-udevadm-settle 2 11 Aug 2026, 12:08

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:49.861 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:21.283
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.369
When I start Tails from USB drive "old" with network unplugged 1:3.281
Then the boot device has safe access rights 2.814
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.791
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.335
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login 50.025
Then Tails is running from USB drive "old" 0.158
And I create a persistent partition 23.744
And I take note of which tps features are available 6.778
Then a Tails persistence partition exists on USB drive "old" 0.522
And I shutdown Tails and wait for the computer to power off 3.997
After features/support/hooks.rb:339 0.565
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.674
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.160
Then Tails is running from USB drive "old" 0.337
And all tps features are active 8.729
When I write some files expected to persist 1.304
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.122
And all persistence configuration files have safe access rights 0.233
And all persistent directories from the old Tails version have safe access rights 1.601
And I take note of which tps features are available 9.016
And I shutdown Tails and wait for the computer to power off 2.627
# 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.457
After features/support/hooks.rb:339 0.135
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.785
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.531
And I log in to a new session 14.392
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.685
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.330
Then the running Tails is installed on USB drive "to_upgrade" 17.315
And I unplug USB drive "to_upgrade" 0.161
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 2.157
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.866
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.703
Then all tps features from the old Tails version are active 1.130
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.318
And the expected persistent files created with the old Tails version are present in the filesystem 1.091
And all persistent directories from the old Tails version have safe access rights 2.300
After features/support/hooks.rb:339 0.821
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.972
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.462
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.025
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.311
When the network is plugged 0.028
And Tor is ready 12.473
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.726
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.515
Given I shutdown Tails and wait for the computer to power off 5.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.735
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.402
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.151
When the network is plugged 0.037
And Tor is ready 10.543
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.996
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.026
Given I shutdown Tails and wait for the computer to power off 4.145
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.248
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.385
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.111
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.034
And Tor is ready 10.384
Then the Upgrader considers the system as up-to-date 0.113
# 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.654
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.678
After features/support/hooks.rb:339 0.846
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.943
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.243
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 11.207
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.095
After features/support/hooks.rb:339 0.821
After features/support/hooks.rb:108 0.000