Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 47 01 May 2025, 19:49

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:33.564 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
1:59.971
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.174
When I start Tails from USB drive "old" with network unplugged 1:23.374
Then the boot device has safe access rights 3.082
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:335 3.511
After features/support/hooks.rb:105 0.008
Tags: @product
2:14.096
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:26.894
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 32.372
And I take note of which tps features are available 2.927
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 10.479
After features/support/hooks.rb:335 0.203
After features/support/hooks.rb:105 0.009
Tags: @product
3:4.472
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.185
Then Tails is running from USB drive "old" 0.455
And all tps features are active 1.919
When I write some files expected to persist 1.650
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.579
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 6.355
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.114
After features/support/hooks.rb:335 0.151
After features/support/hooks.rb:105 0.009
Tags: @product
2:36.499
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.673
And I log in to a new session 19.170
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.653
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.411
Then the running Tails is installed on USB drive "to_upgrade" 27.635
And I unplug USB drive "to_upgrade" 0.255
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:335 2.440
After features/support/hooks.rb:105 0.000
Tags: @product
2:30.476
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.515
Then all tps features from the old Tails version are active 1.964
And Tails is running from USB drive "to_upgrade" 0.418
And the boot device has safe access rights 3.370
And the expected persistent files created with the old Tails version are present in the filesystem 1.453
And all persistent directories from the old Tails version have safe access rights 2.575
After features/support/hooks.rb:335 1.798
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
6:29.233
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 11.608
And no SquashFS delta is installed 0.379
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.502
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.544
When the network is plugged 0.065
And Tor is ready 22.674
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.772
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.935
Given I shutdown Tails and wait for the computer to power off 8.734
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.835
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.022
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
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.286
# 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.374
When the network is plugged 0.076
And Tor is ready 20.509
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.401
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.136
Given I shutdown Tails and wait for the computer to power off 4.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.251
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.318
When the network is plugged 0.085
And Tor is ready 19.390
Then the Upgrader considers the system as up-to-date 0.313
# 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.140
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.695
After features/support/hooks.rb:335 1.022
After features/support/hooks.rb:105 0.017
Tags: @product @automatic_upgrade
38.814
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 9.647
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 21.749
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.683
After features/support/hooks.rb:335 0.753
After features/support/hooks.rb:105 0.000