gnupg-2.2.4: how to deal with failed tests

[Kristian Fiskerstrand]

On 01/17/2018 07:50 AM, Henry wrote:
> I finally got gnugp2 built without any fatal errors.
> Most of the tests passed, but the following tests failed:
> tests/openpgp/issue2346.scm
> tests/openpgp/ssh-export.scm
> tests/openpgp/export.scm
> tests/openpgp/ecc.scm
> tests/openpgp/armor.scm
> 
> I am not hip on using a binary that fails its tests.
> Grateful for any advice on how to configure/build gnupg2 so that
> it passes all its tests.
> 

Some observations on test
* in Gentoo we've had to shorten the socket path length, max is 108
chars of which 42 is used by gpgscm by default.
* Parallel tests fail if building without tofu support
* sparc architecture has a failure in
tests/openpgp/quick-key-manipulation.scm:219 on assert

-- 
----------------------------
Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk
----------------------------
Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
----------------------------
Qui audet vincit
Who dares wins

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180117/e3b484b8/attachment-0001.sig>