Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 41 26 Apr 2025, 18:32

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 19:58.230 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:5.867
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.521
When I start Tails from USB drive "old" with network unplugged 1:27.540
Then the boot device has safe access rights 3.409
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:335 7.135
After features/support/hooks.rb:105 0.008
Tags: @product
2:19.017
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:33.814
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 33.867
And I take note of which tps features are available 1.831
Then a Tails persistence partition exists on USB drive "old" 0.732
And I shutdown Tails and wait for the computer to power off 8.255
After features/support/hooks.rb:335 0.159
After features/support/hooks.rb:105 0.008
Tags: @product
2:56.125
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.852
Then Tails is running from USB drive "old" 1.658
And all tps features are active 2.349
When I write some files expected to persist 2.850
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.484
And I take note of which tps features are available 0.580
And I shutdown Tails and wait for the computer to power off 6.331
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.126
After features/support/hooks.rb:335 0.200
After features/support/hooks.rb:105 0.009
Tags: @product
2:30.320
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 11.674
And I log in to a new session 19.031
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.597
And I plug USB drive "to_upgrade" 2.526
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.671
Then the running Tails is installed on USB drive "to_upgrade" 20.334
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:335 3.005
After features/support/hooks.rb:105 0.000
Tags: @product
2:18.784
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.983
Then all tps features from the old Tails version are active 1.528
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.182
And the expected persistent files created with the old Tails version are present in the filesystem 1.937
And all persistent directories from the old Tails version have safe access rights 2.561
After features/support/hooks.rb:335 1.624
After features/support/hooks.rb:105 0.007
Tags: @product @automatic_upgrade
7:6.811
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 13.512
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.863
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.071
And Tor is ready 21.464
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.584
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.136
Given I shutdown Tails and wait for the computer to power off 8.817
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.866
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.165
And the file system changes introduced in version 6.2~testoverlayfs are present 0.392
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.500
# 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.281
When the network is plugged 0.076
And Tor is ready 19.591
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.587
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.712
Given I shutdown Tails and wait for the computer to power off 6.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.223
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.123
And the file system changes introduced in version 6.3~testoverlayfs are present 0.575
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.085
And Tor is ready 47.192
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 15.722
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.524
After features/support/hooks.rb:335 0.731
After features/support/hooks.rb:105 0.015
Tags: @product @automatic_upgrade
41.303
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.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.757
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.095
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 22.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.678
After features/support/hooks.rb:335 0.881
After features/support/hooks.rb:105 0.000