Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 53 06 May 2025, 20:43

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:2.956 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:6.022
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 30.765
When I start Tails from USB drive "old" with network unplugged 1:29.737
Then the boot device has safe access rights 3.151
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:335 6.962
After features/support/hooks.rb:105 0.010
Tags: @product
2:8.716
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.323
And I start Tails from USB drive "old" with network unplugged and I login 1:23.867
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 31.490
And I take note of which tps features are available 2.763
Then a Tails persistence partition exists on USB drive "old" 1.106
And I shutdown Tails and wait for the computer to power off 8.813
After features/support/hooks.rb:335 0.180
After features/support/hooks.rb:105 0.009
Tags: @product
2:57.354
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.322
Then Tails is running from USB drive "old" 1.219
And all tps features are active 2.016
When I write some files expected to persist 2.471
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.138
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.513
And I take note of which tps features are available 0.671
And I shutdown Tails and wait for the computer to power off 4.424
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.972
After features/support/hooks.rb:335 0.128
After features/support/hooks.rb:105 0.009
Tags: @product
2:31.099
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 without a persistent partition and stopped at Tails Greeter's login screen 10.937
And I log in to a new session 18.156
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.757
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.561
Then the running Tails is installed on USB drive "to_upgrade" 23.756
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:335 2.844
After features/support/hooks.rb:105 0.000
Tags: @product
2:11.549
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.824
Then all tps features from the old Tails version are active 1.603
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.508
And all persistent directories from the old Tails version have safe access rights 2.580
After features/support/hooks.rb:335 1.174
After features/support/hooks.rb:105 0.010
Tags: @product @automatic_upgrade
6:33.277
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.706
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.069
And Tor is ready 19.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.178
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.742
Given I shutdown Tails and wait for the computer to power off 8.944
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.601
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.293
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.355
# 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.245
When the network is plugged 0.069
And Tor is ready 17.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.577
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.120
Given I shutdown Tails and wait for the computer to power off 4.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.336
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.041
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.071
And Tor is ready 19.619
Then the Upgrader considers the system as up-to-date 0.289
# 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.452
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.559
After features/support/hooks.rb:335 0.973
After features/support/hooks.rb:105 0.017
Tags: @product @automatic_upgrade
34.937
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 10.007
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.133
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 17.354
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.787
After features/support/hooks.rb:335 1.165
After features/support/hooks.rb:105 0.000