Cucumber Reports (no 95) - Failures Overview

Project	Number	Date
test_Tails_ISO_20268-more-early-patch-functionality	95	05 Jun 2024, 06:54

Feature: System memory erasure on shutdown

18.940

Scenario Erasure of memory freed by killed userspace processes

Hooks

Before features/support/hooks.rb:269 0.002

Steps

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

And I prepare Tails for memory erasure tests 0.412

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

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

Output 1

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

When I kill the allocating process 0.652

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

3.275%

3.275% 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: 3.275% (28 MiB out of 872 MiB reference memory)

Hooks

After features/support/hooks.rb:315 5.698

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/95/artifact/build-artifacts/00:28:14_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/95/artifact/build-artifacts/00:28:14_Erasure_of_memory_freed_by_killed_userspace_processes.png

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

After features/support/hooks.rb:100 0.000

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker

8:6.615

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:269 0.005

Before features/support/hooks.rb:496 0.009

Steps

Given a computer 0.240

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

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

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

And I accept adding "cowsay" to Additional Software 7.080

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

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

And I start Tails from USB drive "__internal" with network unplugged 59.680

And I enable persistence 15.209

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

And I log in to a new session 27.901

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

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

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

And the network is plugged 0.042

And Tor is ready 1:1.802

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

Hooks

After features/support/hooks.rb:504 0.031

After features/support/hooks.rb:315 14.207

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:28:02)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/95/artifact/build-artifacts/01:28:02_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/95/artifact/build-artifacts/01:28:02_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/95/artifact/build-artifacts/01:28:02_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/95/artifact/build-artifacts/01:28:02_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.024

Feature: Emergency shutdown

Tags: @product @not_release_blocker

2:20.848

Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4

Hooks

Before features/support/hooks.rb:269 0.012

Steps

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

And I prepare Tails for memory erasure tests 0.375

And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 37.136

And I fill the USB drive with a known pattern 1.405

And I read the content of the test FS 0.062

And patterns cover at least 99% of the test FS size in the guest's memory 2.840

Output 1

Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)

When I eject the boot medium 0.382

And I wait for Tails to finish wiping the memory 1:30.314

cannot

cannot find MemoryWipeCompleted.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/erase_memory.rb:229:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'

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

Hooks

After features/support/hooks.rb:315 10.553

Output 1

SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:55:25)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/95/artifact/build-artifacts/01:55:25_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/95/artifact/build-artifacts/01:55:25_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/95/artifact/build-artifacts/01:55:25_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal

After features/support/hooks.rb:100 0.000