Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 34 24 Apr 2025, 19:28

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:47.784 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:15.091
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 28.662
When I start Tails from USB drive "old" with network unplugged 1:40.976
Then the boot device has safe access rights 3.150
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:330 3.859
After features/support/hooks.rb:100 0.015
Tags: @product
2:11.493
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.533
And I start Tails from USB drive "old" with network unplugged and I login 1:28.058
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 31.605
And I take note of which tps features are available 1.656
Then a Tails persistence partition exists on USB drive "old" 0.766
And I shutdown Tails and wait for the computer to power off 8.491
After features/support/hooks.rb:330 0.222
After features/support/hooks.rb:100 0.012
Tags: @product
2:51.478
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.697
Then Tails is running from USB drive "old" 0.406
And all tps features are active 2.459
When I write some files expected to persist 1.783
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.800
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 4.315
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.682
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.491
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.113
And I log in to a new session 19.680
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.870
And I plug USB drive "to_upgrade" 2.460
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.535
Then the running Tails is installed on USB drive "to_upgrade" 28.408
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 0.961
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.396
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.705
Then all tps features from the old Tails version are active 1.718
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.450
And the expected persistent files created with the old Tails version are present in the filesystem 1.479
And all persistent directories from the old Tails version have safe access rights 2.542
After features/support/hooks.rb:330 2.435
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
6:49.986
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 11.440
And no SquashFS delta is installed 0.244
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.415
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.098
And Tor is ready 38.914
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.904
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.706
Given I shutdown Tails and wait for the computer to power off 8.666
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.871
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.289
When the network is plugged 0.066
And Tor is ready 16.788
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.504
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.049
Given I shutdown Tails and wait for the computer to power off 4.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.495
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.912
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.064
And Tor is ready 27.856
Then the Upgrader considers the system as up-to-date 0.315
# 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.428
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.844
After features/support/hooks.rb:330 0.685
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.845
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 9.975
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.137
And the signing key used by the Upgrader is outdated 0.106
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 21.090
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.072
After features/support/hooks.rb:330 0.636
After features/support/hooks.rb:100 0.000