Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 75 27 May 2025, 21: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 19:22.060 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.316
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.198
When I start Tails from USB drive "old" with network unplugged 1:27.764
Then the boot device has safe access rights 4.034
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:335 7.168
After features/support/hooks.rb:105 0.007
Tags: @product
2:10.113
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:26.517
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 31.891
And I take note of which tps features are available 2.017
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 8.374
After features/support/hooks.rb:335 0.144
After features/support/hooks.rb:105 0.007
Tags: @product
3:3.921
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.709
Then Tails is running from USB drive "old" 1.271
And all tps features are active 1.798
When I write some files expected to persist 1.683
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.496
And I take note of which tps features are available 0.382
And I shutdown Tails and wait for the computer to power off 8.771
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.001
After features/support/hooks.rb:335 0.148
After features/support/hooks.rb:105 0.008
Tags: @product
2:40.517
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 10.933
And I log in to a new session 20.349
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.078
And I plug USB drive "to_upgrade" 2.699
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.764
Then the running Tails is installed on USB drive "to_upgrade" 28.246
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:335 1.980
After features/support/hooks.rb:105 0.000
Tags: @product
2:18.087
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.420
Then all tps features from the old Tails version are active 1.754
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.489
And the expected persistent files created with the old Tails version are present in the filesystem 1.461
And all persistent directories from the old Tails version have safe access rights 2.466
After features/support/hooks.rb:335 1.433
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
6:23.218
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 12.757
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
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.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.220
And Tor is ready 23.661
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.748
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.171
Given I shutdown Tails and wait for the computer to power off 8.579
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.117
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.337
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.316
When the network is plugged 0.123
And Tor is ready 16.923
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.577
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.795
Given I shutdown Tails and wait for the computer to power off 4.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.369
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.051
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.357
When the network is plugged 0.093
And Tor is ready 17.409
Then the Upgrader considers the system as up-to-date 0.302
# 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 16.277
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.730
After features/support/hooks.rb:335 0.703
After features/support/hooks.rb:105 0.018
Tags: @product @automatic_upgrade
40.885
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 11.395
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.739
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 21.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.882
After features/support/hooks.rb:335 2.123
After features/support/hooks.rb:105 0.000