Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 77 29 May 2025, 18:48

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:24.012 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:7.053
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 34.486
When I start Tails from USB drive "old" with network unplugged 1:27.338
Then the boot device has safe access rights 2.937
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:335 6.886
After features/support/hooks.rb:105 0.008
Tags: @product
2:9.457
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:25.787
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 32.192
And I take note of which tps features are available 1.587
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.564
After features/support/hooks.rb:335 0.235
After features/support/hooks.rb:105 0.009
Tags: @product
3:2.519
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.961
Then Tails is running from USB drive "old" 1.580
And all tps features are active 2.679
When I write some files expected to persist 4.096
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.628
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 6.639
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.633
After features/support/hooks.rb:335 0.151
After features/support/hooks.rb:105 0.008
Tags: @product
2:38.118
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 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 11.289
And I log in to a new session 19.013
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.659
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.206
Then the running Tails is installed on USB drive "to_upgrade" 28.110
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:335 6.862
After features/support/hooks.rb:105 0.000
Tags: @product
2:17.182
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.690
Then all tps features from the old Tails version are active 1.875
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.761
And the expected persistent files created with the old Tails version are present in the filesystem 1.594
And all persistent directories from the old Tails version have safe access rights 2.713
After features/support/hooks.rb:335 1.015
After features/support/hooks.rb:105 0.007
Tags: @product @automatic_upgrade
6:35.933
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.623
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.698
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.085
And Tor is ready 18.531
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.889
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.719
Given I shutdown Tails and wait for the computer to power off 8.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.359
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 3.313
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# 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.329
When the network is plugged 0.084
And Tor is ready 18.503
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.848
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.447
Given I shutdown Tails and wait for the computer to power off 4.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.605
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.041
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.085
And Tor is ready 16.671
Then the Upgrader considers the system as up-to-date 0.319
# 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.031
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.723
After features/support/hooks.rb:335 0.695
After features/support/hooks.rb:105 0.017
Tags: @product @automatic_upgrade
33.746
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.733
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 15.706
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.655
After features/support/hooks.rb:335 1.159
After features/support/hooks.rb:105 0.000