Project Number Date
test_Tails_ISO_stable 4964 23 Jul 2024, 16:33

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:29.021
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 8.440
And I wait until Tor is ready 3.784
When I disconnect the network through GNOME 3.449
And I connect the network through GNOME 3.191
Then the Tor Connection Assistant autostarts 3.115
And the Tor Connection Assistant connects to Tor 6.668
And I wait until Tor is ready 5:0.371
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.281 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:32:42)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/00:32:42_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/4964/artifact/build-artifacts/00:32:42_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/4964/artifact/build-artifacts/00:32:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/00:32:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/00:32:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/00:32:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/00:32:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.034
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
11:41.890
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.257
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:22.149
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 27.011
And I accept adding "cowsay" to Additional Software 7.327
And Additional Software is correctly configured for package "cowsay" 0.995
And I shutdown Tails and wait for the computer to power off 6.628
And I start Tails from USB drive "__internal" with network unplugged 1:3.235
And I enable persistence 13.063
# 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.026
And I log in to a new session 34.809
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.446
And I revert the APT tweaks that made it prefer an old version of cowsay 0.075
# 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.088
And the network is plugged 0.046
And Tor is ready 21.790
# 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 8.055
And available upgrades have been checked 0.103
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.444
And I can open the Additional Software configuration window from the notification 4.167
And I shutdown Tails and wait for the computer to power off 2:3.846
And I start Tails from USB drive "__internal" with network unplugged 59.701
And I enable persistence 10.808
# 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.031
And I log in to a new session 39.316
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 42.393
And I revert the APT tweaks that made it prefer an old version of cowsay 0.072
And the network is plugged 0.092
And Tor is ready 52.559
Then the Additional Software upgrade service has started 0.197
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.109
Hooks
After features/support/hooks.rb:515 1.488
Error message 
Unexpected connections were made
  #<OpenStruct mac_saddr="50:54:00:a5:81:58", mac_daddr="33:33:00:00:00:02", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::be1f:1f08:f5e1:80c0", daddr="ff02::2">
  #<OpenStruct mac_saddr="50:54:00:a5:81:58", mac_daddr="52:54:00:d9:d3:2d", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::be1f:1f08:f5e1:80c0", daddr="fe80::5054:ff:fed9:d32d">
  #<OpenStruct mac_saddr="50:54:00:a5:81:58", mac_daddr="33:33:00:00:00:16", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::be1f:1f08:f5e1:80c0", daddr="ff02::16">
  #<OpenStruct mac_saddr="50:54:00:a5:81:58", mac_daddr="33:33:ff:20:ba:c5", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="::", daddr="ff02::1:ff20:bac5"> (FirewallAssertionFailedError)
./features/support/helpers/firewall_helper.rb:133:in `assert_all_connections'
./features/support/helpers/firewall_helper.rb:143:in `assert_no_leaks'
./features/support/hooks.rb:524:in `After'
After features/support/hooks.rb:326 5.447 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:35:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/01:35:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/01:35:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log
Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/01:35:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.pcap
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/01:35:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/01:35:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/01:35:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/01:35:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4964/artifact/build-artifacts/01:35:35_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/4964/artifact/build-artifacts/01:35:35_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/4964/artifact/build-artifacts/01:35:35_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.042