Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 2 27 Mar 2025, 20:35

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:12.165 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:25.277
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 36.273
When I start Tails from USB drive "old" with network unplugged 1:43.129
Then the boot device has safe access rights 3.365
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.132
And udev-watchdog is monitoring the correct device 0.383
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.776
After features/support/hooks.rb:100 0.010
Tags: @product
2:21.838
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login 1:34.920
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 34.774
And I take note of which tps features are available 2.026
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 8.579
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.014
Tags: @product
3:4.907
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.338
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.954
Then Tails is running from USB drive "old" 0.503
And all tps features are active 2.704
When I write some files expected to persist 2.025
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 3.100
And I take note of which tps features are available 0.536
And I shutdown Tails and wait for the computer to power off 6.465
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.541
After features/support/hooks.rb:330 0.114
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.450
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.266
And I log in to a new session 19.170
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.992
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.404
Then the running Tails is installed on USB drive "to_upgrade" 28.785
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 2.293
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.804
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:31.554
Then all tps features from the old Tails version are active 1.932
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.446
And the expected persistent files created with the old Tails version are present in the filesystem 1.609
And all persistent directories from the old Tails version have safe access rights 2.664
After features/support/hooks.rb:330 1.456
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
7:17.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.679
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.457
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.545
When the network is plugged 0.077
And Tor is ready 23.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.544
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.674
Given I shutdown Tails and wait for the computer to power off 9.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.564
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.308
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.326
# 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.306
When the network is plugged 0.075
And Tor is ready 47.988
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.568
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.272
Given I shutdown Tails and wait for the computer to power off 4.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.869
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.181
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.078
And Tor is ready 20.601
Then the Upgrader considers the system as up-to-date 0.320
# 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.883
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.796
After features/support/hooks.rb:330 1.254
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
41.367
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.992
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.129
And the signing key used by the Upgrader is outdated 0.114
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 23.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.282
After features/support/hooks.rb:330 1.147
After features/support/hooks.rb:100 0.000