Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 39 25 Apr 2025, 19:51

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:32.604 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:25.159
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 33.068
When I start Tails from USB drive "old" with network unplugged 1:46.612
Then the boot device has safe access rights 3.138
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:334 7.262
After features/support/hooks.rb:104 0.010
Tags: @product
2:12.277
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:27.817
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 31.643
And I take note of which tps features are available 2.317
Then a Tails persistence partition exists on USB drive "old" 1.003
And I shutdown Tails and wait for the computer to power off 8.934
After features/support/hooks.rb:334 0.210
After features/support/hooks.rb:104 0.010
Tags: @product
3:2.022
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.799
Then Tails is running from USB drive "old" 0.687
And all tps features are active 2.555
When I write some files expected to persist 2.368
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.488
And all persistent directories from the old Tails version have safe access rights 3.061
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 6.437
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.723
After features/support/hooks.rb:334 0.146
After features/support/hooks.rb:104 0.011
Tags: @product
2:37.400
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.023
And I log in to a new session 20.690
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.408
And I plug USB drive "to_upgrade" 2.481
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.745
Then the running Tails is installed on USB drive "to_upgrade" 26.573
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.258
After features/support/hooks.rb:334 0.814
After features/support/hooks.rb:104 0.000
Tags: @product
2:20.119
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.190
Then all tps features from the old Tails version are active 1.973
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.635
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 3.109
After features/support/hooks.rb:334 1.144
After features/support/hooks.rb:104 0.015
Tags: @product @automatic_upgrade
7:15.596
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.854
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.461
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.796
When the network is plugged 0.095
And Tor is ready 23.716
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.055
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.964
Given I shutdown Tails and wait for the computer to power off 9.227
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.755
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.222
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.385
# 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.488
When the network is plugged 0.069
And Tor is ready 18.620
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.681
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.031
Given I shutdown Tails and wait for the computer to power off 6.562
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.465
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.214
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.071
And Tor is ready 15.562
Then the Upgrader considers the system as up-to-date 10.992
# 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 16.310
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.786
After features/support/hooks.rb:334 0.900
After features/support/hooks.rb:104 0.023
Tags: @product @automatic_upgrade
40.030
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 with a persistent partition enabled and logged in 10.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.570
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.154
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 20.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.765
After features/support/hooks.rb:334 1.137
After features/support/hooks.rb:104 0.000