Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 14 04 Apr 2025, 18:37

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:40.395 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:21.827
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 51.405
When I start Tails from USB drive "old" with network unplugged 1:25.126
Then the boot device has safe access rights 2.989
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 7.079
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.480
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:26.173
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 31.178
And I take note of which tps features are available 2.410
Then a Tails persistence partition exists on USB drive "old" 0.776
And I shutdown Tails and wait for the computer to power off 8.357
After features/support/hooks.rb:330 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.657
Then Tails is running from USB drive "old" 0.350
And all tps features are active 2.202
When I write some files expected to persist 1.668
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.420
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.356
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.201
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.294
And I log in to a new session 19.584
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.616
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.629
Then the running Tails is installed on USB drive "to_upgrade" 26.450
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 3.676
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.663
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.240
Then all tps features from the old Tails version are active 1.727
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.268
And the expected persistent files created with the old Tails version are present in the filesystem 1.350
And all persistent directories from the old Tails version have safe access rights 2.536
After features/support/hooks.rb:330 1.335
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:37.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.584
And no SquashFS delta is installed 1.008
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.062
And Tor is ready 48.149
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.576
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.204
Given I shutdown Tails and wait for the computer to power off 1:35.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.148
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.211
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# 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.271
When the network is plugged 0.076
And Tor is ready 19.841
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.273
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.420
Given I shutdown Tails and wait for the computer to power off 6.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.265
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.076
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.064
And Tor is ready 17.598
Then the Upgrader considers the system as up-to-date 11.040
# 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.446
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.140
After features/support/hooks.rb:330 0.697
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
41.382
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.602
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.155
And the signing key used by the Upgrader is outdated 0.148
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 22.229
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.829
After features/support/hooks.rb:330 0.976
After features/support/hooks.rb:100 0.000