Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 104 27 Jun 2025, 20:28

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:50.423 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:47.066
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 43.006
When I start Tails from USB drive "old" with network unplugged 1:58.275
Then the boot device has safe access rights 3.202
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.434
And I unplug USB drive "old" 0.310
After features/support/hooks.rb:335 4.072
After features/support/hooks.rb:105 0.067
Tags: @product
2:57.459
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.031
Given a computer 1.710
And I start Tails from USB drive "old" with network unplugged and I login 1:56.546
Then Tails is running from USB drive "old" 0.465
And I create a persistent partition 41.272
And I take note of which tps features are available 5.931
Then a Tails persistence partition exists on USB drive "old" 2.508
And I shutdown Tails and wait for the computer to power off 9.024
After features/support/hooks.rb:335 0.170
After features/support/hooks.rb:105 0.008
Tags: @product
4:3.223
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:1.644
Then Tails is running from USB drive "old" 2.866
And all tps features are active 5.099
When I write some files expected to persist 2.491
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.346
And all persistence configuration files have safe access rights 0.491
And all persistent directories from the old Tails version have safe access rights 2.433
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 7.565
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 39.557
After features/support/hooks.rb:335 1.061
After features/support/hooks.rb:105 0.046
Tags: @product
3:15.702
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.039
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.454
And I log in to a new session 24.541
And I clone USB drive "old" to a new USB drive "to_upgrade" 9.952
And I plug USB drive "to_upgrade" 2.764
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.047
Then the running Tails is installed on USB drive "to_upgrade" 32.541
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:335 4.501
After features/support/hooks.rb:105 0.000
Tags: @product
3:6.984
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.038
Given a computer 0.507
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:50.038
Then all tps features from the old Tails version are active 1.994
And Tails is running from USB drive "to_upgrade" 0.489
And the boot device has safe access rights 4.094
And the expected persistent files created with the old Tails version are present in the filesystem 6.257
And all persistent directories from the old Tails version have safe access rights 3.603
After features/support/hooks.rb:335 2.058
After features/support/hooks.rb:105 0.011
Tags: @product @automatic_upgrade
8:49.486
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.547
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.626
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.789
When the network is plugged 0.068
And Tor is ready 27.030
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.874
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.996
Given I shutdown Tails and wait for the computer to power off 11.622
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:59.261
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.444
And the file system changes introduced in version 6.2~testoverlayfs are present 0.393
And only the 6.2~testoverlayfs SquashFS delta is installed 0.737
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 1.178
# 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 1.827
When the network is plugged 0.383
And Tor is ready 24.728
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.122
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.641
Given I shutdown Tails and wait for the computer to power off 6.935
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:32.092
Then Tails is running version 6.3~testoverlayfs 0.072
And all tps features are active 3.486
And the file system changes introduced in version 6.3~testoverlayfs are present 0.728
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.346
When the network is plugged 0.087
And Tor is ready 25.627
Then the Upgrader considers the system as up-to-date 0.405
# 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 19.979
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.507
After features/support/hooks.rb:335 6.226
After features/support/hooks.rb:105 0.083
Tags: @product @automatic_upgrade
50.499
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.852
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.563
And the signing key used by the Upgrader is outdated 0.588
But a current signing key is available on our website 0.000
When the network is plugged 0.229
And Tor is ready 27.474
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.315
After features/support/hooks.rb:335 1.114
After features/support/hooks.rb:105 0.000