Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 98 21 Jun 2025, 20:32

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 25:42.575 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
2:44.318
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.028
Given a computer 0.289
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 40.848
When I start Tails from USB drive "old" with network unplugged 1:57.638
Then the boot device has safe access rights 3.239
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.316
After features/support/hooks.rb:335 4.108
After features/support/hooks.rb:105 0.010
Tags: @product
2:56.344
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:53.464
Then Tails is running from USB drive "old" 0.604
And I create a persistent partition 44.600
And I take note of which tps features are available 3.132
Then a Tails persistence partition exists on USB drive "old" 5.036
And I shutdown Tails and wait for the computer to power off 9.312
After features/support/hooks.rb:335 0.176
After features/support/hooks.rb:105 0.010
Tags: @product
3:57.216
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:57.949
Then Tails is running from USB drive "old" 0.841
And all tps features are active 2.412
When I write some files expected to persist 2.278
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.598
And all persistent directories from the old Tails version have safe access rights 8.174
And I take note of which tps features are available 0.585
And I shutdown Tails and wait for the computer to power off 6.401
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.470
After features/support/hooks.rb:335 0.141
After features/support/hooks.rb:105 0.008
Tags: @product
3:18.289
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 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 15.146
And I log in to a new session 25.312
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.632
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.123
Then the running Tails is installed on USB drive "to_upgrade" 38.161
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:335 6.871
After features/support/hooks.rb:105 0.000
Tags: @product
2:52.605
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.010
Given a computer 0.290
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:35.904
Then all tps features from the old Tails version are active 2.080
And Tails is running from USB drive "to_upgrade" 0.561
And the boot device has safe access rights 6.081
And the expected persistent files created with the old Tails version are present in the filesystem 4.188
And all persistent directories from the old Tails version have safe access rights 3.498
After features/support/hooks.rb:335 1.502
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
9:0.571
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.221
And no SquashFS delta is installed 0.292
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.627
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.821
When the network is plugged 0.084
And Tor is ready 29.349
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.105
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.242
Given I shutdown Tails and wait for the computer to power off 11.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:56.899
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.511
And the file system changes introduced in version 6.2~testoverlayfs are present 0.379
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.415
# 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.275
When the network is plugged 0.089
And Tor is ready 27.740
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.031
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.347
Given I shutdown Tails and wait for the computer to power off 6.413
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:37.357
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 2.836
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.365
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.069
And Tor is ready 28.129
Then the Upgrader considers the system as up-to-date 0.603
# 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 25.600
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.835
After features/support/hooks.rb:335 0.721
After features/support/hooks.rb:105 0.021
Tags: @product @automatic_upgrade
53.228
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.658
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.165
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.242
And Tor is ready 23.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.999
After features/support/hooks.rb:335 1.708
After features/support/hooks.rb:105 0.000