Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 117 14 Jul 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 23:14.919 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:31.515
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.887
When I start Tails from USB drive "old" with network unplugged 1:50.082
Then the boot device has safe access rights 4.877
And Tails is running from USB drive "old" 0.495
And there is no persistence partition on USB drive "old" 0.107
And process "udev-watchdog" is running 0.161
And udev-watchdog is monitoring the correct device 0.390
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:335 4.059
After features/support/hooks.rb:105 0.016
Tags: @product
2:57.056
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 2:3.500
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 38.786
And I take note of which tps features are available 2.616
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 10.731
After features/support/hooks.rb:335 0.302
After features/support/hooks.rb:105 0.022
Tags: @product
3:27.466
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.019
Given a computer 0.518
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:40.918
Then Tails is running from USB drive "old" 1.252
And all tps features are active 3.057
When I write some files expected to persist 2.230
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 3.016
And I take note of which tps features are available 0.578
And I shutdown Tails and wait for the computer to power off 7.929
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.320
After features/support/hooks.rb:335 0.147
After features/support/hooks.rb:105 0.011
Tags: @product
2:54.256
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.569
And I log in to a new session 25.829
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.780
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.868
Then the running Tails is installed on USB drive "to_upgrade" 30.245
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.311
After features/support/hooks.rb:335 1.040
After features/support/hooks.rb:105 0.000
Tags: @product
2:42.633
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.009
Given a computer 0.406
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:28.336
Then all tps features from the old Tails version are active 1.892
And Tails is running from USB drive "to_upgrade" 0.661
And the boot device has safe access rights 5.994
And the expected persistent files created with the old Tails version are present in the filesystem 2.411
And all persistent directories from the old Tails version have safe access rights 2.930
After features/support/hooks.rb:335 1.849
After features/support/hooks.rb:105 0.046
Tags: @product @automatic_upgrade
7:58.193
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 with a persistent partition enabled and logged in 11.779
And no SquashFS delta is installed 0.235
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.518
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.944
When the network is plugged 0.181
And Tor is ready 22.813
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.987
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.891
Given I shutdown Tails and wait for the computer to power off 16.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.375
Then Tails is running version 6.2~testoverlayfs 0.140
And all tps features are active 4.159
And the file system changes introduced in version 6.2~testoverlayfs are present 0.438
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.372
# 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.362
When the network is plugged 0.066
And Tor is ready 20.457
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.155
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.291
Given I shutdown Tails and wait for the computer to power off 6.981
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.238
Then Tails is running version 6.3~testoverlayfs 0.060
And all tps features are active 3.547
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.388
When the network is plugged 0.069
And Tor is ready 20.194
Then the Upgrader considers the system as up-to-date 0.362
# 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.267
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.725
After features/support/hooks.rb:335 0.737
After features/support/hooks.rb:105 0.019
Tags: @product @automatic_upgrade
43.797
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 12.751
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.580
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.140
And the signing key used by the Upgrader is outdated 0.190
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 22.185
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.854
After features/support/hooks.rb:335 1.738
After features/support/hooks.rb:105 0.000