Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 84 05 Jun 2025, 20:37

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:57.152 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:9.569
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 36.075
When I start Tails from USB drive "old" with network unplugged 1:28.242
Then the boot device has safe access rights 2.931
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:335 3.503
After features/support/hooks.rb:105 0.028
Tags: @product
2:8.895
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:26.302
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 33.162
And I take note of which tps features are available 1.768
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 6.323
After features/support/hooks.rb:335 0.202
After features/support/hooks.rb:105 0.012
Tags: @product
2:55.221
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.923
Then Tails is running from USB drive "old" 0.922
And all tps features are active 2.258
When I write some files expected to persist 2.752
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 1.071
And all persistent directories from the old Tails version have safe access rights 2.527
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 6.378
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.496
After features/support/hooks.rb:335 0.106
After features/support/hooks.rb:105 0.008
Tags: @product
2:37.229
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 9.791
And I log in to a new session 18.442
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.817
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.751
Then the running Tails is installed on USB drive "to_upgrade" 26.584
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:335 2.125
After features/support/hooks.rb:105 0.000
Tags: @product
2:14.195
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.380
Then all tps features from the old Tails version are active 1.886
And Tails is running from USB drive "to_upgrade" 1.158
And the boot device has safe access rights 3.395
And the expected persistent files created with the old Tails version are present in the filesystem 1.564
And all persistent directories from the old Tails version have safe access rights 2.607
After features/support/hooks.rb:335 1.423
After features/support/hooks.rb:105 0.026
Tags: @product @automatic_upgrade
7:13.694
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 15.624
And no SquashFS delta is installed 0.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.067
And Tor is ready 24.560
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.178
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.926
Given I shutdown Tails and wait for the computer to power off 11.161
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.605
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.376
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.289
When the network is plugged 0.076
And Tor is ready 17.362
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.034
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.090
Given I shutdown Tails and wait for the computer to power off 4.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.309
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.546
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.073
And Tor is ready 46.407
Then the Upgrader considers the system as up-to-date 0.329
# 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.703
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.646
After features/support/hooks.rb:335 0.883
After features/support/hooks.rb:105 0.014
Tags: @product @automatic_upgrade
38.347
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.470
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.105
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 20.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.760
After features/support/hooks.rb:335 0.913
After features/support/hooks.rb:105 0.000