Cucumber Reports (no 26) - Failures Overview

Project	Number	Date
test_Tails_ISO_15451-support-manual-fsck-on-error	26	17 Aug 2024, 16:31

Feature: Additional software

11:13.109

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

Steps

Given a computer 0.196

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

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

And I accept adding "cowsay" to Additional Software 6.553

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

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

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

And I enable persistence 13.142

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

And I log in to a new session 37.027

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

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

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

And the network is plugged 0.071

And Tor is ready 21.304

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

And available upgrades have been checked 0.144

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

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

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

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

And I enable persistence 12.775

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

And I log in to a new session 40.131

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

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

And the network is plugged 0.070

And Tor is ready 51.857

Then the Additional Software upgrade service has started 0.174

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

Hooks

After features/support/hooks.rb:515 1.315

Error message

Unexpected connections were made
  #<OpenStruct mac_saddr="50:54:00:e2:a6:94", mac_daddr="33:33:00:00:00:02", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::a093:db20:9777:2414", daddr="ff02::2">
  #<OpenStruct mac_saddr="50:54:00:e2:a6:94", mac_daddr="52:54:00:69:2c:ac", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::a093:db20:9777:2414", daddr="fe80::5054:ff:fe69:2cac">
  #<OpenStruct mac_saddr="50:54:00:e2:a6:94", mac_daddr="33:33:00:00:00:16", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::a093:db20:9777:2414", daddr="ff02::16">
  #<OpenStruct mac_saddr="50:54:00:e2:a6:94", mac_daddr="33:33:ff:a0:e7:16", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="::", daddr="ff02::1:ffa0:e716"> (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.485

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/01:26:30_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.027

Feature: Packages are up-to-date

Tags: @source

0.190

Scenario All packages are up-to-date

Hooks

Before features/support/hooks.rb:532 0.000

Steps

Given I have the build manifest for the image under test 0.000

Then all packages listed in the build manifest are up-to-date 0.190

Command

Command failed (returned pid 63764 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/tmp/tails-amd64-15451-support-manual-fsck-on-error@7641c17fc2+stable@c7db60a915-20240817T1118Z.build-manifest", {:err=>[:child, :out]}]:
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/bin/needed-package-updates", line 417, in <module>
    main()
  File "/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/bin/needed-package-updates", line 386, in main
    suites = tuple(get_suites(config.get("distribution")))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/bin/needed-package-updates", line 334, in get_suites
    codename_pos = ddi_s.index(min_codename)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: 'bullseye' is not in list
.
<0> expected but was
<#<Process::Status: pid 63764 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'

Hooks

After features/support/hooks.rb:539 0.000

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

1:16.008

Scenario Manual filesystem repair

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.900

And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 5.619

When I try to enable persistence 1.486

Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.001

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/usb.rb:1733:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:175:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'

When I repair the filesystem of the Persistent Storage 0.000

Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000

And the filesystem of the Persistent Storage was repaired 0.000

When I close the filesystem repair dialog 0.000

Then persistence is successfully enabled 0.000

Hooks

After features/support/hooks.rb:326 10.621

Output 1

SCENARIO FAILED: 'Manual filesystem repair' (at time 03:26:40)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/03:26:40_Manual_filesystem_repair.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/03:26:40_Manual_filesystem_repair.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/26/artifact/build-artifacts/03:26:40_Manual_filesystem_repair.journal

After features/support/hooks.rb:100 0.000