Project Number Date
test_Tails_ISO_21674-fix-tbb-shared-libs-test 3 13 Jul 2026, 19: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 13:6.604 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:27.582
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.016
And I write an old version of the Tails USB image to disk "old" 14.835
When I start Tails from USB drive "old" with network unplugged 1:7.753
Then the boot device has safe access rights 3.074
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:339 1.757
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.075
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 58.603
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 26.361
And I take note of which tps features are available 5.089
Then a Tails persistence partition exists on USB drive "old" 0.591
And I shutdown Tails and wait for the computer to power off 7.011
After features/support/hooks.rb:339 0.413
After features/support/hooks.rb:108 0.007
Tags: @product
1:43.356
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.491
Then Tails is running from USB drive "old" 0.228
And all tps features are active 4.945
When I write some files expected to persist 1.462
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 2.239
And I take note of which tps features are available 4.462
And I shutdown Tails and wait for the computer to power off 6.888
# 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.951
After features/support/hooks.rb:339 0.545
After features/support/hooks.rb:108 0.008
Tags: @product
2:17.465
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 9.314
And I log in to a new session 14.738
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.079
And I plug USB drive "to_upgrade" 2.280
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.426
Then the running Tails is installed on USB drive "to_upgrade" 17.281
And I unplug USB drive "to_upgrade" 0.177
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:339 4.056
After features/support/hooks.rb:108 0.000
Tags: @product
1:22.058
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.698
Then all tps features from the old Tails version are active 1.243
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 3.249
And the expected persistent files created with the old Tails version are present in the filesystem 1.286
And all persistent directories from the old Tails version have safe access rights 2.278
After features/support/hooks.rb:339 0.816
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:16.608
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 8.735
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.379
When the network is plugged 0.019
And Tor is ready 13.916
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.566
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.413
Given I shutdown Tails and wait for the computer to power off 10.095
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.336
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.934
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.225
When the network is plugged 0.019
And Tor is ready 11.406
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.793
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.715
Given I shutdown Tails and wait for the computer to power off 8.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.195
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.370
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.016
And Tor is ready 11.276
Then the Upgrader considers the system as up-to-date 10.875
# 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 5.428
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:339 0.945
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.458
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.858
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.360
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.815
After features/support/hooks.rb:339 0.829
After features/support/hooks.rb:108 0.000