Project Number Date
test_Tails_ISO_21688-strict-umask 2 23 Jul 2026, 15: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:51.992 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:24.811
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
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" 14.198
When I start Tails from USB drive "old" with network unplugged 1:5.493
Then the boot device has safe access rights 3.303
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 1.552
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.282
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 57.994
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 25.921
And I take note of which tps features are available 4.272
Then a Tails persistence partition exists on USB drive "old" 0.594
And I shutdown Tails and wait for the computer to power off 6.141
After features/support/hooks.rb:339 0.592
After features/support/hooks.rb:108 0.008
Tags: @product
1:42.248
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.595
Then Tails is running from USB drive "old" 0.256
And all tps features are active 5.149
When I write some files expected to persist 1.443
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.341
And all persistence configuration files have safe access rights 0.557
And all persistent directories from the old Tails version have safe access rights 2.322
And I take note of which tps features are available 4.419
And I shutdown Tails and wait for the computer to power off 4.245
# 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.858
After features/support/hooks.rb:339 0.218
After features/support/hooks.rb:108 0.012
Tags: @product
2:18.348
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.068
And I log in to a new session 15.876
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.097
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.332
Then the running Tails is installed on USB drive "to_upgrade" 17.450
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:339 2.876
After features/support/hooks.rb:108 0.000
Tags: @product
1:22.407
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.727
Then all tps features from the old Tails version are active 1.603
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 3.143
And the expected persistent files created with the old Tails version are present in the filesystem 1.381
And all persistent directories from the old Tails version have safe access rights 2.229
After features/support/hooks.rb:339 0.924
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
4:7.030
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.380
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.017
And Tor is ready 14.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.029
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.964
Given I shutdown Tails and wait for the computer to power off 7.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.377
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.825
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
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.138
# 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.226
When the network is plugged 0.026
And Tor is ready 11.271
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.470
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.104
Given I shutdown Tails and wait for the computer to power off 4.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.636
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 5.801
And the file system changes introduced in version 6.3~testoverlayfs are present 0.409
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.023
And Tor is ready 10.995
Then the Upgrader considers the system as up-to-date 10.585
# 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.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.439
After features/support/hooks.rb:339 0.979
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.862
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 8.006
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
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.054
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 10.560
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.910
After features/support/hooks.rb:339 1.189
After features/support/hooks.rb:108 0.000