Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 59 12 May 2025, 19:29

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:39.240 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:19.075
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.430
When I start Tails from USB drive "old" with network unplugged 1:42.122
Then the boot device has safe access rights 3.188
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:335 3.510
After features/support/hooks.rb:105 0.009
Tags: @product
2:13.256
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:31.227
Then Tails is running from USB drive "old" 0.398
And I create a persistent partition 29.904
And I take note of which tps features are available 2.449
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.311
After features/support/hooks.rb:335 0.199
After features/support/hooks.rb:105 0.007
Tags: @product
2:53.901
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.460
Then Tails is running from USB drive "old" 0.475
And all tps features are active 2.031
When I write some files expected to persist 2.254
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.699
And all persistent directories from the old Tails version have safe access rights 3.186
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.763
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.190
After features/support/hooks.rb:335 0.099
After features/support/hooks.rb:105 0.010
Tags: @product
2:38.553
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.936
And I log in to a new session 20.845
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.919
And I plug USB drive "to_upgrade" 2.541
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.396
Then the running Tails is installed on USB drive "to_upgrade" 27.477
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:335 2.631
After features/support/hooks.rb:105 0.000
Tags: @product
2:27.666
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.956
Then all tps features from the old Tails version are active 1.675
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.473
And the expected persistent files created with the old Tails version are present in the filesystem 1.388
And all persistent directories from the old Tails version have safe access rights 2.604
After features/support/hooks.rb:335 1.367
After features/support/hooks.rb:105 0.007
Tags: @product @automatic_upgrade
7:25.873
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.915
And no SquashFS delta is installed 0.410
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.362
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.191
And Tor is ready 23.318
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.071
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.952
Given I shutdown Tails and wait for the computer to power off 10.777
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.656
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# 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.280
When the network is plugged 0.085
And Tor is ready 49.114
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.631
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.215
Given I shutdown Tails and wait for the computer to power off 6.579
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.650
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.291
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.400
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.083
And Tor is ready 18.434
Then the Upgrader considers the system as up-to-date 11.049
# 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 17.029
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.574
After features/support/hooks.rb:335 0.860
After features/support/hooks.rb:105 0.013
Tags: @product @automatic_upgrade
40.913
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 10.255
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.132
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 23.338
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.571
After features/support/hooks.rb:335 0.777
After features/support/hooks.rb:105 0.000