Project Number Date
test_Tails_ISO_devel 4096 01 Dec 2025, 22:27

Failures Overview

The following summary displays scenarios that failed.

Tags: @source
2.153
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:544 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 2.153
Command failed (pid 81106 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_devel/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@8e172cda8e-20251201T1639Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@8e172cda8e-20251201T1639Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2025-12-01 18:05:01+00:00 (2:21:15.755832 ago)
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", line 474, in <module>
    main()
    ~~~~^^
  File "/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", line 465, in main
    propose_update = check_build_manifest(build_manifest, config, suites, args.verbose)
  File "/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", line 307, in check_build_manifest
    udd = get_udd(pkg_dict, suites)
  File "/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", line 242, in get_udd
    return UDD(package_dict.keys(), suites)  # type: ignore[arg-type]
  File "/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", line 121, in __init__
    self.packages = self._request(packages)
                    ~~~~~~~~~~~~~^^^^^^^^^^
  File "/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", line 125, in _request
    with psycopg2.connect(
         ~~~~~~~~~~~~~~~~^
        "postgresql://udd-mirror:udd-mirror@udd-mirror.debian.net/udd",
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ) as conn, conn.cursor() as curs:
    ^
  File "/usr/lib/python3/dist-packages/psycopg2/__init__.py", line 122, in connect
    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: connection to server at "udd-mirror.debian.net" (88.99.39.211), port 5432 failed: FATAL:  permission denied for database "udd"
DETAIL:  User does not have CONNECT privilege.

 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:319:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:319:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/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'
After features/support/hooks.rb:551 0.000
After features/support/hooks.rb:100 0.000
59.342
Scenario Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 40.587
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 18.755
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/veracrypt.rb:188:in `/^I unlock and mount this VeraCrypt (volume|file container) with Unlock VeraCrypt Volumes$/'
features/veracrypt.feature:40:in `And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:331 5.723

SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 04:39:14)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4096/artifact/build-artifacts/04:39:14_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4096/artifact/build-artifacts/04:39:14_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4096/artifact/build-artifacts/04:39:14_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4096/artifact/build-artifacts/04:39:14_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal

After features/support/hooks.rb:100 0.017
46.695
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 36.933
And I unlock and mount this VeraCrypt file container with GNOME Disks 9.761
The
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:364:in `doActionNamed'
./features/support/helpers/dogtail.rb:378:in `activate'
./features/step_definitions/veracrypt.rb:238:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:76:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:331 7.926

SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 04:44:44)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4096/artifact/build-artifacts/04:44:44_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4096/artifact/build-artifacts/04:44:44_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4096/artifact/build-artifacts/04:44:44_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4096/artifact/build-artifacts/04:44:44_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal

After features/support/hooks.rb:100 0.015