Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 81 02 Jun 2025, 21:44

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 21: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:24.961
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 35.160
When I start Tails from USB drive "old" with network unplugged 1:43.666
Then the boot device has safe access rights 3.518
And Tails is running from USB drive "old" 0.428
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.376
And I unplug USB drive "old" 0.260
After features/support/hooks.rb:335 3.610
After features/support/hooks.rb:105 0.029
Tags: @product
2:19.131
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.513
And I start Tails from USB drive "old" with network unplugged and I login 1:33.797
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 34.936
And I take note of which tps features are available 1.946
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 6.756
After features/support/hooks.rb:335 0.149
After features/support/hooks.rb:105 0.009
Tags: @product
3:25.368
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:46.246
Then Tails is running from USB drive "old" 0.845
And all tps features are active 2.473
When I write some files expected to persist 1.927
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.285
And all persistence configuration files have safe access rights 0.567
And all persistent directories from the old Tails version have safe access rights 3.206
And I take note of which tps features are available 0.667
And I shutdown Tails and wait for the computer to power off 4.128
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.744
After features/support/hooks.rb:335 0.144
After features/support/hooks.rb:105 0.010
Tags: @product
2:49.693
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 20.262
And I log in to a new session 21.004
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.998
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.512
Then the running Tails is installed on USB drive "to_upgrade" 27.992
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:335 2.106
After features/support/hooks.rb:105 0.000
Tags: @product
2:22.326
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.152
Then all tps features from the old Tails version are active 1.800
And Tails is running from USB drive "to_upgrade" 0.423
And the boot device has safe access rights 3.690
And the expected persistent files created with the old Tails version are present in the filesystem 1.496
And all persistent directories from the old Tails version have safe access rights 2.534
After features/support/hooks.rb:335 1.290
After features/support/hooks.rb:105 0.008
Tags: @product @automatic_upgrade
7:8.574
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 13.007
And no SquashFS delta is installed 0.268
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.658
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.484
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.066
And Tor is ready 24.171
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.747
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.799
Given I shutdown Tails and wait for the computer to power off 11.288
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.147
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.341
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.286
When the network is plugged 0.118
And Tor is ready 20.981
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.841
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.223
Given I shutdown Tails and wait for the computer to power off 4.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.038
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.149
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.074
And Tor is ready 16.627
Then the Upgrader considers the system as up-to-date 0.340
# 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.385
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.628
After features/support/hooks.rb:335 0.951
After features/support/hooks.rb:105 0.020
Tags: @product @automatic_upgrade
40.735
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 11.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.135
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 20.675
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.310
After features/support/hooks.rb:335 1.619
After features/support/hooks.rb:105 0.000