Project Number Date
test_Tails_ISO_21688-strict-umask 6 27 Jul 2026, 04:46

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:30.494 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:8.779
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.564
When I start Tails from USB drive "old" with network unplugged 50.729
Then the boot device has safe access rights 2.696
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 3.802
After features/support/hooks.rb:108 0.056
Tags: @product
1:26.966
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 "old" with network unplugged and I login 53.997
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 23.966
And I take note of which tps features are available 4.187
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 3.960
After features/support/hooks.rb:339 0.421
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.165
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.024
Then Tails is running from USB drive "old" 0.232
And all tps features are active 4.818
When I write some files expected to persist 1.367
# 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.306
And all persistent directories from the old Tails version have safe access rights 1.959
And I take note of which tps features are available 3.797
And I shutdown Tails and wait for the computer to power off 4.400
# 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.018
After features/support/hooks.rb:339 0.200
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.473
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 7.864
And I log in to a new session 13.066
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.804
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.172
Then the running Tails is installed on USB drive "to_upgrade" 14.062
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.071
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.726
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.784
Then all tps features from the old Tails version are active 1.022
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.549
And the expected persistent files created with the old Tails version are present in the filesystem 1.204
And all persistent directories from the old Tails version have safe access rights 1.899
After features/support/hooks.rb:339 0.480
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:44.568
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.855
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.014
And Tor is ready 13.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.427
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.627
Given I shutdown Tails and wait for the computer to power off 5.592
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.545
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 4.983
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.198
When the network is plugged 0.015
And Tor is ready 9.969
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.163
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.158
Given I shutdown Tails and wait for the computer to power off 4.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.456
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.760
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.015
And Tor is ready 10.981
Then the Upgrader considers the system as up-to-date 10.506
# 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.208
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:339 0.918
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.815
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.143
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.035
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.216
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.136
After features/support/hooks.rb:339 0.898
After features/support/hooks.rb:108 0.000