Project Number Date
test_Tails_ISO_devel 4329 08 Apr 2026, 14:51

Failures Overview

The following summary displays scenarios that failed.

Feature: Emergency shutdown
Tags: @product @not_release_blocker
48.888
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 6.937
And I prepare Tails for memory erasure tests 0.433
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 41.517
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/common_steps.rb:820:in `deal_with_polkit_prompt'
./features/step_definitions/common_steps.rb:1527:in `/^I plug and mount a (\d+) MiB USB drive with an? (.*)$/'
features/emergency_shutdown.feature:39:in `And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf"'
And I fill the USB drive with a known pattern 0.000
And I read the content of the test FS 0.000
And patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:331 5.483 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:19:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4329/artifact/build-artifacts/01:19:19_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4329/artifact/build-artifacts/01:19:19_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4329/artifact/build-artifacts/01:19:19_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4329/artifact/build-artifacts/01:19:19_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.002
Feature: Random Seed
Tags: @product
2:0.563
Scenario A random seed is read during boot and written during boot and shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.079
And I temporarily create a 7200 MiB disk named "temp" 0.009
And I plug USB drive "temp" 1.018
And I write the Tails USB image to disk "temp" 13.642
Then there is no random seed on USB drive "temp" 2.518
When I start Tails from USB drive "temp" with network unplugged 1:43.295
The 
The Dogtail init script raised: DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
STDOUT:

STDERR:
Exception ignored in: <function Ponytail.__del__ at 0x700bac819440>
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/ponytail/ponytail.py", line 51, in __del__
    if (self.connected):
AttributeError: 'Ponytail' object has no attribute 'connected'

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:85:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:457:in `new'
./features/step_definitions/common_steps.rb:457:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/random_seed.feature:12:in `When I start Tails from USB drive "temp" with network unplugged'
Then the random seed was written multiple times on first boot 0.000
And there is a random seed on USB drive "temp" 0.000
When I log in to a new session 0.000
And I wait for the random seed to be updated 0.000
Then there is a random seed on USB drive "temp" 0.000
And the random seed is different from the previous one 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Then there is a random seed on USB drive "temp" 0.000
And the random seed is different from the previous one 0.000
After features/support/hooks.rb:331 5.448 
SCENARIO FAILED: 'A random seed is read during boot and written during boot and shutdown' (at time 03:05:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4329/artifact/build-artifacts/03:05:17_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4329/artifact/build-artifacts/03:05:17_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4329/artifact/build-artifacts/03:05:17_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4329/artifact/build-artifacts/03:05:17_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.journal
After features/support/hooks.rb:100 0.118