Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 42 27 Apr 2025, 18:34

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:34.613 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:6.440
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 36.210
When I start Tails from USB drive "old" with network unplugged 1:24.443
Then the boot device has safe access rights 3.386
And Tails is running from USB drive "old" 0.399
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:335 7.281
After features/support/hooks.rb:105 0.009
Tags: @product
2:9.110
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login 1:27.229
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 32.216
And I take note of which tps features are available 1.768
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 6.424
After features/support/hooks.rb:335 0.136
After features/support/hooks.rb:105 0.010
Tags: @product
2:53.165
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.642
Then Tails is running from USB drive "old" 1.308
And all tps features are active 2.369
When I write some files expected to persist 2.958
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.377
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.272
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.977
After features/support/hooks.rb:335 0.106
After features/support/hooks.rb:105 0.008
Tags: @product
2:47.412
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 29.580
And I log in to a new session 19.641
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.781
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.720
Then the running Tails is installed on USB drive "to_upgrade" 20.821
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:335 2.527
After features/support/hooks.rb:105 0.000
Tags: @product
2:27.139
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.157
Then all tps features from the old Tails version are active 1.928
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.380
And the expected persistent files created with the old Tails version are present in the filesystem 1.568
And all persistent directories from the old Tails version have safe access rights 2.542
After features/support/hooks.rb:335 1.728
After features/support/hooks.rb:105 0.007
Tags: @product @automatic_upgrade
6:35.257
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 11.636
And no SquashFS delta is installed 0.300
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.071
And Tor is ready 21.188
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.567
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.128
Given I shutdown Tails and wait for the computer to power off 8.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.748
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.113
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.336
When the network is plugged 0.078
And Tor is ready 18.589
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.627
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.161
Given I shutdown Tails and wait for the computer to power off 4.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.389
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.298
And the file system changes introduced in version 6.3~testoverlayfs are present 0.447
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.084
And Tor is ready 18.227
Then the Upgrader considers the system as up-to-date 10.901
# 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.311
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.732
After features/support/hooks.rb:335 0.652
After features/support/hooks.rb:105 0.015
Tags: @product @automatic_upgrade
36.089
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.405
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 18.546
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.472
After features/support/hooks.rb:335 0.753
After features/support/hooks.rb:105 0.000