Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 116 08 Jul 2025, 21:50

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 40:39.560 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
4:2.375
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.285
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 1:4.567
When I start Tails from USB drive "old" with network unplugged 2:39.630
Then the boot device has safe access rights 15.310
And Tails is running from USB drive "old" 0.432
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.399
And I unplug USB drive "old" 0.400
After features/support/hooks.rb:335 16.864
After features/support/hooks.rb:105 0.014
Tags: @product
4:17.272
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Given a computer 0.291
And I start Tails from USB drive "old" with network unplugged and I login 2:41.707
Then Tails is running from USB drive "old" 0.616
And I create a persistent partition 1:7.300
And I take note of which tps features are available 8.679
Then a Tails persistence partition exists on USB drive "old" 2.325
And I shutdown Tails and wait for the computer to power off 16.351
After features/support/hooks.rb:335 1.342
After features/support/hooks.rb:105 0.038
Tags: @product
5:49.309
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.017
Given a computer 0.487
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:29.658
Then Tails is running from USB drive "old" 3.086
And all tps features are active 7.873
When I write some files expected to persist 2.109
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 3.533
And I take note of which tps features are available 0.698
And I shutdown Tails and wait for the computer to power off 13.055
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 48.113
After features/support/hooks.rb:335 1.002
After features/support/hooks.rb:105 0.403
Tags: @product
4:51.217
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.310
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 17.642
And I log in to a new session 38.721
And I clone USB drive "old" to a new USB drive "to_upgrade" 11.030
And I plug USB drive "to_upgrade" 4.975
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:23.914
Then the running Tails is installed on USB drive "to_upgrade" 1:13.849
And I unplug USB drive "to_upgrade" 0.550
And I unplug USB drive "__internal" 0.532
After features/support/hooks.rb:335 1.125
After features/support/hooks.rb:105 0.000
Tags: @product
4:59.231
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:27.401
Then all tps features from the old Tails version are active 9.623
And Tails is running from USB drive "to_upgrade" 0.662
And the boot device has safe access rights 5.263
And the expected persistent files created with the old Tails version are present in the filesystem 2.118
And all persistent directories from the old Tails version have safe access rights 13.958
After features/support/hooks.rb:335 2.033
After features/support/hooks.rb:105 0.042
Tags: @product @automatic_upgrade
15:34.175
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 26.210
And no SquashFS delta is installed 1.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 4.600
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.584
And the file system changes introduced in version 6.2~testoverlayfs are not present 2.185
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.670
When the network is plugged 0.177
And Tor is ready 42.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 19.436
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 38.010
Given I shutdown Tails and wait for the computer to power off 2:31.896
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:55.946
Then Tails is running version 6.2~testoverlayfs 0.553
And all tps features are active 11.173
And the file system changes introduced in version 6.2~testoverlayfs are present 0.651
And only the 6.2~testoverlayfs SquashFS delta is installed 0.109
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.384
# 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.419
When the network is plugged 0.101
And Tor is ready 40.959
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 17.015
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 23.213
Given I shutdown Tails and wait for the computer to power off 11.110
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:32.820
Then Tails is running version 6.3~testoverlayfs 0.079
And all tps features are active 7.332
And the file system changes introduced in version 6.3~testoverlayfs are present 3.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.690
# 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 1.060
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.581
When the network is plugged 0.112
And Tor is ready 39.659
Then the Upgrader considers the system as up-to-date 0.557
# 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 27.090
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 11.267
After features/support/hooks.rb:335 2.136
After features/support/hooks.rb:105 0.022
Tags: @product @automatic_upgrade
1:5.978
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 18.684
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.649
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 40.293
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.036
After features/support/hooks.rb:335 1.514
After features/support/hooks.rb:105 0.000