Project Number Date
test_Tails_ISO_21706-dont-use-efficient-cores 4 11 Aug 2026, 18:21

Failures Overview

The following summary displays scenarios that failed.

3:11.447
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.002
Steps
Given a computer 0.084
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:13.482
And I configure APT to prefer an old version of cowsay 0.006
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 5.947
And I accept adding "cowsay" to Additional Software 4.749
And Additional Software is correctly configured for package "cowsay" 0.563
And I shutdown Tails and wait for the computer to power off 3.958
And I start Tails from USB drive "__internal" with network unplugged 33.133
And I enable persistence 10.514
# 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.004
# 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.060
And I log in to a new session 7.130
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.167
And I revert the APT tweaks that made it prefer an old version of cowsay 0.035
# 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.041
And the network is plugged 0.030
And Tor is ready 14.055
And available upgrades have been checked 0.057
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.463
And I can open the Additional Software configuration window from the notification 26.958
The
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with roleName='notification'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/additional_software_packages.rb:33:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:160:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:103: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 installed 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:535 0.035
After features/support/hooks.rb:339 5.443

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21706-dont-use-efficient-cores/4/artifact/build-artifacts/01:01:04_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_21706-dont-use-efficient-cores/4/artifact/build-artifacts/01:01:04_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_21706-dont-use-efficient-cores/4/artifact/build-artifacts/01:01:04_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_21706-dont-use-efficient-cores/4/artifact/build-artifacts/01:01:04_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_21706-dont-use-efficient-cores/4/artifact/build-artifacts/01:01:04_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_21706-dont-use-efficient-cores/4/artifact/build-artifacts/01:01:04_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_21706-dont-use-efficient-cores/4/artifact/build-artifacts/01:01:04_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_21706-dont-use-efficient-cores/4/artifact/build-artifacts/01:01:04_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_21706-dont-use-efficient-cores/4/artifact/build-artifacts/01:01:04_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:108 0.009
Feature: Localization
Tags: @product
2:6.778
Scenario Cleartext localization preferences have priority over Persistent Storage
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 22.142
# The first boot simulates a legacy Tails, where locale is only saved in Persistent Storage
Then Tails is running from USB drive "__internal" 0.287
And I create a persistent partition 29.678
And I manually store legacy localization settings in Persistent Storage 0.226
When I shutdown Tails and wait for the computer to power off 4.042
# The second boot verifies that the legacy setting still works
And I start Tails from USB drive "__internal" with network unplugged 34.502
Then the Welcome Screen's language is set to English 0.182
And the Welcome Screen's formats is set to United States 0.108
When I enable persistence 13.613
Then the Welcome Screen's language is set to German 0.589
And the Welcome Screen's formats is set to France 0.235
When I set the language to Italian (it) 4.516
Then the language and keyboard have not been saved in cleartext storage 2.120
When I save the language and keyboard options in cleartext storage 14.533
The
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with name='Question' roleName='alert'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:511:in `/^I save the language and keyboard options in cleartext storage$/'
features/localization.feature:98:in `When I save the language and keyboard options in cleartext storage'
Then the "it" language and keyboard have been saved in cleartext storage 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# The third boot verifies that cleartext has priority
And I start Tails from USB drive "__internal" with network unplugged 0.000
Then the Welcome Screen's language is set to Italian 0.000
And the Welcome Screen's formats is set to Italy 0.000
When I enable persistence 0.000
# Only formats are loaded from persistence
Then the Welcome Screen's formats is set to France 0.000
And the Welcome Screen's language is set to Italian 0.000
After features/support/hooks.rb:339 5.401

SCENARIO FAILED: 'Cleartext localization preferences have priority over Persistent Storage' (at time 02:09:19)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21706-dont-use-efficient-cores/4/artifact/build-artifacts/02:09:19_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21706-dont-use-efficient-cores/4/artifact/build-artifacts/02:09:19_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21706-dont-use-efficient-cores/4/artifact/build-artifacts/02:09:19_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21706-dont-use-efficient-cores/4/artifact/build-artifacts/02:09:19_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.journal

After features/support/hooks.rb:108 0.006
Tags: @product
9.696
Scenario Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.466
And I capture all network traffic 0.003
And I disable Tails' firewall 0.095
When I do a TCP DNS lookup of "torproject.org" 0.131
Failed to resolve torproject.org:
;; communications error to 9.9.9.9#53: connection reset
;; communications error to 9.9.9.9#53: connection reset
;; no servers could be reached
.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/firewall_leaks.rb:22:in `/^I do a TCP DNS lookup of "(.*?)"$/'
features/tor_enforcement.feature:28:in `When I do a TCP DNS lookup of "torproject.org"'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:339 5.034

SCENARIO FAILED: 'Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector' (at time 02:54:40)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21706-dont-use-efficient-cores/4/artifact/build-artifacts/02:54:40_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21706-dont-use-efficient-cores/4/artifact/build-artifacts/02:54:40_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21706-dont-use-efficient-cores/4/artifact/build-artifacts/02:54:40_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21706-dont-use-efficient-cores/4/artifact/build-artifacts/02:54:40_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.journal

After features/support/hooks.rb:108 0.053