Project Number Date
test_Tails_ISO_devel 3400 26 May 2024, 13:22

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
30.324
Scenario Erasure of read and write disk caches on unmount: vfat
Before features/support/hooks.rb:259 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.646
And I prepare Tails for memory erasure tests 0.463
When I plug and mount a 128 MiB USB drive with a vfat filesystem 9.970
Then I find very few patterns in the guest's memory 4.802 
Pattern coverage: 0.000% (0 MiB out of 893 MiB reference memory)
# write cache
When I fill the USB drive with a known pattern 2.487
Then patterns cover at least 86% of the test FS size in the guest's memory 3.954
85.085% 
85.085% of the test FS size (127.599609375 MiB) has the pattern, but more than 86.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:170:in `/^patterns cover at least (\d+)% of the test FS size in the guest's memory$/'
features/erase_memory.feature:37:in `Then patterns cover at least 86% of the test FS size in the guest's memory'
Output 1 
Pattern coverage: 85.085% (108 MiB out of 127 MiB reference memory)
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory 0.000
# read cache
When I mount the USB drive again 0.000
And I read the content of the test FS 0.000
Then patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:305 4.220 
SCENARIO FAILED: 'Erasure of read and write disk caches on unmount: vfat' (at time 00:30:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/00:30:21_Erasure_of_read_and_write_disk_caches_on_unmount:_vfat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/00:30:21_Erasure_of_read_and_write_disk_caches_on_unmount:_vfat.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/00:30:21_Erasure_of_read_and_write_disk_caches_on_unmount:_vfat.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/00:30:21_Erasure_of_read_and_write_disk_caches_on_unmount:_vfat.journal
After features/support/hooks.rb:89 0.000
Feature: Backing up the persistent storage
Tags: @product
1:16.032
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.541
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 8.805
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.649
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.666
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.206
When I start Tails' custom backup tool 7.435
Then the backup tool displays "Plug in your backup Tails USB stick" 0.269
When I plug USB drive "backup" 2.680
And I give the Persistent Storage on drive "backup" its own UUID 0.169
And I click "Retry" in the backup tool 1.320
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.214
When I click "Back Up" in the backup tool 1.123
And I enter my persistent storage passphrase into the polkit prompt 20.949
try_for() 
try_for() timeout expired (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:783:in `deal_with_polkit_prompt'
./features/step_definitions/backup.rb:18:in `/^I enter my persistent storage passphrase into the polkit prompt$/'
features/backup.feature:21:in `And I enter my persistent storage passphrase into the polkit prompt'
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:305 6.388 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:08:23)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:08:23_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:08:23_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:08:23_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:08:23_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:89 0.135
Feature: Hardware failures
Tags: @product
1:39.845
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:259 0.011
Steps
Given a computer 0.283
And I start the computer from DVD with network unplugged 38.262
When Tails detects disk read failures on the boot device 1.109
Then I see a disk failure message on the splash screen 1:0.190
cannot 
cannot find PlymouthDiskFailureMessage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/hardware.rb:46:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:15:in `Then I see a disk failure message on the splash screen'
features/hardware_failure.feature:11:in `Then I see a disk failure message on the splash screen'
After features/support/hooks.rb:305 3.901 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#2)' (at time 02:20:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:20:56_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:20:56_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:20:56_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:20:56_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.journal
After features/support/hooks.rb:89 0.010
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
23.445
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.010
Steps
Given I have started Tails from DVD without network and logged in 9.213
Then the keys trusted by APT are valid for the next 3 months 14.231
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.386 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:25:07)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:25:07_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:25:07_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:25:07_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3400/artifact/build-artifacts/02:25:07_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000