Cucumber Reports (no 28) - Failures Overview

Project	Number	Date
test_Tails_ISO_15451-support-manual-fsck-on-error	28	19 Aug 2024, 17:11

Feature: Additional software

26:31.162

Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails

Hooks

Before features/support/hooks.rb:269 0.002

Before features/support/hooks.rb:507 0.002

Steps

Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 56.545

And I update APT using apt 18.401

And I install "popularity-contest" using apt 22.388

Then I am proposed to add the "popularity-contest" package to my Additional Software 8.866

When I create a persistent storage and activate the Additional Software feature 18.646

Then Additional Software is correctly configured for package "popularity-contest" 1.334

When I shutdown Tails and wait for the computer to power off 12.972

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

And I enable persistence 19.030

And I log in to a new session 42.007

And the Additional Software installation service has started 2:12.710

Then I am notified that the installation succeeded 20:0.120

execution

execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:591:in `new'
./features/step_definitions/common_steps.rb:591:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'

And Additional Software is correctly configured for package "popularity-contest" 0.000

And the package "popularity-contest" is installed after Additional Software has been started 0.000

Hooks

After features/support/hooks.rb:515 0.043

After features/support/hooks.rb:326 10.843

Output 1

SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:29:46)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/28/artifact/build-artifacts/01:29:46_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/28/artifact/build-artifacts/01:29:46_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/28/artifact/build-artifacts/01:29:46_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal

After features/support/hooks.rb:100 0.010

Feature: Packages are up-to-date

Tags: @source

0.189

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

Command

Command failed (returned pid 63834 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-20240819T1118Z.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 63834 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:17.273

Scenario Manual filesystem repair

Hooks

Before features/support/hooks.rb:269 0.004

Steps

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

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

When I try to enable persistence 0.511

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

Output 1

SCENARIO FAILED: 'Manual filesystem repair' (at time 04:03:12)

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

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

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

After features/support/hooks.rb:100 0.000