Cucumber Reports (no 3759) - Failures Overview

Project	Number	Date
test_Tails_ISO_devel	3759	28 Mar 2025, 13:18

Feature: Packages are up-to-date

Tags: @source

3.594

Scenario All packages are up-to-date

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:536 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 3.594

Command

Command failed (returned pid 62749 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@b27bd39ae1-20250328T0657Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@b27bd39ae1-20250328T0657Z.build-manifest
ERROR: tor-geoipdb: the package version(0.4.8.16-1~d12.bookworm+1) is higher than the version on experimental (0.4.8.14-1)
ERROR: tor: the package version(0.4.8.16-1~d12.bookworm+1) is higher than the version on experimental (0.4.8.14-1)
INFO: Need to upgrade to a new APT snapshot:
  - ghostscript (10.0.0~dfsg-11+deb12u6) to Debian bookworm-security (10.0.0~dfsg-11+deb12u7)
.
<0> expected but was
<#<Process::Status: pid 62749 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303: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'

Hooks

After features/support/hooks.rb:543 0.000

After features/support/hooks.rb:100 0.000

Feature: Chatting anonymously using Pidgin

Tags: @product @fragile @check_tor_leaks

1:1.629

Scenario Using a persistent Pidgin configuration

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.007

Before features/support/hooks.rb:511 0.009

Steps

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

And the network is plugged 0.092

And Tor is ready 23.597

And available upgrades have been checked 0.061

And all notifications have disappeared 4.316

When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.581

Then I see Pidgin's account manager window 4.279

When I create my XMPP account 4.123

cannot

cannot find PidginAddAccountProtocolXMPP.png on the screen (FindFailed)
./features/support/helpers/screen.rb:157:in `find'
./features/support/helpers/screen.rb:367:in `hover'
./features/support/helpers/screen.rb:394:in `click'
./features/step_definitions/pidgin.rb:126:in `/^I create my XMPP account$/'
features/pidgin.feature:68:in `When I create my XMPP account'

And I close Pidgin's account manager window 0.000

Then Pidgin automatically enables my XMPP account 0.000

When I close Pidgin 0.000

And I take note of the configured Pidgin accounts 0.000

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

Given a computer 0.000

And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000

And Pidgin has the expected persistent accounts configured 0.000

When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000

Then Pidgin automatically enables my XMPP account 0.000

And I join some empty multi-user chat 0.000

# Exercise Pidgin AppArmor profile with persistence enabled.

# This should really be in dedicated scenarios, but it would be

# too costly to set up the virtual USB drive with persistence more

# than once in this feature.

Given I start monitoring the AppArmor log of "/usr/bin/pidgin" 0.000

Then I cannot add a certificate from the "/home/amnesia/.gnupg" directory to Pidgin 0.000

And AppArmor has denied "/usr/bin/pidgin" from opening "/home/amnesia/.gnupg/test.crt" 0.000

When I close Pidgin's certificate import failure dialog 0.000

And I close Pidgin's certificate manager 0.000

Given I restart monitoring the AppArmor log of "/usr/bin/pidgin" 0.000

Then I cannot add a certificate from the "/live/persistence/TailsData_unlocked/gnupg" directory to Pidgin 0.000

And AppArmor has denied "/usr/bin/pidgin" from opening "/live/persistence/TailsData_unlocked/gnupg/test.crt" 0.000

When I close Pidgin's certificate import failure dialog 0.000

And I close Pidgin's certificate manager 0.000

Then I can add a certificate from the "/home/amnesia" directory to Pidgin 0.000

Hooks

After features/support/hooks.rb:519 0.049

After features/support/hooks.rb:330 5.945

Output 1

SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 04:35:20)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3759/artifact/build-artifacts/04:35:20_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3759/artifact/build-artifacts/04:35:20_Using_a_persistent_Pidgin_configuration.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3759/artifact/build-artifacts/04:35:20_Using_a_persistent_Pidgin_configuration.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3759/artifact/build-artifacts/04:35:20_Using_a_persistent_Pidgin_configuration.journal

After features/support/hooks.rb:100 0.000