Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 51 05 May 2025, 18:52

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:36.252 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:19.331
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.090
And I write an old version of the Tails USB image to disk "old" 33.187
When I start Tails from USB drive "old" with network unplugged 1:40.264
Then the boot device has safe access rights 3.362
And Tails is running from USB drive "old" 0.490
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:335 3.764
After features/support/hooks.rb:105 0.008
Tags: @product
2:18.365
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:31.095
Then Tails is running from USB drive "old" 0.446
And I create a persistent partition 32.895
And I take note of which tps features are available 2.600
Then a Tails persistence partition exists on USB drive "old" 0.935
And I shutdown Tails and wait for the computer to power off 10.157
After features/support/hooks.rb:335 0.196
After features/support/hooks.rb:105 0.012
Tags: @product
3:25.272
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.315
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:40.996
Then Tails is running from USB drive "old" 0.432
And all tps features are active 3.265
When I write some files expected to persist 2.256
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.338
And all persistence configuration files have safe access rights 0.641
And all persistent directories from the old Tails version have safe access rights 3.598
And I take note of which tps features are available 0.600
And I shutdown Tails and wait for the computer to power off 6.727
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.100
After features/support/hooks.rb:335 0.171
After features/support/hooks.rb:105 0.011
Tags: @product
2:52.420
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 11.407
And I log in to a new session 22.112
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.161
And I plug USB drive "to_upgrade" 2.670
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.279
Then the running Tails is installed on USB drive "to_upgrade" 30.301
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:335 3.618
After features/support/hooks.rb:105 0.000
Tags: @product
2:33.386
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given a computer 0.274
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.798
Then all tps features from the old Tails version are active 1.937
And Tails is running from USB drive "to_upgrade" 0.493
And the boot device has safe access rights 4.181
And the expected persistent files created with the old Tails version are present in the filesystem 1.769
And all persistent directories from the old Tails version have safe access rights 2.931
After features/support/hooks.rb:335 1.188
After features/support/hooks.rb:105 0.010
Tags: @product @automatic_upgrade
7:25.759
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 30.609
And no SquashFS delta is installed 0.276
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.576
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.102
And Tor is ready 23.112
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.013
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.591
Given I shutdown Tails and wait for the computer to power off 9.732
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.863
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.789
And the file system changes introduced in version 6.2~testoverlayfs are present 0.386
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.386
When the network is plugged 0.073
And Tor is ready 23.360
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.517
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.036
Given I shutdown Tails and wait for the computer to power off 6.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.641
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.635
And the file system changes introduced in version 6.3~testoverlayfs are present 0.623
And only the 6.3~testoverlayfs SquashFS delta is installed 0.114
# 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.418
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.408
When the network is plugged 0.107
And Tor is ready 20.214
Then the Upgrader considers the system as up-to-date 0.384
# 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 17.470
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.977
After features/support/hooks.rb:335 0.903
After features/support/hooks.rb:105 0.039
Tags: @product @automatic_upgrade
41.716
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.989
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.736
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the signing key used by the Upgrader is outdated 0.159
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 21.155
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.478
After features/support/hooks.rb:335 0.770
After features/support/hooks.rb:105 0.000