Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 36 25 Apr 2025, 18:18

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:21.847 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:23.717
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 1.503
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 36.396
When I start Tails from USB drive "old" with network unplugged 1:40.352
Then the boot device has safe access rights 3.273
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:334 3.832
After features/support/hooks.rb:104 0.009
Tags: @product
2:20.672
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:35.783
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 32.313
And I take note of which tps features are available 2.773
Then a Tails persistence partition exists on USB drive "old" 0.892
And I shutdown Tails and wait for the computer to power off 8.344
After features/support/hooks.rb:334 0.201
After features/support/hooks.rb:104 0.010
Tags: @product
3:8.222
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.081
Then Tails is running from USB drive "old" 0.421
And all tps features are active 2.379
When I write some files expected to persist 2.174
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.775
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 6.618
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.461
After features/support/hooks.rb:334 0.115
After features/support/hooks.rb:104 0.033
Tags: @product
2:39.097
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 12.681
And I log in to a new session 19.723
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.647
And I plug USB drive "to_upgrade" 2.526
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.712
Then the running Tails is installed on USB drive "to_upgrade" 27.341
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:334 1.240
After features/support/hooks.rb:104 0.000
Tags: @product
2:28.747
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.178
Then all tps features from the old Tails version are active 1.846
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 4.429
And the expected persistent files created with the old Tails version are present in the filesystem 1.748
And all persistent directories from the old Tails version have safe access rights 2.975
After features/support/hooks.rb:334 1.199
After features/support/hooks.rb:104 0.014
Tags: @product @automatic_upgrade
7:33.545
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.886
And no SquashFS delta is installed 0.430
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.533
When the network is plugged 0.090
And Tor is ready 25.800
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.681
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.598
Given I shutdown Tails and wait for the computer to power off 11.503
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.962
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.625
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
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.320
# 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.404
When the network is plugged 0.084
And Tor is ready 19.787
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.700
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.862
Given I shutdown Tails and wait for the computer to power off 4.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.505
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.305
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.104
And Tor is ready 18.399
Then the Upgrader considers the system as up-to-date 10.997
# 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 17.196
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.766
After features/support/hooks.rb:334 0.777
After features/support/hooks.rb:104 0.019
Tags: @product @automatic_upgrade
47.843
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.902
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 21.501
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.954
After features/support/hooks.rb:334 2.518
After features/support/hooks.rb:104 0.000