Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 86 07 Jun 2025, 18:31

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.791 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:19.860
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 35.062
When I start Tails from USB drive "old" with network unplugged 1:39.273
Then the boot device has safe access rights 3.193
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:335 7.036
After features/support/hooks.rb:105 0.009
Tags: @product
2:12.700
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:29.050
Then Tails is running from USB drive "old" 0.384
And I create a persistent partition 31.298
And I take note of which tps features are available 2.464
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.466
After features/support/hooks.rb:335 0.149
After features/support/hooks.rb:105 0.008
Tags: @product
3:8.717
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.664
Then Tails is running from USB drive "old" 1.675
And all tps features are active 1.966
When I write some files expected to persist 2.860
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.360
And all persistence configuration files have safe access rights 0.507
And all persistent directories from the old Tails version have safe access rights 2.563
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 6.201
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.215
After features/support/hooks.rb:335 0.165
After features/support/hooks.rb:105 0.009
Tags: @product
2:38.955
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 10.580
And I log in to a new session 22.113
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.712
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.138
Then the running Tails is installed on USB drive "to_upgrade" 26.555
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:335 2.244
After features/support/hooks.rb:105 0.000
Tags: @product
2:20.278
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.149
Then all tps features from the old Tails version are active 1.770
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.685
And the expected persistent files created with the old Tails version are present in the filesystem 1.633
And all persistent directories from the old Tails version have safe access rights 2.499
After features/support/hooks.rb:335 1.467
After features/support/hooks.rb:105 0.019
Tags: @product @automatic_upgrade
6:48.535
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 12.386
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.372
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.603
When the network is plugged 0.097
And Tor is ready 26.470
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.916
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.140
Given I shutdown Tails and wait for the computer to power off 11.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.666
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.016
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.307
When the network is plugged 0.064
And Tor is ready 20.085
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.488
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.200
Given I shutdown Tails and wait for the computer to power off 4.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.553
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.104
And the file system changes introduced in version 6.3~testoverlayfs are present 0.589
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.070
And Tor is ready 19.077
Then the Upgrader considers the system as up-to-date 0.315
# 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.639
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.084
After features/support/hooks.rb:335 1.026
After features/support/hooks.rb:105 0.025
Tags: @product @automatic_upgrade
41.744
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.801
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
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.160
But a current signing key is available on our website 0.000
When the network is plugged 0.131
And Tor is ready 21.961
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.264
After features/support/hooks.rb:335 0.773
After features/support/hooks.rb:105 0.000