Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 110 03 Jul 2025, 20:51

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 22:19.912 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:28.837
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 33.622
When I start Tails from USB drive "old" with network unplugged 1:48.093
Then the boot device has safe access rights 4.390
And Tails is running from USB drive "old" 0.753
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:335 8.238
After features/support/hooks.rb:105 0.008
Tags: @product
2:28.525
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:40.994
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 36.048
And I take note of which tps features are available 2.621
Then a Tails persistence partition exists on USB drive "old" 0.867
And I shutdown Tails and wait for the computer to power off 7.442
After features/support/hooks.rb:335 1.276
After features/support/hooks.rb:105 0.295
Tags: @product
3:27.337
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.263
Given a computer 0.660
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.999
Then Tails is running from USB drive "old" 1.821
And all tps features are active 3.549
When I write some files expected to persist 2.224
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.583
And all persistent directories from the old Tails version have safe access rights 2.823
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 6.552
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 30.396
After features/support/hooks.rb:335 0.129
After features/support/hooks.rb:105 0.010
Tags: @product
2:50.287
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 without a persistent partition and stopped at Tails Greeter's login screen 9.765
And I log in to a new session 24.531
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.589
And I plug USB drive "to_upgrade" 2.687
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.432
Then the running Tails is installed on USB drive "to_upgrade" 31.864
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:335 3.491
After features/support/hooks.rb:105 0.000
Tags: @product
2:43.417
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.014
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:30.840
Then all tps features from the old Tails version are active 2.114
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 4.487
And the expected persistent files created with the old Tails version are present in the filesystem 2.455
And all persistent directories from the old Tails version have safe access rights 2.987
After features/support/hooks.rb:335 1.763
After features/support/hooks.rb:105 0.019
Tags: @product @automatic_upgrade
7:37.482
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 13.664
And no SquashFS delta is installed 0.572
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.756
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.454
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.598
When the network is plugged 0.071
And Tor is ready 21.988
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.910
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.958
Given I shutdown Tails and wait for the computer to power off 11.247
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.066
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.536
And the file system changes introduced in version 6.2~testoverlayfs are present 0.381
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.412
When the network is plugged 0.195
And Tor is ready 17.751
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.950
Given I shutdown Tails and wait for the computer to power off 6.654
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.938
Then Tails is running version 6.3~testoverlayfs 0.166
And all tps features are active 2.933
And the file system changes introduced in version 6.3~testoverlayfs are present 0.882
And only the 6.3~testoverlayfs SquashFS delta is installed 0.123
# 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.411
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.420
When the network is plugged 0.136
And Tor is ready 19.305
Then the Upgrader considers the system as up-to-date 0.310
# 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 19.055
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.805
After features/support/hooks.rb:335 0.724
After features/support/hooks.rb:105 0.038
Tags: @product @automatic_upgrade
44.025
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 11.898
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.935
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.241
But a current signing key is available on our website 0.000
When the network is plugged 0.392
And Tor is ready 23.153
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.337
After features/support/hooks.rb:335 1.119
After features/support/hooks.rb:105 0.000