Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 19 09 Apr 2025, 19:03

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:9.713 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:8.335
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 37.037
When I start Tails from USB drive "old" with network unplugged 1:25.882
Then the boot device has safe access rights 3.154
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 3.527
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.046
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:23.861
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 31.073
And I take note of which tps features are available 2.265
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.571
After features/support/hooks.rb:330 0.215
After features/support/hooks.rb:100 0.007
Tags: @product
3:5.033
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.143
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.874
Then Tails is running from USB drive "old" 0.325
And all tps features are active 2.192
When I write some files expected to persist 1.642
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.622
And I take note of which tps features are available 0.380
And I shutdown Tails and wait for the computer to power off 6.700
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.506
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.006
Tags: @product
2:36.261
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.283
And I log in to a new session 19.937
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.939
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.641
Then the running Tails is installed on USB drive "to_upgrade" 26.633
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 6.508
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.298
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.147
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.922
Then all tps features from the old Tails version are active 1.609
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.345
And the expected persistent files created with the old Tails version are present in the filesystem 1.295
And all persistent directories from the old Tails version have safe access rights 2.653
After features/support/hooks.rb:330 1.149
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
6:25.115
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.767
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.415
And Tor is ready 22.107
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.487
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.598
Given I shutdown Tails and wait for the computer to power off 9.003
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.472
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.031
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.249
When the network is plugged 0.060
And Tor is ready 20.938
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.342
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.875
Given I shutdown Tails and wait for the computer to power off 4.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.491
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.885
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.083
And Tor is ready 17.439
Then the Upgrader considers the system as up-to-date 0.315
# 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.563
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.564
After features/support/hooks.rb:330 0.808
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
36.621
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.376
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.044
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 18.423
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.860
After features/support/hooks.rb:330 0.907
After features/support/hooks.rb:100 0.000