Project Number Date
test_Tails_ISO_stable 4862 30 May 2024, 20:07

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
20.491
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:265 0.002
Steps
Given I have started Tails from DVD without network and logged in 9.220
And I prepare Tails for memory erasure tests 0.521
When I start a process allocating 128 MiB of memory with a known pattern 2.288
Then patterns cover at least 128 MiB in the guest's memory 3.602 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I kill the allocating process 0.492
Then I find very few patterns in the guest's memory 4.366
9.241% 
9.241% 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: 9.241% (82 MiB out of 893 MiB reference memory)
After features/support/hooks.rb:311 5.489 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:28:53)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4862/artifact/build-artifacts/00:28:53_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4862/artifact/build-artifacts/00:28:53_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4862/artifact/build-artifacts/00:28:53_Erasure_of_memory_freed_by_killed_userspace_processes.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4862/artifact/build-artifacts/00:28:53_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:26.701
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:265 0.009
Before features/support/hooks.rb:492 0.008
Steps
Given a computer 0.271
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:27.818
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 30.319
And I accept adding "cowsay" to Additional Software 5.188
And Additional Software is correctly configured for package "cowsay" 0.925
And I shutdown Tails and wait for the computer to power off 6.881
And I start Tails from USB drive "__internal" with network unplugged 1:2.228
And I enable persistence 13.825
# 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 38.042
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.676
And I revert the APT tweaks that made it prefer an old version of cowsay 0.058
# 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.075
And the network is plugged 0.044
And Tor is ready 24.600
# 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 41.830
And available upgrades have been checked 0.425
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.104
And I can open the Additional Software configuration window from the notification 31.321
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:500 0.032
After features/support/hooks.rb:311 5.638 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:34:03)
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4862/artifact/build-artifacts/01:34:03_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/4862/artifact/build-artifacts/01:34:03_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/4862/artifact/build-artifacts/01:34:03_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/4862/artifact/build-artifacts/01:34:03_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/4862/artifact/build-artifacts/01:34:03_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/4862/artifact/build-artifacts/01:34:03_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/4862/artifact/build-artifacts/01:34:03_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4862/artifact/build-artifacts/01:34:03_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4862/artifact/build-artifacts/01:34:03_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.023