Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 68 21 May 2025, 18: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 21:26.854 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:45.675
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.539
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 1:12.386
When I start Tails from USB drive "old" with network unplugged 1:27.322
Then the boot device has safe access rights 3.227
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:335 7.010
After features/support/hooks.rb:105 0.007
Tags: @product
2:9.300
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.292
And I start Tails from USB drive "old" with network unplugged and I login 1:25.547
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 31.379
And I take note of which tps features are available 2.631
Then a Tails persistence partition exists on USB drive "old" 0.773
And I shutdown Tails and wait for the computer to power off 8.344
After features/support/hooks.rb:335 0.143
After features/support/hooks.rb:105 0.010
Tags: @product
2:56.625
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.009
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.065
Then Tails is running from USB drive "old" 0.367
And all tps features are active 2.072
When I write some files expected to persist 2.207
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.630
And I take note of which tps features are available 1.024
And I shutdown Tails and wait for the computer to power off 6.577
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.856
After features/support/hooks.rb:335 0.129
After features/support/hooks.rb:105 0.012
Tags: @product
2:47.553
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 without a persistent partition and stopped at Tails Greeter's login screen 16.802
And I log in to a new session 18.695
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.595
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.915
Then the running Tails is installed on USB drive "to_upgrade" 24.649
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.258
After features/support/hooks.rb:335 2.595
After features/support/hooks.rb:105 0.000
Tags: @product
2:24.976
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.312
Then all tps features from the old Tails version are active 3.134
And Tails is running from USB drive "to_upgrade" 0.469
And the boot device has safe access rights 3.568
And the expected persistent files created with the old Tails version are present in the filesystem 1.617
And all persistent directories from the old Tails version have safe access rights 2.632
After features/support/hooks.rb:335 1.927
After features/support/hooks.rb:105 0.008
Tags: @product @automatic_upgrade
7:43.178
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 49.648
And no SquashFS delta is installed 0.603
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.098
And Tor is ready 23.738
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.530
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.009
Given I shutdown Tails and wait for the computer to power off 10.962
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.283
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.484
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.265
When the network is plugged 0.083
And Tor is ready 17.338
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.245
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.009
Given I shutdown Tails and wait for the computer to power off 6.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.666
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 5.724
And the file system changes introduced in version 6.3~testoverlayfs are present 0.700
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.413
When the network is plugged 0.444
And Tor is ready 19.250
Then the Upgrader considers the system as up-to-date 0.314
# 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 15.547
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.855
After features/support/hooks.rb:335 0.738
After features/support/hooks.rb:105 0.019
Tags: @product @automatic_upgrade
39.544
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.462
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 21.250
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.251
After features/support/hooks.rb:335 2.273
After features/support/hooks.rb:105 0.000