Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 70 23 May 2025, 18:53

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 21:55.519 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:28.988
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 1.099
And I create a 7200 MiB disk named "old" 0.402
And I plug USB drive "old" 1.239
And I write an old version of the Tails USB image to disk "old" 53.081
When I start Tails from USB drive "old" with network unplugged 1:28.492
Then the boot device has safe access rights 3.550
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:335 9.384
After features/support/hooks.rb:105 0.009
Tags: @product
2:35.361
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.301
And I start Tails from USB drive "old" with network unplugged and I login 1:41.544
Then Tails is running from USB drive "old" 0.507
And I create a persistent partition 39.986
And I take note of which tps features are available 2.799
Then a Tails persistence partition exists on USB drive "old" 1.064
And I shutdown Tails and wait for the computer to power off 9.158
After features/support/hooks.rb:335 0.280
After features/support/hooks.rb:105 0.013
Tags: @product
3:19.180
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.009
Given a computer 0.323
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.152
Then Tails is running from USB drive "old" 0.352
And all tps features are active 6.629
When I write some files expected to persist 1.852
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.459
And I take note of which tps features are available 2.605
And I shutdown Tails and wait for the computer to power off 6.695
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.475
After features/support/hooks.rb:335 0.161
After features/support/hooks.rb:105 0.008
Tags: @product
2:58.074
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 without a persistent partition and stopped at Tails Greeter's login screen 16.783
And I log in to a new session 20.952
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.610
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.417
Then the running Tails is installed on USB drive "to_upgrade" 31.369
And I unplug USB drive "to_upgrade" 0.263
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:335 2.193
After features/support/hooks.rb:105 0.000
Tags: @product
2:29.090
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.428
Then all tps features from the old Tails version are active 2.477
And Tails is running from USB drive "to_upgrade" 0.581
And the boot device has safe access rights 3.625
And the expected persistent files created with the old Tails version are present in the filesystem 1.881
And all persistent directories from the old Tails version have safe access rights 2.850
After features/support/hooks.rb:335 1.459
After features/support/hooks.rb:105 0.010
Tags: @product @automatic_upgrade
7:10.789
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 20.763
And no SquashFS delta is installed 1.610
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.603
When the network is plugged 0.170
And Tor is ready 25.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.889
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.157
Given I shutdown Tails and wait for the computer to power off 11.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.680
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 3.846
And the file system changes introduced in version 6.2~testoverlayfs are present 0.425
And only the 6.2~testoverlayfs SquashFS delta is installed 1.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.263
When the network is plugged 1.153
And Tor is ready 19.070
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.702
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.689
Given I shutdown Tails and wait for the computer to power off 4.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.294
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.875
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.099
And Tor is ready 18.828
Then the Upgrader considers the system as up-to-date 0.341
# 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.523
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.881
After features/support/hooks.rb:335 0.753
After features/support/hooks.rb:105 0.021
Tags: @product @automatic_upgrade
54.035
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 19.418
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.736
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.089
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 25.993
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.596
After features/support/hooks.rb:335 0.878
After features/support/hooks.rb:105 0.000