Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 112 05 Jul 2025, 20:41

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 26:10.248 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:53.633
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 39.900
When I start Tails from USB drive "old" with network unplugged 2:1.776
Then the boot device has safe access rights 3.901
And Tails is running from USB drive "old" 3.515
And there is no persistence partition on USB drive "old" 0.600
And process "udev-watchdog" is running 0.215
And udev-watchdog is monitoring the correct device 0.928
And I unplug USB drive "old" 1.466
After features/support/hooks.rb:335 4.673
After features/support/hooks.rb:105 0.010
Tags: @product
2:49.223
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:52.284
Then Tails is running from USB drive "old" 0.988
And I create a persistent partition 43.117
And I take note of which tps features are available 2.755
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 9.090
After features/support/hooks.rb:335 2.781
After features/support/hooks.rb:105 0.075
Tags: @product
4:10.457
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.018
Given a computer 0.957
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:11.861
Then Tails is running from USB drive "old" 0.926
And all tps features are active 3.149
When I write some files expected to persist 6.029
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.465
And all persistence configuration files have safe access rights 0.723
And all persistent directories from the old Tails version have safe access rights 3.520
And I take note of which tps features are available 0.487
And I shutdown Tails and wait for the computer to power off 6.510
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.825
After features/support/hooks.rb:335 0.112
After features/support/hooks.rb:105 0.009
Tags: @product
3:13.212
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 12.974
And I log in to a new session 28.992
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.210
And I plug USB drive "to_upgrade" 3.093
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.985
Then the running Tails is installed on USB drive "to_upgrade" 31.399
And I unplug USB drive "to_upgrade" 0.291
And I unplug USB drive "__internal" 0.265
After features/support/hooks.rb:335 7.477
After features/support/hooks.rb:105 0.000
Tags: @product
3:1.373
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:45.121
Then all tps features from the old Tails version are active 5.418
And Tails is running from USB drive "to_upgrade" 0.635
And the boot device has safe access rights 5.283
And the expected persistent files created with the old Tails version are present in the filesystem 1.673
And all persistent directories from the old Tails version have safe access rights 3.018
After features/support/hooks.rb:335 1.164
After features/support/hooks.rb:105 0.020
Tags: @product @automatic_upgrade
8:53.242
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 18.553
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.190
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.669
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.079
And Tor is ready 27.489
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.174
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.795
Given I shutdown Tails and wait for the computer to power off 9.731
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:57.541
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.525
And the file system changes introduced in version 6.2~testoverlayfs are present 0.391
And only the 6.2~testoverlayfs SquashFS delta is installed 0.118
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.441
# 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.294
When the network is plugged 0.074
And Tor is ready 21.524
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.994
Given I shutdown Tails and wait for the computer to power off 6.726
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:40.022
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.274
And the file system changes introduced in version 6.3~testoverlayfs are present 0.779
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.397
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.838
When the network is plugged 0.186
And Tor is ready 27.926
Then the Upgrader considers the system as up-to-date 0.364
# 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 21.704
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.069
After features/support/hooks.rb:335 0.816
After features/support/hooks.rb:105 0.017
Tags: @product @automatic_upgrade
1:9.107
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 14.375
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.567
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.206
And the signing key used by the Upgrader is outdated 0.166
But a current signing key is available on our website 0.000
When the network is plugged 0.337
And Tor is ready 51.973
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.479
After features/support/hooks.rb:335 3.119
After features/support/hooks.rb:105 0.000