Project Number Date
test_Tails_ISO_21688-strict-umask 5 26 Jul 2026, 04: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:37.942 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:22.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.523
When I start Tails from USB drive "old" with network unplugged 1:3.039
Then the boot device has safe access rights 2.708
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:339 3.694
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.279
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 59.910
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 26.227
And I take note of which tps features are available 4.907
Then a Tails persistence partition exists on USB drive "old" 0.715
And I shutdown Tails and wait for the computer to power off 4.126
After features/support/hooks.rb:339 0.158
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.314
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.451
Then Tails is running from USB drive "old" 0.361
And all tps features are active 6.099
When I write some files expected to persist 1.409
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.942
And I take note of which tps features are available 4.239
And I shutdown Tails and wait for the computer to power off 4.582
# 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.669
After features/support/hooks.rb:339 0.517
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.985
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 without a persistent partition and stopped at Tails Greeter's login screen 8.462
And I log in to a new session 13.690
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.865
And I plug USB drive "to_upgrade" 2.306
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.356
Then the running Tails is installed on USB drive "to_upgrade" 16.017
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:339 2.116
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.167
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.052
Then all tps features from the old Tails version are active 1.206
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.974
And the expected persistent files created with the old Tails version are present in the filesystem 1.368
And all persistent directories from the old Tails version have safe access rights 2.261
After features/support/hooks.rb:339 0.620
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
4:4.268
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 with a persistent partition enabled and logged in 7.888
And no SquashFS delta is installed 0.163
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.580
When the network is plugged 0.028
And Tor is ready 12.792
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.712
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.748
Given I shutdown Tails and wait for the computer to power off 7.084
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.210
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 6.004
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.266
When the network is plugged 0.018
And Tor is ready 12.262
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.868
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.856
Given I shutdown Tails and wait for the computer to power off 4.038
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.035
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.817
And the file system changes introduced in version 6.3~testoverlayfs are present 0.419
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.014
And Tor is ready 10.332
Then the Upgrader considers the system as up-to-date 10.599
# 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.221
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.535
After features/support/hooks.rb:339 0.776
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
20.809
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.440
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
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.018
And Tor is ready 10.153
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.717
After features/support/hooks.rb:339 0.961
After features/support/hooks.rb:108 0.000