Cucumber Reports (no 11) - Failures Overview

Project	Number	Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix	11	04 Nov 2024, 11:59

Feature: Backing up the persistent storage

Tags: @product

1:53.454

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

Hooks

Before features/support/hooks.rb:269 0.007

Steps

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

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

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

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

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

When I start Tails' custom backup tool 5.721

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

When I plug USB drive "backup" 2.817

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

And I click "Retry" in the backup tool 1.345

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

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

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

Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 30.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/backup.rb:6:in `/^the backup tool displays "([^"]+)"$/'
features/backup.feature:22:in `Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!"'

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

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/11/artifact/build-artifacts/02:06:06_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_20634-greeter-tps-update-failure-fix/11/artifact/build-artifacts/02:06:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/11/artifact/build-artifacts/02:06:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/11/artifact/build-artifacts/02:06:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal

After features/support/hooks.rb:100 0.212

Feature: Packages are up-to-date

Tags: @source

12.949

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 12.949

Command

Command failed (returned pid 72711 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/tmp/tails-amd64-20634-greeter-tps-update-failure-fix@f89ed2ae99+stable@85b3d133b7-20241104T0640Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/tmp/tails-amd64-20634-greeter-tps-update-failure-fix@f89ed2ae99+stable@85b3d133b7-20241104T0640Z.build-manifest
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/bin/needed-package-updates", line 127, in _request
    curs.execute(
psycopg2.OperationalError: SSL connection has been closed unexpectedly


During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/bin/needed-package-updates", line 444, in <module>
    main()
  File "/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/bin/needed-package-updates", line 435, in main
    propose_update = check_build_manifest(build_manifest, config, suites, args.verbose)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/bin/needed-package-updates", line 293, in check_build_manifest
    udd = get_udd(pkg_dict, suites)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/bin/needed-package-updates", line 231, in get_udd
    return UDD(package_dict.keys(), suites)  # type: ignore[arg-type]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/bin/needed-package-updates", line 115, in __init__
    self.packages = self._request(packages)
                    ^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/bin/needed-package-updates", line 119, in _request
    with psycopg2.connect(
psycopg2.InterfaceError: connection already closed
.
<0> expected but was
<#<Process::Status: pid 72711 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/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

55.551

Scenario Manual filesystem repair is successful

Hooks

Before features/support/hooks.rb:269 0.003

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

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

When I try to enable persistence 0.419

Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 5.865

When I repair the filesystem of the Persistent Storage 1.284

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

And the filesystem of the Persistent Storage was repaired 0.100

When I close the filesystem repair dialog 1.261

Then persistence is successfully enabled 31.195

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:693:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/usb.rb:691:in `block in <top (required)>' (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:691:in `/^persistence is successfully enabled$/'
features/persistence.feature:181:in `Then persistence is successfully enabled'

Hooks

After features/support/hooks.rb:326 5.163

Output 1

SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 03:41:37)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/11/artifact/build-artifacts/03:41:37_Manual_filesystem_repair_is_successful.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/11/artifact/build-artifacts/03:41:37_Manual_filesystem_repair_is_successful.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/11/artifact/build-artifacts/03:41:37_Manual_filesystem_repair_is_successful.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/11/artifact/build-artifacts/03:41:37_Manual_filesystem_repair_is_successful.journal

After features/support/hooks.rb:100 0.000