Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 80 01 Jun 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:56.583 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:26.345
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.331
When I start Tails from USB drive "old" with network unplugged 1:49.587
Then the boot device has safe access rights 3.017
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:335 6.991
After features/support/hooks.rb:105 0.010
Tags: @product
2:12.696
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:30.211
Then Tails is running from USB drive "old" 0.426
And I create a persistent partition 30.791
And I take note of which tps features are available 2.023
Then a Tails persistence partition exists on USB drive "old" 0.704
And I shutdown Tails and wait for the computer to power off 8.326
After features/support/hooks.rb:335 0.170
After features/support/hooks.rb:105 0.008
Tags: @product
2:51.398
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.865
Then Tails is running from USB drive "old" 0.358
And all tps features are active 2.000
When I write some files expected to persist 1.682
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.877
And I take note of which tps features are available 1.650
And I shutdown Tails and wait for the computer to power off 4.239
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.896
After features/support/hooks.rb:335 0.123
After features/support/hooks.rb:105 0.009
Tags: @product
2:32.793
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 9.876
And I log in to a new session 18.682
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.117
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.367
Then the running Tails is installed on USB drive "to_upgrade" 24.796
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:335 2.302
After features/support/hooks.rb:105 0.000
Tags: @product
2:20.818
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.340
Then all tps features from the old Tails version are active 1.778
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.243
And the expected persistent files created with the old Tails version are present in the filesystem 1.467
And all persistent directories from the old Tails version have safe access rights 2.385
After features/support/hooks.rb:335 1.383
After features/support/hooks.rb:105 0.007
Tags: @product @automatic_upgrade
6:48.763
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 12.178
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.968
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.470
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.073
And Tor is ready 23.441
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.735
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.771
Given I shutdown Tails and wait for the computer to power off 8.965
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.327
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.383
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.414
# 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.297
When the network is plugged 0.070
And Tor is ready 17.273
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.456
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.733
Given I shutdown Tails and wait for the computer to power off 6.425
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.475
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.354
When the network is plugged 0.076
And Tor is ready 19.786
Then the Upgrader considers the system as up-to-date 0.332
# 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 14.675
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.923
After features/support/hooks.rb:335 0.707
After features/support/hooks.rb:105 0.016
Tags: @product @automatic_upgrade
43.766
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 11.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.116
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 24.544
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.791
After features/support/hooks.rb:335 0.688
After features/support/hooks.rb:105 0.000