Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 20 11 Apr 2025, 18:24

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:7.681 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:26.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 31.766
When I start Tails from USB drive "old" with network unplugged 1:49.305
Then the boot device has safe access rights 3.356
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 10.351
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.404
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login 1:33.731
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 30.710
And I take note of which tps features are available 2.375
Then a Tails persistence partition exists on USB drive "old" 1.517
And I shutdown Tails and wait for the computer to power off 6.419
After features/support/hooks.rb:330 0.183
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.004
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.564
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.413
When I write some files expected to persist 1.911
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.480
And all persistent directories from the old Tails version have safe access rights 3.044
And I take note of which tps features are available 0.542
And I shutdown Tails and wait for the computer to power off 4.427
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.828
After features/support/hooks.rb:330 0.122
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.261
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 11.519
And I log in to a new session 22.083
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.759
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.341
Then the running Tails is installed on USB drive "to_upgrade" 24.681
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 3.701
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.201
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.799
Then all tps features from the old Tails version are active 1.613
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.501
And the expected persistent files created with the old Tails version are present in the filesystem 1.423
And all persistent directories from the old Tails version have safe access rights 2.301
After features/support/hooks.rb:330 1.591
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:50.740
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 12.170
And no SquashFS delta is installed 0.360
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.420
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.076
And Tor is ready 18.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.142
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.792
Given I shutdown Tails and wait for the computer to power off 9.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.681
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.269
And the file system changes introduced in version 6.2~testoverlayfs are present 0.405
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.297
When the network is plugged 0.087
And Tor is ready 20.110
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.086
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.905
Given I shutdown Tails and wait for the computer to power off 4.316
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.107
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.594
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.437
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.104
And Tor is ready 18.560
Then the Upgrader considers the system as up-to-date 10.902
# 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.965
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.040
After features/support/hooks.rb:330 1.279
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
38.249
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.874
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.681
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 19.571
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.762
After features/support/hooks.rb:330 2.166
After features/support/hooks.rb:100 0.000