Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 28 19 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 19:50.803 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:14.084
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 30.069
When I start Tails from USB drive "old" with network unplugged 1:38.221
Then the boot device has safe access rights 3.304
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.336
After features/support/hooks.rb:330 3.587
After features/support/hooks.rb:100 0.074
Tags: @product
2:13.029
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:30.825
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 30.583
And I take note of which tps features are available 2.040
Then a Tails persistence partition exists on USB drive "old" 0.838
And I shutdown Tails and wait for the computer to power off 8.221
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.011
Tags: @product
2:55.813
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.872
Then Tails is running from USB drive "old" 0.603
And all tps features are active 2.033
When I write some files expected to persist 2.069
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.360
And I take note of which tps features are available 0.614
And I shutdown Tails and wait for the computer to power off 4.370
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.049
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.695
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.900
And I log in to a new session 18.641
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.615
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.234
Then the running Tails is installed on USB drive "to_upgrade" 24.437
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:330 1.131
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.770
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.128
Then all tps features from the old Tails version are active 2.898
And Tails is running from USB drive "to_upgrade" 0.438
And the boot device has safe access rights 4.106
And the expected persistent files created with the old Tails version are present in the filesystem 1.570
And all persistent directories from the old Tails version have safe access rights 2.407
After features/support/hooks.rb:330 1.934
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:47.198
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.748
And no SquashFS delta is installed 0.297
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.500
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.081
And Tor is ready 23.544
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.704
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.211
Given I shutdown Tails and wait for the computer to power off 10.824
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.987
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.465
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
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.304
# 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.354
When the network is plugged 0.084
And Tor is ready 21.096
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.547
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.132
Given I shutdown Tails and wait for the computer to power off 4.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.290
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.114
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.407
When the network is plugged 0.075
And Tor is ready 19.340
Then the Upgrader considers the system as up-to-date 0.349
# 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.520
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.598
After features/support/hooks.rb:330 0.799
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.606
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.571
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.137
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 17.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.904
After features/support/hooks.rb:330 1.427
After features/support/hooks.rb:100 0.000