Project Number Date
test_Tails_ISO_stable 4941 15 Jul 2024, 12:13

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
52.959
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:269 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.291
When I bump the system time with "+8 hours +15 minutes" 0.253
And all notifications have disappeared 4.209
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.122
And the network is plugged 0.030
And the Tor Connection Assistant autostarts 3.974
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.056
And I click "Connect to Tor" 1.202
And the Tor Connection Assistant fails to connect to Tor 16.051
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 13.764
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:850:in `/^I set the time zone in Tor Connection to "([^"]*)"$/'
features/time_syncing.feature:74:in `Then I set the time zone in Tor Connection to "Asia/Shanghai"'
Then the system clock is less than 20 minutes incorrect 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.031
After features/support/hooks.rb:326 5.006 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 00:17:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/00:17:47_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/00:17:47_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/00:17:47_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/00:17:47_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.journal
After features/support/hooks.rb:100 0.048
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
20.235
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:269 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.216
And I prepare Tails for memory erasure tests 0.594
When I start a process allocating 128 MiB of memory with a known pattern 2.432
Then patterns cover at least 128 MiB in the guest's memory 3.756 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I kill the allocating process 0.951
Then I find very few patterns in the guest's memory 4.282
8.935% 
8.935% of the free memory still has the pattern, but less than 0.800% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:219:in `/^I find very few patterns in the guest's memory$/'
features/erase_memory.feature:19:in `Then I find very few patterns in the guest's memory'
Output 1 
Pattern coverage: 8.935% (78 MiB out of 880 MiB reference memory)
After features/support/hooks.rb:326 5.664 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:28:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/00:28:26_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/00:28:26_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/00:28:26_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/00:28:26_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
7:4.826
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.008
Steps
Given a computer 0.191
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:19.100
And I configure APT to prefer an old version of cowsay 0.024
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 30.365
And I accept adding "cowsay" to Additional Software 4.820
And Additional Software is correctly configured for package "cowsay" 0.848
And I shutdown Tails and wait for the computer to power off 6.294
And I start Tails from USB drive "__internal" with network unplugged 59.139
And I enable persistence 12.324
# 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.030
And I log in to a new session 36.221
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.042
And I revert the APT tweaks that made it prefer an old version of cowsay 0.048
# 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.078
And the network is plugged 0.048
And Tor is ready 22.452
# 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 39.353
And available upgrades have been checked 0.526
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.184
And I can open the Additional Software configuration window from the notification 30.730
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with name="Configure" roleName='push button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/additional_software_packages.rb:41:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:164:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:106:in `And I can open the Additional Software configuration window from the notification'
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 5.603 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:24:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/01:24:02_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/4941/artifact/build-artifacts/01:24:02_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
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4941/artifact/build-artifacts/01:24:02_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/4941/artifact/build-artifacts/01:24:02_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/4941/artifact/build-artifacts/01:24:02_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/4941/artifact/build-artifacts/01:24:02_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/4941/artifact/build-artifacts/01:24:02_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/4941/artifact/build-artifacts/01:24:02_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/4941/artifact/build-artifacts/01:24:02_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.031