Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 64 17 May 2025, 18: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:45.639 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:29.399
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 56.720
When I start Tails from USB drive "old" with network unplugged 1:27.586
Then the boot device has safe access rights 2.842
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:335 6.805
After features/support/hooks.rb:105 0.009
Tags: @product
2:15.766
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:30.969
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 32.745
And I take note of which tps features are available 2.528
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.202
After features/support/hooks.rb:335 0.206
After features/support/hooks.rb:105 0.009
Tags: @product
3:4.441
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.449
Then Tails is running from USB drive "old" 0.325
And all tps features are active 2.102
When I write some files expected to persist 1.729
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 2.573
And I take note of which tps features are available 0.387
And I shutdown Tails and wait for the computer to power off 6.645
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.444
After features/support/hooks.rb:335 0.154
After features/support/hooks.rb:105 0.008
Tags: @product
2:27.151
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.514
And I log in to a new session 17.984
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.515
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.968
Then the running Tails is installed on USB drive "to_upgrade" 18.348
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:335 3.724
After features/support/hooks.rb:105 0.000
Tags: @product
2:21.464
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.372
Then all tps features from the old Tails version are active 1.592
And Tails is running from USB drive "to_upgrade" 0.492
And the boot device has safe access rights 3.028
And the expected persistent files created with the old Tails version are present in the filesystem 1.378
And all persistent directories from the old Tails version have safe access rights 2.407
After features/support/hooks.rb:335 1.451
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
6:29.188
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.756
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.773
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.069
And Tor is ready 20.580
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.021
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.782
Given I shutdown Tails and wait for the computer to power off 8.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.830
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.234
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.273
When the network is plugged 0.100
And Tor is ready 19.857
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.678
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.838
Given I shutdown Tails and wait for the computer to power off 4.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.280
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.225
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.073
And Tor is ready 18.848
Then the Upgrader considers the system as up-to-date 0.402
# 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 16.096
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.937
After features/support/hooks.rb:335 0.826
After features/support/hooks.rb:105 0.018
Tags: @product @automatic_upgrade
38.227
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 10.537
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the signing key used by the Upgrader is outdated 0.135
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 20.675
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.357
After features/support/hooks.rb:335 1.589
After features/support/hooks.rb:105 0.000