Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 76 28 May 2025, 19:24

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 20:12.135 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:16.485
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.019
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 30.253
When I start Tails from USB drive "old" with network unplugged 1:40.851
Then the boot device has safe access rights 3.078
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:335 3.707
After features/support/hooks.rb:105 0.011
Tags: @product
2:11.791
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:28.592
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 31.491
And I take note of which tps features are available 1.889
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.395
After features/support/hooks.rb:335 0.205
After features/support/hooks.rb:105 0.016
Tags: @product
2:56.695
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.013
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.749
Then Tails is running from USB drive "old" 0.383
And all tps features are active 2.368
When I write some files expected to persist 1.818
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.485
And all persistent directories from the old Tails version have safe access rights 2.876
And I take note of which tps features are available 0.522
And I shutdown Tails and wait for the computer to power off 4.541
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.466
After features/support/hooks.rb:335 0.126
After features/support/hooks.rb:105 0.010
Tags: @product
2:37.743
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 without a persistent partition and stopped at Tails Greeter's login screen 10.423
And I log in to a new session 20.128
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.570
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.099
Then the running Tails is installed on USB drive "to_upgrade" 27.659
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:335 2.137
After features/support/hooks.rb:105 0.000
Tags: @product
2:25.844
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.319
Then all tps features from the old Tails version are active 1.778
And Tails is running from USB drive "to_upgrade" 0.408
And the boot device has safe access rights 4.699
And the expected persistent files created with the old Tails version are present in the filesystem 1.662
And all persistent directories from the old Tails version have safe access rights 2.775
After features/support/hooks.rb:335 1.463
After features/support/hooks.rb:105 0.013
7:3.288
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.198
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.570
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.574
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.593
When the network is plugged 0.116
And Tor is ready 24.468
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.285
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.934
Given I shutdown Tails and wait for the computer to power off 13.488
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.473
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.360
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.310
When the network is plugged 0.471
And Tor is ready 18.578
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.174
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.575
Given I shutdown Tails and wait for the computer to power off 4.445
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.513
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.439
And the file system changes introduced in version 6.3~testoverlayfs are present 0.602
And only the 6.3~testoverlayfs SquashFS delta is installed 0.096
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.072
And Tor is ready 18.571
Then the Upgrader considers the system as up-to-date 0.337
# 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 16.603
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.795
After features/support/hooks.rb:335 0.991
After features/support/hooks.rb:105 0.023
40.286
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.259
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.534
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.100
But a current signing key is available on our website 0.000
When the network is plugged 0.177
And Tor is ready 21.154
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.010
After features/support/hooks.rb:335 1.467
After features/support/hooks.rb:105 0.000