Cucumber Reports (no 81) - Failures Overview

Project	Number	Date
test_Tails_ISO_20268-more-early-patch-functionality	81	23 May 2024, 07:32

Feature: System memory erasure on shutdown

21.010

Scenario Erasure of memory freed by killed userspace processes

Hooks

Before features/support/hooks.rb:259 0.007

Steps

Given I have started Tails from DVD without network and logged in 8.407

And I prepare Tails for memory erasure tests 0.408

When I start a process allocating 128 MiB of memory with a known pattern 2.418

Then patterns cover at least 128 MiB in the guest's memory 4.151

Output 1

Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)

When I kill the allocating process 0.231

Then I find very few patterns in the guest's memory 5.392

8.950%

8.950% 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: 8.950% (78 MiB out of 873 MiB reference memory)

Hooks

After features/support/hooks.rb:305 6.202

Output 1

SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:29:11)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/81/artifact/build-artifacts/00:29:11_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/81/artifact/build-artifacts/00:29:11_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/81/artifact/build-artifacts/00:29:11_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/81/artifact/build-artifacts/00:29:11_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:89 0.000

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker

11:32.305

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:259 0.005

Before features/support/hooks.rb:456 0.006

Steps

Given a computer 0.193

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:40.810

And I configure APT to prefer an old version of cowsay 0.028

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.914

And I accept adding "cowsay" to Additional Software 7.472

And Additional Software is correctly configured for package "cowsay" 0.945

And I shutdown Tails and wait for the computer to power off 6.501

And I start Tails from USB drive "__internal" with network unplugged 1:1.818

And I enable persistence 12.847

# 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.024

And I log in to a new session 37.692

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.411

And I revert the APT tweaks that made it prefer an old version of cowsay 0.063

# 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.071

And the network is plugged 0.057

And Tor is ready 22.368

# 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 11.449

And available upgrades have been checked 0.568

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 5:1.064

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:591:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:105:in `And I see the "The upgrade of your additional software failed" notification after at most 300 seconds'

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

Hooks

After features/support/hooks.rb:464 0.034

After features/support/hooks.rb:305 8.656

Output 1

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:33:34)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/81/artifact/build-artifacts/01:33:34_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/81/artifact/build-artifacts/01:33:34_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

After features/support/hooks.rb:89 0.015

Feature: Tails-related cryptographic keys are up-to-date

Tags: @product

24.121

Scenario The included APT repository keys are up-to-date

Hooks

Before features/support/hooks.rb:259 0.005

Steps

Given I have started Tails from DVD without network and logged in 9.717

Then the keys trusted by APT are valid for the next 3 months 14.403

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'

Hooks

After features/support/hooks.rb:305 5.311

Output 1

SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:20:17)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/81/artifact/build-artifacts/02:20:17_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/81/artifact/build-artifacts/02:20:17_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/81/artifact/build-artifacts/02:20:17_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/81/artifact/build-artifacts/02:20:17_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000