Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 72 25 May 2025, 18:45

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 19:43.750 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:49.534
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 1:13.659
When I start Tails from USB drive "old" with network unplugged 1:30.177
Then the boot device has safe access rights 3.293
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:335 7.179
After features/support/hooks.rb:105 0.010
Tags: @product
2:14.760
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:31.002
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 31.727
And I take note of which tps features are available 1.839
Then a Tails persistence partition exists on USB drive "old" 0.866
And I shutdown Tails and wait for the computer to power off 8.814
After features/support/hooks.rb:335 0.169
After features/support/hooks.rb:105 0.008
Tags: @product
2:50.215
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.589
Then Tails is running from USB drive "old" 0.409
And all tps features are active 2.936
When I write some files expected to persist 1.672
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.477
And I take note of which tps features are available 0.528
And I shutdown Tails and wait for the computer to power off 4.727
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.061
After features/support/hooks.rb:335 0.105
After features/support/hooks.rb:105 0.009
Tags: @product
2:34.853
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.306
And I log in to a new session 19.297
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.449
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.762
Then the running Tails is installed on USB drive "to_upgrade" 26.173
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:335 1.754
After features/support/hooks.rb:105 0.000
Tags: @product
2:22.341
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.327
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.243
Then all tps features from the old Tails version are active 1.759
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.655
And the expected persistent files created with the old Tails version are present in the filesystem 1.557
And all persistent directories from the old Tails version have safe access rights 2.456
After features/support/hooks.rb:335 1.702
After features/support/hooks.rb:105 0.008
Tags: @product @automatic_upgrade
6:12.949
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.264
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.421
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.607
When the network is plugged 0.074
And Tor is ready 22.786
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.001
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.486
Given I shutdown Tails and wait for the computer to power off 8.673
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.468
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.427
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.310
When the network is plugged 0.071
And Tor is ready 17.362
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.547
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.103
Given I shutdown Tails and wait for the computer to power off 4.264
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.094
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.004
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.074
And Tor is ready 20.257
Then the Upgrader considers the system as up-to-date 0.323
# 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.018
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.875
After features/support/hooks.rb:335 0.753
After features/support/hooks.rb:105 0.017
Tags: @product @automatic_upgrade
39.095
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.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 20.487
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.772
After features/support/hooks.rb:335 0.871
After features/support/hooks.rb:105 0.000