Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 101 11 Jun 2024, 06:37

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
22.904
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.299
And I prepare Tails for memory erasure tests 0.446
When I start a process allocating 128 MiB of memory with a known pattern 4.933
Then patterns cover at least 128 MiB in the guest's memory 3.902 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I kill the allocating process 0.822
Then I find very few patterns in the guest's memory 4.500
12.040% 
12.040% 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: 12.040% (107 MiB out of 889 MiB reference memory)
After features/support/hooks.rb:315 5.132 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:28:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/00:28:01_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/00:28:01_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/00:28:01_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/00:28:01_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
59.022
Scenario Erasure of read and write disk caches on unmount: LUKS-encrypted ext4
Before features/support/hooks.rb:269 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.001
And I prepare Tails for memory erasure tests 0.668
When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 50.352
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:785:in `deal_with_polkit_prompt'
./features/step_definitions/common_steps.rb:1486:in `/^I plug and mount a (\d+) MiB USB drive with an? (.*)$/'
features/erase_memory.feature:50:in `When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf"'
Then I find very few patterns in the guest's memory 0.000
# write cache
When I fill the USB drive with a known pattern 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
# 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:315 5.530 
SCENARIO FAILED: 'Erasure of read and write disk caches on unmount: LUKS-encrypted ext4' (at time 00:30:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/00:30:47_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/00:30:47_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/00:30:47_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/00:30:47_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.002
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
7:57.878
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:269 0.016
Before features/support/hooks.rb:496 0.006
Steps
Given a computer 0.197
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:16.900
And I configure APT to prefer an old version of cowsay 0.023
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.731
And I accept adding "cowsay" to Additional Software 6.073
And Additional Software is correctly configured for package "cowsay" 0.817
And I shutdown Tails and wait for the computer to power off 6.315
And I start Tails from USB drive "__internal" with network unplugged 56.603
And I enable persistence 11.145
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.025
And I log in to a new session 37.877
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 2:13.699
And I revert the APT tweaks that made it prefer an old version of cowsay 0.054
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.059
And the network is plugged 0.048
And Tor is ready 1:1.303
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:646:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:601:in `/^Tor is ready$/'
features/additional_software_packages.feature:97:in `And Tor is ready'
# Note: the next step races against the appearance of the "The
# upgrade of your additional software failed" notification.
# It should win most of the time, which is good, but there's no
# guarantee it does. If it loses, then it'll remove the notification
# we'll be trying to interact with below ("I can open…")
And all notifications have disappeared 0.000
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:504 0.035
After features/support/hooks.rb:315 14.229 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:27:00)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/01:27:00_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/01:27:00_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/01:27:00_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/101/artifact/build-artifacts/01:27:00_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.017