Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 99 22 Jun 2025, 19:51

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 83 1 3 0 0 87 6 1 7 25:25.538 Failed
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:49.292
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 41.786
When I start Tails from USB drive "old" with network unplugged 2:0.924
Then the boot device has safe access rights 3.722
And Tails is running from USB drive "old" 0.462
And there is no persistence partition on USB drive "old" 0.111
And process "udev-watchdog" is running 0.133
And udev-watchdog is monitoring the correct device 0.470
And I unplug USB drive "old" 0.337
After features/support/hooks.rb:335 5.681
After features/support/hooks.rb:105 0.242
Tags: @product
2:55.706
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.213
Given a computer 1.074
And I start Tails from USB drive "old" with network unplugged and I login 1:53.543
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 47.621
And I take note of which tps features are available 3.566
Then a Tails persistence partition exists on USB drive "old" 1.111
And I shutdown Tails and wait for the computer to power off 8.432
After features/support/hooks.rb:335 1.909
After features/support/hooks.rb:105 0.075
Tags: @product
3:56.610
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.039
Given a computer 0.474
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:3.970
Then Tails is running from USB drive "old" 2.310
And all tps features are active 3.062
When I write some files expected to persist 1.902
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 3.314
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 8.421
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.906
After features/support/hooks.rb:335 0.145
After features/support/hooks.rb:105 0.009
Tags: @product
3:28.364
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 15.780
And I log in to a new session 24.385
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.559
And I plug USB drive "to_upgrade" 5.143
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.122
Then the running Tails is installed on USB drive "to_upgrade" 37.490
And I unplug USB drive "to_upgrade" 5.525
And I unplug USB drive "__internal" 1.357
After features/support/hooks.rb:335 2.672
After features/support/hooks.rb:105 0.000
Tags: @product
3:5.665
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.320
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:49.576
Then all tps features from the old Tails version are active 5.012
And Tails is running from USB drive "to_upgrade" 0.895
And the boot device has safe access rights 5.227
And the expected persistent files created with the old Tails version are present in the filesystem 1.702
And all persistent directories from the old Tails version have safe access rights 2.929
After features/support/hooks.rb:335 2.191
After features/support/hooks.rb:105 0.010
Tags: @product @automatic_upgrade
8:26.015
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.267
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.615
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.448
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.974
When the network is plugged 1.077
And Tor is ready 55.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.668
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.206
Given I shutdown Tails and wait for the computer to power off 16.223
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:45.027
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.976
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.383
# 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.355
When the network is plugged 0.076
And Tor is ready 28.479
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.755
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.634
Given I shutdown Tails and wait for the computer to power off 4.662
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:29.503
Then Tails is running version 6.3~testoverlayfs 0.146
And all tps features are active 4.718
And the file system changes introduced in version 6.3~testoverlayfs are present 0.755
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.493
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.611
When the network is plugged 0.123
And Tor is ready 14.402
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:119:in `And Tor is ready'
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:335 5.992 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:01:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/99/artifact/build-artifacts/02:01:46_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/99/artifact/build-artifacts/02:01:46_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/99/artifact/build-artifacts/02:01:46_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/99/artifact/build-artifacts/02:01:46_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:105 0.096
Tags: @product @automatic_upgrade
43.884
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.752
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.627
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.136
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 25.206
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.950
After features/support/hooks.rb:335 1.546
After features/support/hooks.rb:105 0.000