Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 86 07 Jun 2025, 18:31

Failures Overview

The following summary displays scenarios that failed.

8:48.081
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Before features/support/hooks.rb:518 0.006
Steps
Given a computer 0.230
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:54.428
And I configure APT to prefer an old version of cowsay 0.035
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.194
And I accept adding "cowsay" to Additional Software 6.820
And Additional Software is correctly configured for package "cowsay" 0.817
And I shutdown Tails and wait for the computer to power off 6.349
And I start Tails from USB drive "__internal" with network unplugged 1:2.659
And I enable persistence 12.201
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.025
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.087
And I log in to a new session 40.798
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 2:15.139
And I revert the APT tweaks that made it prefer an old version of cowsay 0.054
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.067
And the network is plugged 0.072
And Tor is ready 1:2.099
TCA
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:652:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/additional_software_packages.feature:100:in `And Tor is ready'
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:526 0.030
After features/support/hooks.rb:335 14.325

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:20:32)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/86/artifact/build-artifacts/01:20:32_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/86/artifact/build-artifacts/01:20:32_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/86/artifact/build-artifacts/01:20:32_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/86/artifact/build-artifacts/01:20:32_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:105 0.031