Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 106 29 Jun 2025, 20:07

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 26:20.931 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:46.120
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 43.017
When I start Tails from USB drive "old" with network unplugged 1:56.937
Then the boot device has safe access rights 3.804
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:335 6.022
After features/support/hooks.rb:105 0.017
Tags: @product
2:58.957
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Given a computer 0.413
And I start Tails from USB drive "old" with network unplugged and I login 1:54.674
Then Tails is running from USB drive "old" 1.676
And I create a persistent partition 48.947
And I take note of which tps features are available 2.283
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 10.173
After features/support/hooks.rb:335 0.470
After features/support/hooks.rb:105 0.047
Tags: @product
4:4.814
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.025
Given a computer 0.406
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:5.012
Then Tails is running from USB drive "old" 0.560
And all tps features are active 2.113
When I write some files expected to persist 1.685
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 3.249
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 9.397
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 41.278
After features/support/hooks.rb:335 0.142
After features/support/hooks.rb:105 0.010
Tags: @product
3:16.697
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.195
And I log in to a new session 31.023
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.379
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.607
Then the running Tails is installed on USB drive "to_upgrade" 34.564
And I unplug USB drive "to_upgrade" 2.284
And I unplug USB drive "__internal" 1.193
After features/support/hooks.rb:335 2.324
After features/support/hooks.rb:105 0.000
Tags: @product
3:6.132
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.336
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:49.553
Then all tps features from the old Tails version are active 6.782
And Tails is running from USB drive "to_upgrade" 0.693
And the boot device has safe access rights 4.648
And the expected persistent files created with the old Tails version are present in the filesystem 1.542
And all persistent directories from the old Tails version have safe access rights 2.575
After features/support/hooks.rb:335 1.798
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
8:55.182
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.956
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.577
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.199
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.984
When the network is plugged 0.111
And Tor is ready 28.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.066
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.419
Given I shutdown Tails and wait for the computer to power off 13.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:44.317
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.605
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.285
When the network is plugged 0.065
And Tor is ready 28.086
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.444
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.376
Given I shutdown Tails and wait for the computer to power off 8.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:41.342
Then Tails is running version 6.3~testoverlayfs 0.070
And all tps features are active 3.319
And the file system changes introduced in version 6.3~testoverlayfs are present 0.670
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.353
When the network is plugged 0.091
And Tor is ready 28.100
Then the Upgrader considers the system as up-to-date 0.374
# 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 22.833
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.741
After features/support/hooks.rb:335 0.889
After features/support/hooks.rb:105 0.061
Tags: @product @automatic_upgrade
1:13.025
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 with a persistent partition enabled and logged in 14.685
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.082
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.136
And the signing key used by the Upgrader is outdated 0.259
But a current signing key is available on our website 0.000
When the network is plugged 0.131
And Tor is ready 54.777
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.952
After features/support/hooks.rb:335 1.038
After features/support/hooks.rb:105 0.000