Project Number Date
test_Tails_ISO_stable 4960 22 Jul 2024, 12:26

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:23.049
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 6.888
And I wait until Tor is ready 4.346
When I disconnect the network through GNOME 2.803
And I connect the network through GNOME 2.884
Then the Tor Connection Assistant autostarts 2.715
And the Tor Connection Assistant connects to Tor 2.971
And I wait until Tor is ready 5:0.439
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:698:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:696:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:649:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:326 5.408 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:32:07)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4960/artifact/build-artifacts/00:32:07_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4960/artifact/build-artifacts/00:32:07_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4960/artifact/build-artifacts/00:32:07_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4960/artifact/build-artifacts/00:32:07_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4960/artifact/build-artifacts/00:32:07_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4960/artifact/build-artifacts/00:32:07_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4960/artifact/build-artifacts/00:32:07_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.056
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
11:0.599
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:269 0.005
Before features/support/hooks.rb:507 0.006
Steps
Given a computer 0.214
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:18.227
And I configure APT to prefer an old version of cowsay 0.029
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 27.051
And I accept adding "cowsay" to Additional Software 6.863
And Additional Software is correctly configured for package "cowsay" 0.898
And I shutdown Tails and wait for the computer to power off 6.777
And I start Tails from USB drive "__internal" with network unplugged 57.616
And I enable persistence 10.125
# 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.024
And I log in to a new session 36.567
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.418
And I revert the APT tweaks that made it prefer an old version of cowsay 0.063
# 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.095
And the network is plugged 0.054
And Tor is ready 21.436
# Note: the next step races against the appearance of the "The
# upgrade of your additional software failed" notification.
# It should win most of the time, which is good, but there's no
# guarantee it does. If it loses, then it'll remove the notification
# we'll be trying to interact with below ("I can open…")
And all notifications have disappeared 11.476
And available upgrades have been checked 0.575
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 5:1.082
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/common_steps.rb:586:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:105:in `And I see the "The upgrade of your additional software failed" notification after at most 300 seconds'
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:515 0.041
After features/support/hooks.rb:326 8.233 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:32:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4960/artifact/build-artifacts/01:32:21_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_stable/4960/artifact/build-artifacts/01:32:21_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_stable/4960/artifact/build-artifacts/01:32:21_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.019