Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 35 25 Apr 2025, 18:09

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:14.244 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:4.117
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 31.549
When I start Tails from USB drive "old" with network unplugged 1:27.176
Then the boot device has safe access rights 3.067
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.094
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:334 3.789
After features/support/hooks.rb:104 0.009
Tags: @product
2:16.335
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:33.740
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 31.258
And I take note of which tps features are available 1.764
Then a Tails persistence partition exists on USB drive "old" 0.746
And I shutdown Tails and wait for the computer to power off 8.355
After features/support/hooks.rb:334 0.176
After features/support/hooks.rb:104 0.010
Tags: @product
2:59.445
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.222
Then Tails is running from USB drive "old" 0.346
And all tps features are active 1.804
When I write some files expected to persist 1.755
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.938
And I take note of which tps features are available 0.389
And I shutdown Tails and wait for the computer to power off 6.336
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.850
After features/support/hooks.rb:334 0.156
After features/support/hooks.rb:104 0.007
Tags: @product
2:33.518
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.372
And I log in to a new session 21.215
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.775
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.024
Then the running Tails is installed on USB drive "to_upgrade" 24.273
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:334 0.819
After features/support/hooks.rb:104 0.000
Tags: @product
2:17.141
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.941
Then all tps features from the old Tails version are active 1.701
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 3.093
And the expected persistent files created with the old Tails version are present in the filesystem 1.459
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:334 1.259
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
6:27.421
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.773
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.355
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.068
And Tor is ready 19.170
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.815
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.474
Given I shutdown Tails and wait for the computer to power off 8.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.015
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.901
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.140
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.398
# 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.429
When the network is plugged 0.069
And Tor is ready 17.726
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.253
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.236
Given I shutdown Tails and wait for the computer to power off 4.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.925
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.063
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
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.390
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.060
And Tor is ready 19.563
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 14.850
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.559
After features/support/hooks.rb:334 0.727
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
36.264
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.131
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 18.950
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.494
After features/support/hooks.rb:334 0.781
After features/support/hooks.rb:104 0.000