Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 63 16 May 2025, 18:29

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:42.245 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:39.815
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 1:2.183
When I start Tails from USB drive "old" with network unplugged 1:32.072
Then the boot device has safe access rights 3.215
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:335 3.559
After features/support/hooks.rb:105 0.010
Tags: @product
2:8.351
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.523
And I start Tails from USB drive "old" with network unplugged and I login 1:24.502
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 32.012
And I take note of which tps features are available 1.921
Then a Tails persistence partition exists on USB drive "old" 0.780
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:335 0.219
After features/support/hooks.rb:105 0.008
Tags: @product
2:48.997
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.834
Then Tails is running from USB drive "old" 0.316
And all tps features are active 1.952
When I write some files expected to persist 1.589
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
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.638
And I take note of which tps features are available 0.488
And I shutdown Tails and wait for the computer to power off 6.436
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.962
After features/support/hooks.rb:335 0.129
After features/support/hooks.rb:105 0.007
Tags: @product
2:40.871
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.187
And I log in to a new session 18.057
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.326
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.318
Then the running Tails is installed on USB drive "to_upgrade" 30.112
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.267
After features/support/hooks.rb:335 3.560
After features/support/hooks.rb:105 0.000
Tags: @product
2:18.590
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.255
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.935
Then all tps features from the old Tails version are active 1.699
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.255
And the expected persistent files created with the old Tails version are present in the filesystem 1.682
And all persistent directories from the old Tails version have safe access rights 2.447
After features/support/hooks.rb:335 1.439
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
6:30.526
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 11.501
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.094
And Tor is ready 19.787
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.702
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.608
Given I shutdown Tails and wait for the computer to power off 8.758
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.383
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.137
And the file system changes introduced in version 6.2~testoverlayfs are present 0.371
And only the 6.2~testoverlayfs SquashFS delta is installed 0.103
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.399
# 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.253
When the network is plugged 0.071
And Tor is ready 17.524
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.021
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.016
Given I shutdown Tails and wait for the computer to power off 4.486
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.387
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.324
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.098
And Tor is ready 18.276
Then the Upgrader considers the system as up-to-date 0.312
# 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.976
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.500
After features/support/hooks.rb:335 0.752
After features/support/hooks.rb:105 0.016
Tags: @product @automatic_upgrade
35.092
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.115
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.065
And the signing key used by the Upgrader is outdated 0.119
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 16.137
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.109
After features/support/hooks.rb:335 1.120
After features/support/hooks.rb:105 0.000