Test failures in noble-proposed (all-proposed)

[Adrien Nader]

Autopkgtests for request-tracker4 (and 5 it seems) fail on all arches and due to the recent changes around test environments and the use of all-proposed, it's difficult to identify which package change is responsible.

I actually see some passes on amd64 and arm64 but due to the environment issues that existed when the tests ran, I can't conclude much from them. Moreover, they weren't running with all-proposed like they would now. I also didn't see triggers related to gpg which could have been useful hints even with unreliable environment considering the errors.

The typical errors are

https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/arm64/r/request-tracker4/20240326_183841_3725f@/log.gz

2470s t/security/CVE-2012-4735-incoming-encryption-header.t ..
2470s # GnuPG --homedir /tmp/WbcjpQjcFA
2470s ok 1 - created a ticket
2470s ok 2 - loaded ticket
2470s ok 3 - Found the right attachment
2470s ok 4 - Incoming encryption header is removed
2470s ok 5 - Incoming signature header is removed
2470s ok 6 - created a ticket
2470s not ok 7
2470s
2470s # Failed test at t/security/CVE-2012-4735-incoming-encryption-header.t line 60.
2470s # found warning: gpg: keybox '/tmp/WbcjpQjcFA/pubring.kbx' created
2470s # found warning: Failure during GnuPG data: No data has been found. The reason is 'Invalid packet found'
2470s # found warning: Failure during GnuPG data: No data has been found. The reason is 'No armored data'
2470s # found warning: Failure during GnuPG gpg-exit: Failed to gpg-exit
2470s # expected to find warning: (?^:(?:keyring|keybox) .* created)
2470s # expected to find warning: (?^:Failure during GnuPG data: No data has been found\. The reason is 'Invalid packet found')
2470s # expected to find warning: (?^:Failure during GnuPG data: No data has been found\. The reason is 'No armored data')
2470s ok 8 - loaded ticket
2470s ok 9 - Found the right attachment
2470s ok 10 - Incoming encryption header is removed
2470s ok 11 - Incoming signature header is removed
2470s ok 12 - no warnings
2470s 1..12
2470s # Some tests failed or we bailed out, tmp directory '/tmp/autopkgtest.z5x7lQ/autopkgtest_tmp/smokeFWUfP9/t/tmp/security-CVE-2012-4735-incoming-encryption-header.t-kZdETulR' is not cleaned

or

https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/ppc64el/r/request-tracker4/20240323_184121_31e59@/log.gz

727s # encryption only, bad recipient
727s not ok 43
727s
727s # Failed test at t/mail/crypt-gnupg.t line 180.
727s # didn't find a warning
727s # expected to find warning: (?^:No public key|public key not found)
727s not ok 44 - no way to encrypt without keys of recipients
727s
727s # Failed test 'no way to encrypt without keys of recipients'
727s # at t/mail/crypt-gnupg.t line 182.

1569s ok 71 - RT's mail includes this instance's name
1569s not ok 72
1569s
1569s # Failed test at t/web/crypt-gnupg.t line 382.
1569s # didn't find a warning
1569s # expected to find warning: (?^:nokey\@example.com: skipped: (?:No public key|public key not found))
1569s # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)
1569s ok 73 - created ticket for owner-without-pubkey
1569s ok 74 - created ticket for owner-with-pubkey
1569s not ok 75
1569s
1569s # Failed test at t/web/crypt-gnupg.t line 404.
1569s # didn't find a warning
1569s # expected to find warning: (?^:nokey\@example.com: skipped: (?:No public key|public key not found))
1569s # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

[Lukas Märdian (slyon)]

The same issue happens with gnupg2 2.4 from Debian experimental, see https://ci.debian.net/packages/r/request-tracker5/unstable/amd64/

I think the tests need to be adoped to account for the additional "Failure during GnuPG gpg-exit: Failed to gpg-exit" output from GPG 2.4.

[Adrien Nader (adrien)]

Removed the request to badtest this (it was denied anyway).

[Lukas Märdian (slyon)]

Actually, there is a proper upstream fix here: https://github.com/bestpractical/rt/commit/8b574915649a424370aff12282360bed08623c47 (part of v5.0.6)

[Launchpad Janitor (janitor)]

This bug was fixed in the package request-tracker5 - 5.0.5+dfsg-2ubuntu1

---------------
request-tracker5 (5.0.5+dfsg-2ubuntu1) oracular; urgency=medium

  * Adopt incoming-encryption-header test case for GPG 2.4 output, LP: #2059287

 -- Lukas Märdian <email address hidden> Wed, 15 May 2024 11:56:54 +0200