Project Number Date
test_Tails_ISO_devel 3368 30 Apr 2024, 23:51

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
23.805
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:259 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.748
And I prepare Tails for memory erasure tests 0.459
When I start a process allocating 128 MiB of memory with a known pattern 5.107
Then patterns cover at least 128 MiB in the guest's memory 3.866 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I kill the allocating process 0.459
Then I find very few patterns in the guest's memory 4.163
9.535% 
9.535% 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.535% (82 MiB out of 864 MiB reference memory)
After features/support/hooks.rb:305 4.623 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:28:26)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:28:26_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:28:26_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:28:26_Erasure_of_memory_freed_by_killed_userspace_processes.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:28:26_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:89 0.000
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
6:56.810
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:259 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 6:56.810
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./features/step_definitions/snapshots.rb:152:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:149:in `each'
./features/step_definitions/snapshots.rb:149:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:172:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:76:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
And I wait 20 seconds 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:305 4.193 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:38:57)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:38:57_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:38:57_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:38:57_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:38:57_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:89 0.011
Feature: Installing Tails to a USB drive
Tags: @product
1:57.421
Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage
Before features/support/hooks.rb:259 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:57.421
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./features/step_definitions/snapshots.rb:152:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:149:in `each'
./features/step_definitions/snapshots.rb:149:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:172:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:43:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I create a file in the Persistent directory 0.000
And I temporarily create a 7200 MiB disk named "install" 0.000
And I create a gpt partition with a vfat filesystem on disk "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails with Persistent Storage to USB drive "install" by cloning 0.000
Then the running Tails is installed 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:305 4.602 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 00:49:36)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:49:36_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_devel/3368/artifact/build-artifacts/00:49:36_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:49:36_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/00:49:36_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:89 0.000
Feature: Installing Tails to a USB drive
Tags: @product
3:1.450
Scenario The system partition is updated when booting from a USB drive where a Tails USB image was copied
Before features/support/hooks.rb:259 0.003
Steps
Given a computer 0.166
And I start Tails from USB drive "usbimage" with network unplugged and I login 3:1.283
try_for() 
try_for() timeout expired
Last ignored exception was: FindFailed: can not find any of the patterns ["TailsBootMenuSyslinux.png", "TailsBootMenuSyslinux_alt.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:404:in `block in enter_boot_menu_cmdline'
./features/support/helpers/misc_helpers.rb:79:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:67:in `loop'
./features/support/helpers/misc_helpers.rb:67:in `block in try_for'
./features/support/helpers/misc_helpers.rb:66:in `try_for'
./features/step_definitions/common_steps.rb:401:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:431:in `the_computer_boots'
./features/step_definitions/common_steps.rb:445:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:286:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/step_definitions/common_steps.rb:401:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:431:in `the_computer_boots'
./features/step_definitions/common_steps.rb:445:in `/^the computer (?:re)?boots Tails( with genuine APT sources)?$/'
./features/step_definitions/common_steps.rb:286: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:95:in `And I start Tails from USB drive "usbimage" with network unplugged and I login'
Then Tails is running from USB drive "usbimage" 0.000
And the label of the system partition on "usbimage" is "Tails" 0.000
And the system partition on "usbimage" is an EFI system partition 0.000
And the FAT filesystem on the system partition on "usbimage" is at least 4000M large 0.000
And the UUID of the FAT filesystem on the system partition on "usbimage" was randomized 0.000
And the label of the FAT filesystem on the system partition on "usbimage" is "TAILS" 0.000
And the system partition on "usbimage" has the expected flags 0.000
After features/support/hooks.rb:305 9.636 
SCENARIO FAILED: 'The system partition is updated when booting from a USB drive where a Tails USB image was copied' (at time 01:12:27)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/01:12:27_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/01:12:27_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.mkv
After features/support/hooks.rb:89 0.094
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
20.751
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails from DVD without network and logged in 7.975
Then the keys trusted by APT are valid for the next 3 months 12.776
The 
The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:305 4.468 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:25:44)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/02:25:44_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/02:25:44_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/02:25:44_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3368/artifact/build-artifacts/02:25:44_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000