Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 56 09 May 2025, 18:27

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:30.338 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:20.551
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.224
When I start Tails from USB drive "old" with network unplugged 1:43.887
Then the boot device has safe access rights 3.081
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:335 1.051
After features/support/hooks.rb:105 0.009
Tags: @product
2:27.134
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:43.889
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 30.949
And I take note of which tps features are available 2.293
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.612
After features/support/hooks.rb:335 0.133
After features/support/hooks.rb:105 0.008
Tags: @product
2:49.092
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.928
Then Tails is running from USB drive "old" 0.911
And all tps features are active 1.900
When I write some files expected to persist 1.878
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.537
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.256
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.389
After features/support/hooks.rb:335 0.112
After features/support/hooks.rb:105 0.007
Tags: @product
2:48.164
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 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 10.472
And I log in to a new session 23.432
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.314
And I plug USB drive "to_upgrade" 2.807
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.225
Then the running Tails is installed on USB drive "to_upgrade" 24.487
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:335 1.988
After features/support/hooks.rb:105 0.000
Tags: @product
2:19.637
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.805
Then all tps features from the old Tails version are active 1.766
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.706
And the expected persistent files created with the old Tails version are present in the filesystem 1.371
And all persistent directories from the old Tails version have safe access rights 2.448
After features/support/hooks.rb:335 1.065
After features/support/hooks.rb:105 0.008
Tags: @product @automatic_upgrade
7:6.927
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 29.596
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.399
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.664
When the network is plugged 0.087
And Tor is ready 19.361
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.210
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.967
Given I shutdown Tails and wait for the computer to power off 13.120
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.340
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.186
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
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.329
# 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.324
When the network is plugged 0.080
And Tor is ready 16.207
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.835
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.678
Given I shutdown Tails and wait for the computer to power off 4.225
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.023
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.365
When the network is plugged 0.087
And Tor is ready 20.344
Then the Upgrader considers the system as up-to-date 0.300
# 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.796
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.450
After features/support/hooks.rb:335 0.936
After features/support/hooks.rb:105 0.017
Tags: @product @automatic_upgrade
38.831
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.171
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 21.268
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.743
After features/support/hooks.rb:335 0.686
After features/support/hooks.rb:105 0.000