Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 67 20 May 2025, 19:01

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:29.714 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:14.431
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 34.492
When I start Tails from USB drive "old" with network unplugged 1:34.857
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:335 3.564
After features/support/hooks.rb:105 0.008
Tags: @product
2:22.002
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.303
And I start Tails from USB drive "old" with network unplugged and I login 1:38.979
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 30.602
And I take note of which tps features are available 2.560
Then a Tails persistence partition exists on USB drive "old" 0.763
And I shutdown Tails and wait for the computer to power off 8.386
After features/support/hooks.rb:335 0.263
After features/support/hooks.rb:105 0.010
Tags: @product
2:59.829
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.168
Then Tails is running from USB drive "old" 0.387
And all tps features are active 2.178
When I write some files expected to persist 1.854
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.419
And I take note of which tps features are available 0.477
And I shutdown Tails and wait for the computer to power off 4.384
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.106
After features/support/hooks.rb:335 0.130
After features/support/hooks.rb:105 0.007
Tags: @product
2:27.900
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 9.582
And I log in to a new session 18.201
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.377
And I plug USB drive "to_upgrade" 2.508
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.340
Then the running Tails is installed on USB drive "to_upgrade" 21.468
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:335 3.503
After features/support/hooks.rb:105 0.000
Tags: @product
2:15.268
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.152
Then all tps features from the old Tails version are active 1.855
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.599
And the expected persistent files created with the old Tails version are present in the filesystem 1.455
And all persistent directories from the old Tails version have safe access rights 2.680
After features/support/hooks.rb:335 0.744
After features/support/hooks.rb:105 0.010
Tags: @product @automatic_upgrade
6:30.938
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 12.358
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
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.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.111
And Tor is ready 18.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.103
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.199
Given I shutdown Tails and wait for the computer to power off 8.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.829
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.115
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.267
When the network is plugged 0.082
And Tor is ready 20.391
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.366
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.506
Given I shutdown Tails and wait for the computer to power off 4.233
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.755
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.374
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.074
And Tor is ready 20.106
Then the Upgrader considers the system as up-to-date 0.350
# 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.996
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.147
After features/support/hooks.rb:335 0.756
After features/support/hooks.rb:105 0.024
Tags: @product @automatic_upgrade
39.342
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 10.339
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.307
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 20.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.493
After features/support/hooks.rb:335 0.909
After features/support/hooks.rb:105 0.000