Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 79 21 May 2024, 06:39

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
19.540
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 8.534
And I prepare Tails for memory erasure tests 0.651
When I start a process allocating 128 MiB of memory with a known pattern 2.363
Then patterns cover at least 128 MiB in the guest's memory 3.956 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I kill the allocating process 0.226
Then I find very few patterns in the guest's memory 3.809
2.610% 
2.610% 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: 2.610% (23 MiB out of 914 MiB reference memory)
After features/support/hooks.rb:305 4.571 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:28:12)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/00:28:12_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/00:28:12_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/00:28:12_Erasure_of_memory_freed_by_killed_userspace_processes.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/00:28:12_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:89 0.000
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
22.088
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.005
Steps
Given I have started Tails from DVD without network and logged in 8.419
Then the keys trusted by APT are valid for the next 3 months 13.668
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.435 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:20:22)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/02:20:22_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/02:20:22_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/02:20:22_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/02:20:22_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Tails persistence
Tags: @product
15.349
Scenario Deleting a Tails persistent partition
Before features/support/hooks.rb:259 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 11.280
And I log in to a new session without activating the Persistent Storage 4.068
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:511:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:128:in `And I log in to a new session without activating the Persistent Storage'
Then persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
And all notifications have disappeared 0.000
When I delete the persistent partition 0.000
Then there is no persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:305 4.266 
SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 03:25:04)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/03:25:04_Deleting_a_Tails_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/03:25:04_Deleting_a_Tails_persistent_partition.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/03:25:04_Deleting_a_Tails_persistent_partition.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/79/artifact/build-artifacts/03:25:04_Deleting_a_Tails_persistent_partition.journal
After features/support/hooks.rb:89 0.000