Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 83 04 Jun 2025, 20:16

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:14.358 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:17.920
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.240
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.763
When I start Tails from USB drive "old" with network unplugged 1:40.743
Then the boot device has safe access rights 3.031
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:335 7.078
After features/support/hooks.rb:105 0.008
Tags: @product
2:13.003
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.629
And I start Tails from USB drive "old" with network unplugged and I login 1:27.926
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 31.554
And I take note of which tps features are available 2.654
Then a Tails persistence partition exists on USB drive "old" 0.924
And I shutdown Tails and wait for the computer to power off 8.938
After features/support/hooks.rb:335 0.245
After features/support/hooks.rb:105 0.010
Tags: @product
3:3.801
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.573
Then Tails is running from USB drive "old" 0.618
And all tps features are active 2.112
When I write some files expected to persist 1.813
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.710
And I take note of which tps features are available 0.426
And I shutdown Tails and wait for the computer to power off 4.508
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.203
After features/support/hooks.rb:335 0.131
After features/support/hooks.rb:105 0.008
Tags: @product
2:44.135
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.095
And I log in to a new session 20.825
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.744
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.743
Then the running Tails is installed on USB drive "to_upgrade" 29.421
And I unplug USB drive "to_upgrade" 0.449
And I unplug USB drive "__internal" 0.431
After features/support/hooks.rb:335 2.745
After features/support/hooks.rb:105 0.000
Tags: @product
2:21.161
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.309
Then all tps features from the old Tails version are active 2.638
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 3.636
And the expected persistent files created with the old Tails version are present in the filesystem 1.436
And all persistent directories from the old Tails version have safe access rights 2.539
After features/support/hooks.rb:335 1.441
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
8:49.350
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 13.890
And no SquashFS delta is installed 0.355
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.672
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.614
When the network is plugged 0.100
And Tor is ready 23.528
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.322
Given I shutdown Tails and wait for the computer to power off 1:29.033
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.892
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.669
And the file system changes introduced in version 6.2~testoverlayfs are present 0.402
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.449
# 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.489
When the network is plugged 0.091
And Tor is ready 47.900
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.732
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.305
Given I shutdown Tails and wait for the computer to power off 4.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.436
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.818
And the file system changes introduced in version 6.3~testoverlayfs are present 0.651
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.375
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.381
When the network is plugged 0.083
And Tor is ready 19.965
Then the Upgrader considers the system as up-to-date 0.454
# 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 17.330
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.729
After features/support/hooks.rb:335 0.751
After features/support/hooks.rb:105 0.019
Tags: @product @automatic_upgrade
44.987
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.975
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.722
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 0.162
But a current signing key is available on our website 0.000
When the network is plugged 0.527
And Tor is ready 22.374
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.110
After features/support/hooks.rb:335 0.933
After features/support/hooks.rb:105 0.000