Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 100 23 Jun 2025, 20:45

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 36:11.678 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
3:55.133
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 1:7.687
When I start Tails from USB drive "old" with network unplugged 2:31.710
Then the boot device has safe access rights 13.314
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.253
After features/support/hooks.rb:335 3.779
After features/support/hooks.rb:105 0.007
Tags: @product
4:7.468
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login 2:40.889
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 59.699
And I take note of which tps features are available 5.520
Then a Tails persistence partition exists on USB drive "old" 6.583
And I shutdown Tails and wait for the computer to power off 14.208
After features/support/hooks.rb:335 0.612
After features/support/hooks.rb:105 0.035
Tags: @product
5:31.132
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.015
Given a computer 0.498
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:6.268
Then Tails is running from USB drive "old" 0.797
And all tps features are active 3.753
When I write some files expected to persist 2.048
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.205
And all persistence configuration files have safe access rights 4.484
And all persistent directories from the old Tails version have safe access rights 8.447
And I take note of which tps features are available 0.588
And I shutdown Tails and wait for the computer to power off 5.501
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 57.540
After features/support/hooks.rb:335 0.197
After features/support/hooks.rb:105 0.006
Tags: @product
4:19.946
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 without a persistent partition and stopped at Tails Greeter's login screen 20.916
And I log in to a new session 39.684
And I clone USB drive "old" to a new USB drive "to_upgrade" 13.693
And I plug USB drive "to_upgrade" 3.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:15.794
Then the running Tails is installed on USB drive "to_upgrade" 45.769
And I unplug USB drive "to_upgrade" 0.429
And I unplug USB drive "__internal" 0.453
After features/support/hooks.rb:335 4.760
After features/support/hooks.rb:105 0.000
Tags: @product
4:17.618
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.025
Given a computer 0.836
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:52.378
Then all tps features from the old Tails version are active 3.059
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 15.211
And the expected persistent files created with the old Tails version are present in the filesystem 2.110
And all persistent directories from the old Tails version have safe access rights 3.646
After features/support/hooks.rb:335 7.903
After features/support/hooks.rb:105 0.047
Tags: @product @automatic_upgrade
12:59.008
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.027
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:0.221
And no SquashFS delta is installed 0.762
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.177
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.497
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.609
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.771
When the network is plugged 0.142
And Tor is ready 41.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 18.091
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.688
Given I shutdown Tails and wait for the computer to power off 19.667
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:0.119
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.542
And the file system changes introduced in version 6.2~testoverlayfs are present 0.539
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.402
# 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.421
When the network is plugged 0.092
And Tor is ready 37.441
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 18.069
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 21.160
Given I shutdown Tails and wait for the computer to power off 9.156
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:31.845
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.079
And the file system changes introduced in version 6.3~testoverlayfs are present 1.056
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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.454
When the network is plugged 0.414
And Tor is ready 33.112
Then the Upgrader considers the system as up-to-date 0.366
# 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 24.699
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 8.932
After features/support/hooks.rb:335 3.691
After features/support/hooks.rb:105 0.028
Tags: @product @automatic_upgrade
1:1.369
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 with a persistent partition enabled and logged in 11.347
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.761
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.329
And the signing key used by the Upgrader is outdated 0.828
But a current signing key is available on our website 0.000
When the network is plugged 0.896
And Tor is ready 27.104
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 18.101
After features/support/hooks.rb:335 1.781
After features/support/hooks.rb:105 0.000