Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 82 03 Jun 2025, 18:42

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:27.776 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:7.497
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.250
And I create a 7200 MiB disk named "old" 0.245
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.792
When I start Tails from USB drive "old" with network unplugged 1:29.976
Then the boot device has safe access rights 3.200
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.259
After features/support/hooks.rb:335 3.522
After features/support/hooks.rb:105 0.009
Tags: @product
2:11.571
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:28.910
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 31.612
And I take note of which tps features are available 1.505
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.270
After features/support/hooks.rb:335 0.136
After features/support/hooks.rb:105 0.009
Tags: @product
2:42.877
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.264
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.833
When I write some files expected to persist 1.716
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.413
And I take note of which tps features are available 0.381
And I shutdown Tails and wait for the computer to power off 6.406
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.713
After features/support/hooks.rb:335 0.119
After features/support/hooks.rb:105 0.009
Tags: @product
2:34.693
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 without a persistent partition and stopped at Tails Greeter's login screen 10.314
And I log in to a new session 19.908
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.763
And I plug USB drive "to_upgrade" 2.382
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.462
Then the running Tails is installed on USB drive "to_upgrade" 24.448
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:335 2.522
After features/support/hooks.rb:105 0.000
Tags: @product
2:21.567
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.248
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.116
Then all tps features from the old Tails version are active 1.737
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.950
And the expected persistent files created with the old Tails version are present in the filesystem 1.566
And all persistent directories from the old Tails version have safe access rights 2.612
After features/support/hooks.rb:335 1.398
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
6:51.318
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 12.751
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.629
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.365
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.059
And Tor is ready 22.800
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.227
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.305
Given I shutdown Tails and wait for the computer to power off 11.052
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.387
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.078
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.276
# 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.315
When the network is plugged 0.067
And Tor is ready 15.283
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.235
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.810
Given I shutdown Tails and wait for the computer to power off 4.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.605
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.587
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.068
And Tor is ready 24.376
Then the Upgrader considers the system as up-to-date 0.315
# 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.777
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.587
After features/support/hooks.rb:335 0.728
After features/support/hooks.rb:105 0.049
Tags: @product @automatic_upgrade
38.250
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 10.280
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.136
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 19.126
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.080
After features/support/hooks.rb:335 0.725
After features/support/hooks.rb:105 0.000