Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 79 31 May 2025, 18:23

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 18:31.142 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
1:52.765
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.019
When I start Tails from USB drive "old" with network unplugged 1:17.734
Then the boot device has safe access rights 2.810
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.095
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.376
After features/support/hooks.rb:105 0.008
Tags: @product
2:12.590
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.180
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.352
And I create a persistent partition 29.810
And I take note of which tps features are available 2.291
Then a Tails persistence partition exists on USB drive "old" 0.716
And I shutdown Tails and wait for the computer to power off 8.237
After features/support/hooks.rb:335 0.196
After features/support/hooks.rb:105 0.010
Tags: @product
2:46.978
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.240
Then Tails is running from USB drive "old" 0.347
And all tps features are active 1.970
When I write some files expected to persist 1.701
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 2.761
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.753
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.925
After features/support/hooks.rb:335 0.158
After features/support/hooks.rb:105 0.008
Tags: @product
2:30.293
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 without a persistent partition and stopped at Tails Greeter's login screen 10.070
And I log in to a new session 18.658
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.599
And I plug USB drive "to_upgrade" 2.354
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.852
Then the running Tails is installed on USB drive "to_upgrade" 23.340
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:335 1.915
After features/support/hooks.rb:105 0.000
Tags: @product
2:10.920
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.915
Then all tps features from the old Tails version are active 1.478
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.320
And the expected persistent files created with the old Tails version are present in the filesystem 1.395
And all persistent directories from the old Tails version have safe access rights 2.302
After features/support/hooks.rb:335 1.111
After features/support/hooks.rb:105 0.008
Tags: @product @automatic_upgrade
6:21.955
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 10.983
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.681
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.521
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.079
And Tor is ready 21.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.558
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.877
Given I shutdown Tails and wait for the computer to power off 8.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.396
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.409
# 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.321
When the network is plugged 0.068
And Tor is ready 17.319
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.505
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.750
Given I shutdown Tails and wait for the computer to power off 4.274
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.677
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.952
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.084
And Tor is ready 19.839
Then the Upgrader considers the system as up-to-date 0.303
# 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.110
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.161
After features/support/hooks.rb:335 0.747
After features/support/hooks.rb:105 0.017
Tags: @product @automatic_upgrade
35.637
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.297
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.795
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
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.069
And Tor is ready 17.763
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.512
After features/support/hooks.rb:335 2.860
After features/support/hooks.rb:105 0.000