Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 87 08 Jun 2025, 18:32

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.183 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:8.836
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.890
When I start Tails from USB drive "old" with network unplugged 1:31.679
Then the boot device has safe access rights 2.945
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:335 3.498
After features/support/hooks.rb:105 0.019
Tags: @product
2:14.073
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 "old" with network unplugged and I login 1:32.034
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 30.635
And I take note of which tps features are available 1.579
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.518
After features/support/hooks.rb:335 0.171
After features/support/hooks.rb:105 0.007
Tags: @product
2:51.020
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.580
Then Tails is running from USB drive "old" 0.806
And all tps features are active 1.972
When I write some files expected to persist 2.722
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.485
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.588
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 4.359
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.409
After features/support/hooks.rb:335 0.144
After features/support/hooks.rb:105 0.010
Tags: @product
2:40.190
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.910
And I log in to a new session 20.187
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.600
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.530
Then the running Tails is installed on USB drive "to_upgrade" 30.064
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:335 3.608
After features/support/hooks.rb:105 0.000
Tags: @product
2:14.608
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.707
Then all tps features from the old Tails version are active 1.739
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.585
And the expected persistent files created with the old Tails version are present in the filesystem 1.506
And all persistent directories from the old Tails version have safe access rights 2.505
After features/support/hooks.rb:335 1.335
After features/support/hooks.rb:105 0.010
Tags: @product @automatic_upgrade
6:58.277
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.403
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.447
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.067
And Tor is ready 22.280
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.526
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.965
Given I shutdown Tails and wait for the computer to power off 9.209
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.329
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.211
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.398
When the network is plugged 0.070
And Tor is ready 20.824
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.649
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.937
Given I shutdown Tails and wait for the computer to power off 6.622
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.275
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.181
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.128
# 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.380
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.064
And Tor is ready 19.746
Then the Upgrader considers the system as up-to-date 0.318
# 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.455
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.129
After features/support/hooks.rb:335 0.749
After features/support/hooks.rb:105 0.015
Tags: @product @automatic_upgrade
36.176
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 9.896
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.506
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 0.107
But a current signing key is available on our website 0.000
When the network is plugged 0.887
And Tor is ready 18.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.649
After features/support/hooks.rb:335 0.980
After features/support/hooks.rb:105 0.000