Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 44 29 Apr 2025, 19:58

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:25.996 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.621
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.478
When I start Tails from USB drive "old" with network unplugged 1:46.502
Then the boot device has safe access rights 3.271
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:335 7.131
After features/support/hooks.rb:105 0.007
Tags: @product
2:13.793
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:29.535
Then Tails is running from USB drive "old" 0.403
And I create a persistent partition 32.222
And I take note of which tps features are available 1.903
Then a Tails persistence partition exists on USB drive "old" 1.001
And I shutdown Tails and wait for the computer to power off 8.552
After features/support/hooks.rb:335 0.201
After features/support/hooks.rb:105 0.010
Tags: @product
3:15.103
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.931
Then Tails is running from USB drive "old" 0.476
And all tps features are active 2.722
When I write some files expected to persist 2.324
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.501
And all persistent directories from the old Tails version have safe access rights 2.893
And I take note of which tps features are available 0.673
And I shutdown Tails and wait for the computer to power off 4.866
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.213
After features/support/hooks.rb:335 0.156
After features/support/hooks.rb:105 0.010
Tags: @product
2:47.920
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 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 16.633
And I log in to a new session 19.478
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.247
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.950
Then the running Tails is installed on USB drive "to_upgrade" 24.706
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:335 1.127
After features/support/hooks.rb:105 0.000
Tags: @product
2:31.121
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.662
Then all tps features from the old Tails version are active 1.693
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.880
And the expected persistent files created with the old Tails version are present in the filesystem 1.599
And all persistent directories from the old Tails version have safe access rights 2.729
After features/support/hooks.rb:335 1.424
After features/support/hooks.rb:105 0.012
Tags: @product @automatic_upgrade
8:33.105
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 12.451
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.507
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.073
And Tor is ready 20.191
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.955
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.461
Given I shutdown Tails and wait for the computer to power off 1:28.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.053
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.704
And the file system changes introduced in version 6.2~testoverlayfs are present 0.396
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.372
# 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.326
When the network is plugged 0.091
And Tor is ready 47.552
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.628
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.696
Given I shutdown Tails and wait for the computer to power off 4.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.413
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.319
And the file system changes introduced in version 6.3~testoverlayfs are present 0.545
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.409
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.070
And Tor is ready 18.266
Then the Upgrader considers the system as up-to-date 0.323
# 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.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.519
After features/support/hooks.rb:335 0.753
After features/support/hooks.rb:105 0.020
Tags: @product @automatic_upgrade
39.330
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 10.779
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 21.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.895
After features/support/hooks.rb:335 2.443
After features/support/hooks.rb:105 0.000