Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 61 14 May 2025, 18:30

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 19:4.511 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:3.406
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 31.136
When I start Tails from USB drive "old" with network unplugged 1:27.007
Then the boot device has safe access rights 2.968
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:335 3.483
After features/support/hooks.rb:105 0.008
Tags: @product
2:4.638
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:22.918
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 30.747
And I take note of which tps features are available 1.649
Then a Tails persistence partition exists on USB drive "old" 0.716
And I shutdown Tails and wait for the computer to power off 8.125
After features/support/hooks.rb:335 0.159
After features/support/hooks.rb:105 0.008
Tags: @product
2:45.125
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.085
Then Tails is running from USB drive "old" 0.360
And all tps features are active 1.924
When I write some files expected to persist 1.798
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.587
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.293
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.726
After features/support/hooks.rb:335 0.136
After features/support/hooks.rb:105 0.008
Tags: @product
2:32.617
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 11.412
And I log in to a new session 19.224
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.655
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.494
Then the running Tails is installed on USB drive "to_upgrade" 24.947
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:335 2.106
After features/support/hooks.rb:105 0.000
Tags: @product
2:24.774
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.112
Then all tps features from the old Tails version are active 1.589
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.070
And the expected persistent files created with the old Tails version are present in the filesystem 1.932
And all persistent directories from the old Tails version have safe access rights 2.541
After features/support/hooks.rb:335 1.557
After features/support/hooks.rb:105 0.019
Tags: @product @automatic_upgrade
6:31.763
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 12.515
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.530
When the network is plugged 0.069
And Tor is ready 19.272
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.572
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.636
Given I shutdown Tails and wait for the computer to power off 8.229
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.788
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# 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.271
When the network is plugged 0.064
And Tor is ready 18.590
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.003
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.677
Given I shutdown Tails and wait for the computer to power off 9.056
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.155
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.276
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.120
And Tor is ready 17.891
Then the Upgrader considers the system as up-to-date 0.343
# 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 15.598
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.842
After features/support/hooks.rb:335 0.814
After features/support/hooks.rb:105 0.017
Tags: @product @automatic_upgrade
42.184
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 10.339
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 22.227
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.080
After features/support/hooks.rb:335 1.037
After features/support/hooks.rb:105 0.000