Project Number Date
test_Tails_ISO_21688-strict-umask 4 25 Jul 2026, 04:47

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:42.928 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.649
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.958
When I start Tails from USB drive "old" with network unplugged 1:4.424
Then the boot device has safe access rights 2.606
And Tails is running from USB drive "old" 0.200
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 3.651
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.959
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 52.673
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 24.451
And I take note of which tps features are available 3.968
Then a Tails persistence partition exists on USB drive "old" 0.543
And I shutdown Tails and wait for the computer to power off 4.009
After features/support/hooks.rb:339 0.376
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.508
Then Tails is running from USB drive "old" 0.266
And all tps features are active 4.859
When I write some files expected to persist 1.175
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.253
And all persistent directories from the old Tails version have safe access rights 1.866
And I take note of which tps features are available 3.597
And I shutdown Tails and wait for the computer to power off 3.951
# 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.061
After features/support/hooks.rb:339 0.520
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.496
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.159
And I log in to a new session 13.802
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.673
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.163
Then the running Tails is installed on USB drive "to_upgrade" 14.167
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:339 2.177
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.011
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.466
Then all tps features from the old Tails version are active 1.034
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.422
And the expected persistent files created with the old Tails version are present in the filesystem 1.019
And all persistent directories from the old Tails version have safe access rights 1.776
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
3:43.286
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.866
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.167
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.340
When the network is plugged 0.015
And Tor is ready 13.051
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.408
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.392
Given I shutdown Tails and wait for the computer to power off 5.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.237
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.694
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.176
When the network is plugged 0.012
And Tor is ready 10.687
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.649
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.817
Given I shutdown Tails and wait for the computer to power off 4.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.402
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.167
And the file system changes introduced in version 6.3~testoverlayfs are present 0.313
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.017
And Tor is ready 11.445
Then the Upgrader considers the system as up-to-date 10.518
# 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.702
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.371
After features/support/hooks.rb:339 0.600
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.752
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.041
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
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.045
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 8.331
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.065
After features/support/hooks.rb:339 1.176
After features/support/hooks.rb:108 0.000