Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 85 06 Jun 2025, 19:08

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:52.946 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:45.694
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.275
And I create a 7200 MiB disk named "old" 0.091
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 58.447
When I start Tails from USB drive "old" with network unplugged 1:41.251
Then the boot device has safe access rights 3.467
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:335 6.921
After features/support/hooks.rb:105 0.008
Tags: @product
2:28.462
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.307
And I start Tails from USB drive "old" with network unplugged and I login 1:42.749
Then Tails is running from USB drive "old" 0.416
And I create a persistent partition 32.214
And I take note of which tps features are available 2.744
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 9.140
After features/support/hooks.rb:335 0.227
After features/support/hooks.rb:105 0.010
Tags: @product
3:4.138
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.772
Then Tails is running from USB drive "old" 0.441
And all tps features are active 2.312
When I write some files expected to persist 1.650
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.512
And all persistent directories from the old Tails version have safe access rights 2.896
And I take note of which tps features are available 0.603
And I shutdown Tails and wait for the computer to power off 6.557
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.935
After features/support/hooks.rb:335 0.165
After features/support/hooks.rb:105 0.011
Tags: @product
2:56.976
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 without a persistent partition and stopped at Tails Greeter's login screen 22.980
And I log in to a new session 20.487
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.792
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.269
Then the running Tails is installed on USB drive "to_upgrade" 28.411
And I unplug USB drive "to_upgrade" 0.262
And I unplug USB drive "__internal" 0.278
After features/support/hooks.rb:335 2.362
After features/support/hooks.rb:105 0.000
Tags: @product
2:33.483
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.295
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.137
Then all tps features from the old Tails version are active 2.129
And Tails is running from USB drive "to_upgrade" 0.482
And the boot device has safe access rights 3.379
And the expected persistent files created with the old Tails version are present in the filesystem 1.406
And all persistent directories from the old Tails version have safe access rights 2.653
After features/support/hooks.rb:335 2.142
After features/support/hooks.rb:105 0.013
Tags: @product @automatic_upgrade
8:25.852
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 14.932
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.408
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.736
When the network is plugged 0.190
And Tor is ready 20.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.793
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.406
Given I shutdown Tails and wait for the computer to power off 1:31.472
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.883
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.988
And the file system changes introduced in version 6.2~testoverlayfs are present 0.482
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.399
# 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.503
When the network is plugged 0.511
And Tor is ready 17.901
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.941
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.142
Given I shutdown Tails and wait for the computer to power off 6.562
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.765
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.281
And the file system changes introduced in version 6.3~testoverlayfs are present 0.590
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.373
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.426
When the network is plugged 0.083
And Tor is ready 18.759
Then the Upgrader considers the system as up-to-date 10.912
# 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 16.657
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.161
After features/support/hooks.rb:335 0.738
After features/support/hooks.rb:105 0.043
Tags: @product @automatic_upgrade
38.338
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 10.425
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.089
And the signing key used by the Upgrader is outdated 0.115
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 20.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.090
After features/support/hooks.rb:335 1.579
After features/support/hooks.rb:105 0.000