Cucumber Reports (no 5025) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	5025	13 Aug 2024, 17:42

Feature: System memory erasure on shutdown

53.492

Scenario Erasure of the overlayfs read-write branch on shutdown

Hooks

Before features/support/hooks.rb:269 0.003

Steps

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

And I prepare Tails for memory erasure tests 0.402

When I fill a 128 MiB file with a known pattern on the root filesystem 15.995

# ensure the pattern is in memory due to tmpfs, not to disk cache

And I drop all kernel caches 2.462

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

Output 1

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

When I trigger shutdown 0.013

Then I find very few patterns in the guest's memory after 20 seconds 22.909

13.898%

13.898% 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:222:in `/^I find very few patterns in the guest's memory(?: after (\d+) seconds)?$/'
features/erase_memory.feature:72:in `Then I find very few patterns in the guest's memory after 20 seconds'

Output 1

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

Hooks

After features/support/hooks.rb:326 10.528

Output 1

SCENARIO FAILED: 'Erasure of the overlayfs read-write branch on shutdown' (at time 00:32:14)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5025/artifact/build-artifacts/00:32:14_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5025/artifact/build-artifacts/00:32:14_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5025/artifact/build-artifacts/00:32:14_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.journal

After features/support/hooks.rb:100 0.000

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker

12:4.218

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

Before features/support/hooks.rb:507 0.008

Steps

Given a computer 0.222

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

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

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

And I accept adding "cowsay" to Additional Software 5.972

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

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

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

And I enable persistence 13.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.035

And I log in to a new session 40.552

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

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

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

And Tor is ready 45.560

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

And available upgrades have been checked 0.054

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

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

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

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

And I enable persistence 13.375

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

And I log in to a new session 36.876

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

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

And the network is plugged 0.061

And Tor is ready 53.181

Then the Additional Software upgrade service has started 0.157

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

Hooks

After features/support/hooks.rb:515 1.255

Error message

Unexpected connections were made
  #<OpenStruct mac_saddr="50:54:00:7d:ed:d8", mac_daddr="33:33:00:00:00:02", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::7cb:808:a3d4:dbf6", daddr="ff02::2">
  #<OpenStruct mac_saddr="50:54:00:7d:ed:d8", mac_daddr="52:54:00:7d:e5:e9", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::7cb:808:a3d4:dbf6", daddr="fe80::5054:ff:fe7d:e5e9">
  #<OpenStruct mac_saddr="50:54:00:7d:ed:d8", mac_daddr="33:33:00:00:00:16", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::7cb:808:a3d4:dbf6", daddr="ff02::16">
  #<OpenStruct mac_saddr="50:54:00:7d:ed:d8", mac_daddr="33:33:ff:1a:c6:21", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="::", daddr="ff02::1:ff1a:c621"> (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.429

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:30:20)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5025/artifact/build-artifacts/01:30:20_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/5025/artifact/build-artifacts/01:30:20_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/5025/artifact/build-artifacts/01:30:20_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/5025/artifact/build-artifacts/01:30:20_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/5025/artifact/build-artifacts/01:30:20_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/5025/artifact/build-artifacts/01:30:20_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/5025/artifact/build-artifacts/01:30:20_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/5025/artifact/build-artifacts/01:30:20_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/5025/artifact/build-artifacts/01:30:20_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/5025/artifact/build-artifacts/01:30:20_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.023

Feature: Backing up the persistent storage

Tags: @product

1:17.809

Scenario Using Tails' custom backup tool to backup a newly added file

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.088

# The volume cannot be in use when GuestFs clones it, which we do below

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

And I clone USB drive "__internal" to a temporary USB drive "backup" 1.747

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.867

And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.023

When I start Tails' custom backup tool 3.962

Then the backup tool displays "Plug in your backup Tails USB stick" 0.224

When I plug USB drive "backup" 2.567

And I give the Persistent Storage on drive "backup" its own UUID 0.426

And I click "Retry" in the backup tool 1.254

Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.198

When I click "Back Up" in the backup tool 1.144

And I enter my persistent storage passphrase into the polkit prompt 20.801

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:787:in `deal_with_polkit_prompt'
./features/step_definitions/backup.rb:18:in `/^I enter my persistent storage passphrase into the polkit prompt$/'
features/backup.feature:21:in `And I enter my persistent storage passphrase into the polkit prompt'

Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000

# The backup tool ejects the drive, so we have to replug it

When I unplug USB drive "backup" 0.000

And I plug USB drive "backup" 0.000

Then the USB drive "backup" contains the same files as my persistent storage 0.000

Hooks

After features/support/hooks.rb:326 7.583

Output 1

SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:00:34)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5025/artifact/build-artifacts/02:00:34_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5025/artifact/build-artifacts/02:00:34_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5025/artifact/build-artifacts/02:00:34_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5025/artifact/build-artifacts/02:00:34_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal

After features/support/hooks.rb:100 0.134