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

Failures Overview

The following summary displays scenarios that failed.

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() 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
1:16.178
Scenario Feature activation fails
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.207
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 14.666
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.102
When I try to enable persistence 1.400
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.009
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/usb.rb:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:335 10.298

SCENARIO FAILED: 'Feature activation fails' (at time 04:26:18)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/99/artifact/build-artifacts/04:26:18_Feature_activation_fails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/99/artifact/build-artifacts/04:26:18_Feature_activation_fails.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/99/artifact/build-artifacts/04:26:18_Feature_activation_fails.journal

After features/support/hooks.rb:105 0.000