Project Number Date
test_Tails_ISO_devel 3599 25 Nov 2024, 13:21

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
27.119
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.149
And I prepare Tails for memory erasure tests 0.460
When I start a process allocating 128 MiB of memory with a known pattern 4.596
Then patterns cover at least 128 MiB in the guest's memory 4.216 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I kill the allocating process 2.286
Then I find very few patterns in the guest's memory after 3 seconds 7.409
7.672% 
7.672% 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:222:in `/^I find very few patterns in the guest's memory(?: after (\d+) seconds)?$/'
features/erase_memory.feature:19:in `Then I find very few patterns in the guest's memory after 3 seconds'
Output 1 
Pattern coverage: 7.672% (68 MiB out of 889 MiB reference memory)
After features/support/hooks.rb:326 5.598 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:30:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/00:30:03_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/00:30:03_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/00:30:03_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/00:30:03_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product @uefi
3:17.014
Scenario Booting Tails from a USB drive in UEFI mode
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.322
And I power off the computer 0.348
And the computer is set to boot in UEFI mode 0.029
When I start Tails from USB drive "__internal" with network unplugged and I login 3:1.312
try_for() 
try_for() timeout expired
Last ignored exception was: FindFailed: can not find any of the patterns ["TailsBootMenuGRUB_Bullseye.png", "TailsBootMenuGRUB_Bookworm.png"] on the screen
./features/support/helpers/screen.rb:240:in `rescue in wait_any'
./features/support/helpers/screen.rb:224:in `wait_any'
./features/step_definitions/common_steps.rb:407:in `block in enter_boot_menu_cmdline'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66: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/common_steps.rb:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284: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/common_steps.rb:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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/usb_install.feature:85:in `When I start Tails from USB drive "__internal" with network unplugged and I login'
Then Tails is running from USB drive "__internal" 0.000
And the boot device has safe access rights 0.000
And Tails has started in UEFI mode 0.000
After features/support/hooks.rb:326 10.596 
SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 01:00:37)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/01:00:37_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/01:00:37_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/01:00:37_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal
After features/support/hooks.rb:100 0.102
Feature: Tails persistence
Tags: @product @doc
21:28.760
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:269 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.110
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.125
When I try to enable persistence 0.298
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 33.797
When I repair the filesystem of the Persistent Storage 1.267
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.676
When I log in to a new session 43.320
And all notifications have disappeared 20:0.163
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
features/persistence.feature:192:in `And all notifications have disappeared'
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:326 10.987 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 04:20:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/04:20:39_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/04:20:39_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/04:20:39_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
32.970
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 7.365
And I cancel the GNOME authentication prompt 2.953
And I unlock and mount this VeraCrypt volume with GNOME Disks 22.652
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-disks]: child with name="Select a Keyfile" roleName='file chooser'
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/veracrypt.rb:269:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:51:in `And I unlock and mount this VeraCrypt volume with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:326 6.484 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 05:47:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/05:47:04_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/05:47:04_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/05:47:04_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3599/artifact/build-artifacts/05:47:04_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:100 0.000