Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 11 09 Aug 2026, 23:20

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks @not_release_blocker
1:41.055
Scenario Anti-test: Changes to the hardware clock are kept when rebooting
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.002
Steps
Given I have started Tails from DVD without network and logged in 6.378
When I bump the hardware clock's time with "-15 days" 1.475
And I warm reboot the computer 0.005
And the computer reboots Tails 1:33.195
can 
can not find any of the patterns ["TailsGreeter.png", "PlymouthGraphicsCardFailureMessage.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:446:in `/^the computer (?:re)?boots Tails$/'
features/time_syncing.feature:45:in `And the computer reboots Tails'
Then the hardware clock is still off by "-15 days" 0.000
After features/support/hooks.rb:535 0.039
After features/support/hooks.rb:339 4.903 
SCENARIO FAILED: 'Anti-test: Changes to the hardware clock are kept when rebooting' (at time 00:18:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/00:18:09_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/00:18:09_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/00:18:09_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/00:18:09_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.journal
After features/support/hooks.rb:108 0.005
Feature: Installing Tails to a USB drive
Tags: @product
15:26.452
Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.285
And I create a file in the Persistent directory 0.061
And I temporarily create a 7200 MiB disk named "install" 0.034
And I create a gpt partition with a vfat filesystem on disk "install" 3.054
And I plug USB drive "install" 2.193
And I install Tails with Persistent Storage to USB drive "install" by cloning 15:12.823
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendant of [application | tails-installer]: child with name='Information' roleName='alert'
STDOUT:

STDERR:


./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/usb.rb:272:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/usb.rb:270:in `block in <top (required)>' (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/usb.rb:270:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_install.feature:50:in `And I install Tails with Persistent Storage to USB drive "install" by cloning'
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is a persistence partition on USB drive "install" 0.000
And the USB drive "install" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:339 4.990 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 00:56:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/00:56:11_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/00:56:11_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/00:56:11_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/00:56:11_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:108 0.135
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
3:17.614
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.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.079
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:18.182
And I configure APT to prefer an old version of cowsay 0.004
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 5.966
And I accept adding "cowsay" to Additional Software 4.794
And Additional Software is correctly configured for package "cowsay" 0.525
And I shutdown Tails and wait for the computer to power off 4.064
And I start Tails from USB drive "__internal" with network unplugged 33.943
And I enable persistence 13.169
# 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.005
# 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.049
And I log in to a new session 7.105
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.176
And I revert the APT tweaks that made it prefer an old version of cowsay 0.034
# 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.039
And the network is plugged 0.031
And Tor is ready 12.655
And available upgrades have been checked 0.041
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.413
And I can open the Additional Software configuration window from the notification 25.331
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.033
After features/support/hooks.rb:339 5.202 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:14:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/01:14:08_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_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/01:14:08_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_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/01:14:08_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_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/01:14:08_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_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/01:14:08_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_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/01:14:08_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_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/01:14:08_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_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/01:14:08_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_17367-per-setting-dconf-persistence/11/artifact/build-artifacts/01:14:08_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.018