Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 95 17 Jun 2025, 22:02

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 22:48.111 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:29.125
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 38.763
When I start Tails from USB drive "old" with network unplugged 1:44.971
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:335 3.787
After features/support/hooks.rb:105 0.009
Tags: @product
2:29.773
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:38.090
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 38.722
And I take note of which tps features are available 2.652
Then a Tails persistence partition exists on USB drive "old" 0.862
And I shutdown Tails and wait for the computer to power off 8.956
After features/support/hooks.rb:335 0.201
After features/support/hooks.rb:105 0.008
Tags: @product
3:43.318
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:51.136
Then Tails is running from USB drive "old" 2.162
And all tps features are active 4.281
When I write some files expected to persist 2.398
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.569
And all persistent directories from the old Tails version have safe access rights 2.807
And I take note of which tps features are available 1.371
And I shutdown Tails and wait for the computer to power off 6.349
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.793
After features/support/hooks.rb:335 0.163
After features/support/hooks.rb:105 0.007
Tags: @product
2:59.691
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 11.957
And I log in to a new session 23.981
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.487
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.783
Then the running Tails is installed on USB drive "to_upgrade" 33.483
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.319
After features/support/hooks.rb:335 3.889
After features/support/hooks.rb:105 0.000
Tags: @product
2:42.105
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.026
Given a computer 0.341
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:30.926
Then all tps features from the old Tails version are active 2.376
And Tails is running from USB drive "to_upgrade" 0.416
And the boot device has safe access rights 3.549
And the expected persistent files created with the old Tails version are present in the filesystem 1.717
And all persistent directories from the old Tails version have safe access rights 2.776
After features/support/hooks.rb:335 0.716
After features/support/hooks.rb:105 0.009
7:40.121
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 19.768
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.540
When the network is plugged 0.388
And Tor is ready 23.288
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.216
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.989
Given I shutdown Tails and wait for the computer to power off 9.200
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.961
Then Tails is running version 6.2~testoverlayfs 0.080
And all tps features are active 3.795
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
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.347
# 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.384
When the network is plugged 0.066
And Tor is ready 21.381
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.700
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.030
Given I shutdown Tails and wait for the computer to power off 6.596
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.054
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.257
And the file system changes introduced in version 6.3~testoverlayfs are present 0.731
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.371
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.536
When the network is plugged 0.106
And Tor is ready 20.653
Then the Upgrader considers the system as up-to-date 0.330
# 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 18.355
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.637
After features/support/hooks.rb:335 1.335
After features/support/hooks.rb:105 0.070
43.975
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.756
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.458
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.463
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.004
After features/support/hooks.rb:335 1.370
After features/support/hooks.rb:105 0.000