Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 74 26 May 2025, 22: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 20:10.436 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:10.852
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 31.396
When I start Tails from USB drive "old" with network unplugged 1:33.932
Then the boot device has safe access rights 3.208
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:335 7.080
After features/support/hooks.rb:105 0.010
Tags: @product
2:17.113
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:30.817
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 33.612
And I take note of which tps features are available 2.141
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 9.086
After features/support/hooks.rb:335 0.165
After features/support/hooks.rb:105 0.010
Tags: @product
3:5.201
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.158
Then Tails is running from USB drive "old" 0.995
And all tps features are active 2.428
When I write some files expected to persist 2.460
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.550
And all persistent directories from the old Tails version have safe access rights 3.145
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 6.693
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.921
After features/support/hooks.rb:335 0.171
After features/support/hooks.rb:105 0.010
Tags: @product
2:41.482
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.825
And I log in to a new session 20.272
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.941
And I plug USB drive "to_upgrade" 2.502
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.877
Then the running Tails is installed on USB drive "to_upgrade" 29.633
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:335 2.984
After features/support/hooks.rb:105 0.000
Tags: @product
2:20.076
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.391
Then all tps features from the old Tails version are active 1.819
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.959
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.781
After features/support/hooks.rb:335 0.851
After features/support/hooks.rb:105 0.010
Tags: @product @automatic_upgrade
7:0.405
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 11.459
And no SquashFS delta is installed 0.270
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.396
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.568
When the network is plugged 0.087
And Tor is ready 21.541
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.081
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.780
Given I shutdown Tails and wait for the computer to power off 11.419
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.695
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.243
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.295
When the network is plugged 0.069
And Tor is ready 19.892
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.468
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.590
Given I shutdown Tails and wait for the computer to power off 6.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.742
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.982
And the file system changes introduced in version 6.3~testoverlayfs are present 0.687
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.410
When the network is plugged 0.070
And Tor is ready 21.023
Then the Upgrader considers the system as up-to-date 0.307
# 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.256
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.740
After features/support/hooks.rb:335 0.701
After features/support/hooks.rb:105 0.019
Tags: @product @automatic_upgrade
35.304
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.877
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 16.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.002
After features/support/hooks.rb:335 2.296
After features/support/hooks.rb:105 0.000