Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 55 08 May 2025, 19:40

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:32.887 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:0.791
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.225
When I start Tails from USB drive "old" with network unplugged 1:24.212
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:335 3.784
After features/support/hooks.rb:105 0.007
Tags: @product
2:15.013
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:32.840
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 30.851
And I take note of which tps features are available 1.710
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.271
After features/support/hooks.rb:335 0.200
After features/support/hooks.rb:105 0.009
Tags: @product
2:52.656
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.877
Then Tails is running from USB drive "old" 0.471
And all tps features are active 2.018
When I write some files expected to persist 2.207
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.721
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 6.233
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.852
After features/support/hooks.rb:335 0.146
After features/support/hooks.rb:105 0.009
Tags: @product
2:33.683
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 10.344
And I log in to a new session 20.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.188
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.532
Then the running Tails is installed on USB drive "to_upgrade" 24.279
And I unplug USB drive "to_upgrade" 0.485
And I unplug USB drive "__internal" 0.382
After features/support/hooks.rb:335 6.737
After features/support/hooks.rb:105 0.000
Tags: @product
2:16.940
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:6.748
Then all tps features from the old Tails version are active 1.748
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.793
And the expected persistent files created with the old Tails version are present in the filesystem 1.524
And all persistent directories from the old Tails version have safe access rights 2.576
After features/support/hooks.rb:335 1.589
After features/support/hooks.rb:105 0.011
Tags: @product @automatic_upgrade
6:53.626
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 13.627
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.396
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.076
And Tor is ready 22.769
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.433
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.925
Given I shutdown Tails and wait for the computer to power off 8.977
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.325
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.313
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.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.392
# 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.342
When the network is plugged 0.070
And Tor is ready 17.261
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.784
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.289
Given I shutdown Tails and wait for the computer to power off 4.409
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.418
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.259
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.362
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.065
And Tor is ready 18.363
Then the Upgrader considers the system as up-to-date 0.299
# 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.390
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.686
After features/support/hooks.rb:335 0.826
After features/support/hooks.rb:105 0.063
Tags: @product @automatic_upgrade
40.176
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 with a persistent partition enabled and logged in 12.224
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.126
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 19.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.987
After features/support/hooks.rb:335 0.714
After features/support/hooks.rb:105 0.000