Cucumber Reports (no 4984) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	4984	31 Jul 2024, 08:51

Feature: System memory erasure on shutdown

20.344

Scenario Erasure of memory freed by killed userspace processes

Hooks

Before features/support/hooks.rb:269 0.003

Steps

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

And I prepare Tails for memory erasure tests 0.725

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

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

Output 1

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

When I kill the allocating process 0.309

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

5.035%

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

Hooks

After features/support/hooks.rb:326 5.970

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/00:30:00_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/00:30:00_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/00:30:00_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/00:30:00_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

11:58.627

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.013

Before features/support/hooks.rb:507 0.008

Steps

Given a computer 0.225

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

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

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

And I accept adding "cowsay" to Additional Software 8.615

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

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

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

And I enable persistence 13.065

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

And I log in to a new session 37.182

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

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

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

And the network is plugged 0.043

And Tor is ready 19.068

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

And available upgrades have been checked 0.151

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

And I can open the Additional Software configuration window from the notification 4.225

And I shutdown Tails and wait for the computer to power off 2:7.430

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

And I enable persistence 13.300

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

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

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

And the network is plugged 0.049

And Tor is ready 53.226

Then the Additional Software upgrade service has started 0.191

And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.104

Hooks

After features/support/hooks.rb:515 1.403

Error message

Unexpected connections were made
  #<OpenStruct mac_saddr="50:54:00:94:2f:49", mac_daddr="33:33:00:00:00:02", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::9e90:eef:9315:6006", daddr="ff02::2">
  #<OpenStruct mac_saddr="50:54:00:94:2f:49", mac_daddr="52:54:00:3a:7b:fc", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::9e90:eef:9315:6006", daddr="fe80::5054:ff:fe3a:7bfc">
  #<OpenStruct mac_saddr="50:54:00:94:2f:49", mac_daddr="33:33:00:00:00:16", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::9e90:eef:9315:6006", daddr="ff02::16">
  #<OpenStruct mac_saddr="50:54:00:94:2f:49", mac_daddr="33:33:ff:78:84:49", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="::", daddr="ff02::1:ff78:8449"> (FirewallAssertionFailedError)
./features/support/helpers/firewall_helper.rb:133:in `assert_all_connections'
./features/support/helpers/firewall_helper.rb:143:in `assert_no_leaks'
./features/support/hooks.rb:524:in `After'

After features/support/hooks.rb:326 5.366

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:27:42)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/01:27:42_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/01:27:42_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log

Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/01:27:42_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.pcap

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/01:27:42_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/01:27:42_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/01:27:42_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/01:27:42_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4984/artifact/build-artifacts/01:27:42_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_stable/4984/artifact/build-artifacts/01:27:42_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_stable/4984/artifact/build-artifacts/01:27:42_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.028