Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 78 30 May 2025, 18:38

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 20:28.790 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:19.096
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 37.201
When I start Tails from USB drive "old" with network unplugged 1:35.632
Then the boot device has safe access rights 3.754
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.378
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:335 3.600
After features/support/hooks.rb:105 0.010
Tags: @product
2:16.965
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.476
And I start Tails from USB drive "old" with network unplugged and I login 1:33.105
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 31.089
And I take note of which tps features are available 1.667
Then a Tails persistence partition exists on USB drive "old" 0.920
And I shutdown Tails and wait for the computer to power off 9.356
After features/support/hooks.rb:335 0.206
After features/support/hooks.rb:105 0.011
Tags: @product
2:56.715
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.273
Then Tails is running from USB drive "old" 0.495
And all tps features are active 2.111
When I write some files expected to persist 1.924
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.555
And all persistent directories from the old Tails version have safe access rights 2.920
And I take note of which tps features are available 0.645
And I shutdown Tails and wait for the computer to power off 6.645
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.659
After features/support/hooks.rb:335 0.108
After features/support/hooks.rb:105 0.008
Tags: @product
2:39.002
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.912
And I log in to a new session 20.101
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.729
And I plug USB drive "to_upgrade" 2.539
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.144
Then the running Tails is installed on USB drive "to_upgrade" 27.138
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:335 1.883
After features/support/hooks.rb:105 0.000
Tags: @product
2:29.836
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.661
Then all tps features from the old Tails version are active 1.802
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.608
And the expected persistent files created with the old Tails version are present in the filesystem 1.517
And all persistent directories from the old Tails version have safe access rights 2.672
After features/support/hooks.rb:335 2.055
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
6:57.572
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.709
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.549
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.084
And Tor is ready 23.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.098
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.108
Given I shutdown Tails and wait for the computer to power off 8.998
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.933
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.389
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.282
# 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.272
When the network is plugged 0.083
And Tor is ready 18.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.479
Given I shutdown Tails and wait for the computer to power off 4.275
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.775
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 5.755
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.397
And Tor is ready 16.191
Then the Upgrader considers the system as up-to-date 0.318
# 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.208
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.468
After features/support/hooks.rb:335 0.731
After features/support/hooks.rb:105 0.020
Tags: @product @automatic_upgrade
49.601
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 with a persistent partition enabled and logged in 15.727
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.648
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 24.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.162
After features/support/hooks.rb:335 1.334
After features/support/hooks.rb:105 0.000