Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 71 24 May 2025, 18:24

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:10.349 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.866
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 28.852
When I start Tails from USB drive "old" with network unplugged 1:25.680
Then the boot device has safe access rights 3.030
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:335 6.895
After features/support/hooks.rb:105 0.007
Tags: @product
2:4.480
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:22.262
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 30.774
And I take note of which tps features are available 1.945
Then a Tails persistence partition exists on USB drive "old" 0.722
And I shutdown Tails and wait for the computer to power off 8.224
After features/support/hooks.rb:335 0.179
After features/support/hooks.rb:105 0.008
Tags: @product
2:51.511
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.725
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.100
When I write some files expected to persist 1.698
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 2.312
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.305
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.877
After features/support/hooks.rb:335 0.086
After features/support/hooks.rb:105 0.008
Tags: @product
2:36.093
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 11.043
And I log in to a new session 19.553
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.099
Then the running Tails is installed on USB drive "to_upgrade" 24.902
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:335 4.079
After features/support/hooks.rb:105 0.000
Tags: @product
2:17.114
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.238
Then all tps features from the old Tails version are active 1.653
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.127
And the expected persistent files created with the old Tails version are present in the filesystem 1.589
And all persistent directories from the old Tails version have safe access rights 3.003
After features/support/hooks.rb:335 1.328
After features/support/hooks.rb:105 0.008
Tags: @product @automatic_upgrade
6:45.429
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.832
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.530
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.145
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.530
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.079
And Tor is ready 22.922
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.322
Given I shutdown Tails and wait for the computer to power off 8.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.373
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.215
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.268
When the network is plugged 0.080
And Tor is ready 20.766
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.879
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.991
Given I shutdown Tails and wait for the computer to power off 4.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.021
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.008
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.265
When the network is plugged 0.076
And Tor is ready 18.244
Then the Upgrader considers the system as up-to-date 10.764
# 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.284
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.313
After features/support/hooks.rb:335 0.704
After features/support/hooks.rb:105 0.018
Tags: @product @automatic_upgrade
35.855
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 with a persistent partition enabled and logged in 9.923
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.130
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 17.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.956
After features/support/hooks.rb:335 0.748
After features/support/hooks.rb:105 0.000