Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 57 10 May 2025, 18:35

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.465 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:20.373
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 35.685
When I start Tails from USB drive "old" with network unplugged 1:39.304
Then the boot device has safe access rights 3.030
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:335 7.147
After features/support/hooks.rb:105 0.021
Tags: @product
2:26.516
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.009
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:42.261
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 32.258
And I take note of which tps features are available 2.437
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.228
After features/support/hooks.rb:335 0.206
After features/support/hooks.rb:105 0.008
Tags: @product
3:15.469
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.302
Then Tails is running from USB drive "old" 0.541
And all tps features are active 2.380
When I write some files expected to persist 1.952
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 3.212
And I take note of which tps features are available 0.608
And I shutdown Tails and wait for the computer to power off 6.848
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.675
After features/support/hooks.rb:335 0.146
After features/support/hooks.rb:105 0.010
Tags: @product
2:32.788
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.958
And I log in to a new session 20.627
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.672
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.493
Then the running Tails is installed on USB drive "to_upgrade" 21.073
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.276
After features/support/hooks.rb:335 1.090
After features/support/hooks.rb:105 0.000
Tags: @product
2:23.721
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.453
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.932
Then all tps features from the old Tails version are active 1.565
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 4.128
And the expected persistent files created with the old Tails version are present in the filesystem 1.701
And all persistent directories from the old Tails version have safe access rights 2.590
After features/support/hooks.rb:335 0.953
After features/support/hooks.rb:105 0.008
Tags: @product @automatic_upgrade
7:34.235
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.869
And no SquashFS delta is installed 0.191
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.080
And Tor is ready 49.547
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.606
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.951
Given I shutdown Tails and wait for the computer to power off 8.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.629
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.261
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.263
When the network is plugged 0.071
And Tor is ready 17.462
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.394
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.436
Given I shutdown Tails and wait for the computer to power off 6.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.061
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.399
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.099
# 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.398
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.357
When the network is plugged 0.087
And Tor is ready 48.105
Then the Upgrader considers the system as up-to-date 0.356
# 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.591
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.968
After features/support/hooks.rb:335 0.693
After features/support/hooks.rb:105 0.015
Tags: @product @automatic_upgrade
37.358
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.335
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
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.072
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 19.090
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.366
After features/support/hooks.rb:335 1.081
After features/support/hooks.rb:105 0.000