Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 109 02 Jul 2025, 20:24

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 26:0.917 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:43.351
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.028
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 42.736
When I start Tails from USB drive "old" with network unplugged 1:54.328
Then the boot device has safe access rights 3.870
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:335 3.722
After features/support/hooks.rb:105 0.009
Tags: @product
2:56.340
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:52.735
Then Tails is running from USB drive "old" 0.651
And I create a persistent partition 47.293
And I take note of which tps features are available 3.251
Then a Tails persistence partition exists on USB drive "old" 2.162
And I shutdown Tails and wait for the computer to power off 10.023
After features/support/hooks.rb:335 0.190
After features/support/hooks.rb:105 0.009
Tags: @product
4:18.790
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:18.709
Then Tails is running from USB drive "old" 0.642
And all tps features are active 2.494
When I write some files expected to persist 2.176
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.389
And all persistence configuration files have safe access rights 0.477
And all persistent directories from the old Tails version have safe access rights 8.425
And I take note of which tps features are available 0.972
And I shutdown Tails and wait for the computer to power off 7.492
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 36.804
After features/support/hooks.rb:335 0.162
After features/support/hooks.rb:105 0.009
Tags: @product
3:18.026
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 14.648
And I log in to a new session 28.521
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.533
And I plug USB drive "to_upgrade" 3.832
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.549
Then the running Tails is installed on USB drive "to_upgrade" 37.525
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:335 1.235
After features/support/hooks.rb:105 0.000
Tags: @product
3:1.074
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:45.479
Then all tps features from the old Tails version are active 2.573
And Tails is running from USB drive "to_upgrade" 1.493
And the boot device has safe access rights 6.928
And the expected persistent files created with the old Tails version are present in the filesystem 1.756
And all persistent directories from the old Tails version have safe access rights 2.666
After features/support/hooks.rb:335 1.807
After features/support/hooks.rb:105 0.012
Tags: @product @automatic_upgrade
8:57.089
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.142
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.575
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.562
When the network is plugged 0.097
And Tor is ready 31.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.502
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 22.882
Given I shutdown Tails and wait for the computer to power off 16.092
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.139
Then Tails is running version 6.2~testoverlayfs 0.148
And all tps features are active 4.650
And the file system changes introduced in version 6.2~testoverlayfs are present 0.715
And only the 6.2~testoverlayfs SquashFS delta is installed 0.218
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.538
# 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.625
When the network is plugged 0.083
And Tor is ready 26.370
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.833
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 18.081
Given I shutdown Tails and wait for the computer to power off 7.007
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:42.155
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.339
And the file system changes introduced in version 6.3~testoverlayfs are present 1.075
And only the 6.3~testoverlayfs SquashFS delta is installed 0.663
# 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 1.015
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.957
When the network is plugged 0.679
And Tor is ready 24.058
Then the Upgrader considers the system as up-to-date 0.420
# 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 22.947
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.395
After features/support/hooks.rb:335 0.732
After features/support/hooks.rb:105 0.021
Tags: @product @automatic_upgrade
46.244
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 15.591
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.182
But a current signing key is available on our website 0.000
When the network is plugged 0.200
And Tor is ready 22.029
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.779
After features/support/hooks.rb:335 3.620
After features/support/hooks.rb:105 0.000