Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 52 06 May 2025, 17:22

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 22:31.033 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:45.466
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.246
And I create a 7200 MiB disk named "old" 0.078
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 1:4.846
When I start Tails from USB drive "old" with network unplugged 1:34.450
Then the boot device has safe access rights 3.677
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:335 7.217
After features/support/hooks.rb:105 0.008
Tags: @product
2:22.662
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login 1:33.182
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 35.971
And I take note of which tps features are available 2.794
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 9.226
After features/support/hooks.rb:335 0.263
After features/support/hooks.rb:105 0.010
Tags: @product
3:16.720
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.014
Given a computer 0.315
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.732
Then Tails is running from USB drive "old" 1.514
And all tps features are active 2.818
When I write some files expected to persist 3.363
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.310
And all persistence configuration files have safe access rights 0.507
And all persistent directories from the old Tails version have safe access rights 2.917
And I take note of which tps features are available 0.771
And I shutdown Tails and wait for the computer to power off 6.798
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.670
After features/support/hooks.rb:335 0.148
After features/support/hooks.rb:105 0.012
Tags: @product
2:49.467
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 15.561
And I log in to a new session 25.202
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.799
And I plug USB drive "to_upgrade" 2.531
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.682
Then the running Tails is installed on USB drive "to_upgrade" 27.221
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:335 2.320
After features/support/hooks.rb:105 0.000
Tags: @product
2:25.803
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.216
Then all tps features from the old Tails version are active 1.943
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.584
And the expected persistent files created with the old Tails version are present in the filesystem 1.748
And all persistent directories from the old Tails version have safe access rights 2.779
After features/support/hooks.rb:335 1.531
After features/support/hooks.rb:105 0.008
8:0.108
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 29.616
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.521
When the network is plugged 0.072
And Tor is ready 23.640
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.599
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.326
Given I shutdown Tails and wait for the computer to power off 8.804
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.017
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.462
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.351
When the network is plugged 0.078
And Tor is ready 19.986
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.046
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.928
Given I shutdown Tails and wait for the computer to power off 4.797
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.124
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.486
And the file system changes introduced in version 6.3~testoverlayfs are present 0.589
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.160
And Tor is ready 47.558
Then the Upgrader considers the system as up-to-date 0.393
# 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 18.205
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.946
After features/support/hooks.rb:335 1.224
After features/support/hooks.rb:105 0.038
50.804
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.030
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.562
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the signing key used by the Upgrader is outdated 0.132
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 25.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.255
After features/support/hooks.rb:335 1.339
After features/support/hooks.rb:105 0.000