Project Number Date
test_Tails_ISO_21688-strict-umask 3 24 Jul 2026, 05:06

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:3.267 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:15.896
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.898
When I start Tails from USB drive "old" with network unplugged 57.680
Then the boot device has safe access rights 2.517
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.437
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.665
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 55.360
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 25.555
And I take note of which tps features are available 4.710
Then a Tails persistence partition exists on USB drive "old" 0.611
And I shutdown Tails and wait for the computer to power off 4.145
After features/support/hooks.rb:339 0.216
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.989
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.509
Then Tails is running from USB drive "old" 0.223
And all tps features are active 4.653
When I write some files expected to persist 1.194
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.272
And all persistent directories from the old Tails version have safe access rights 2.087
And I take note of which tps features are available 4.189
And I shutdown Tails and wait for the computer to power off 4.142
# 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.519
After features/support/hooks.rb:339 0.380
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.805
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.143
And I log in to a new session 13.547
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.759
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.796
Then the running Tails is installed on USB drive "to_upgrade" 16.027
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.164
After features/support/hooks.rb:339 2.535
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.139
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.091
Then all tps features from the old Tails version are active 1.121
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.627
And the expected persistent files created with the old Tails version are present in the filesystem 1.192
And all persistent directories from the old Tails version have safe access rights 1.825
After features/support/hooks.rb:339 0.637
After features/support/hooks.rb:108 0.044
Tags: @product @automatic_upgrade
3:52.163
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.989
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.019
And Tor is ready 13.383
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.114
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.146
Given I shutdown Tails and wait for the computer to power off 6.952
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.288
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.150
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.214
When the network is plugged 0.015
And Tor is ready 11.041
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.203
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.595
Given I shutdown Tails and wait for the computer to power off 4.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.547
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 5.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.017
And Tor is ready 11.512
Then the Upgrader considers the system as up-to-date 10.587
# 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.428
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:339 0.911
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
20.606
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.345
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.214
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.722
After features/support/hooks.rb:339 0.866
After features/support/hooks.rb:108 0.000