AEAD, Kyber and Dilithium Test Failures

Description:

Testing build of the package on older AMD processor leads to test failures for the AEAD, Kyber and Dilithium protocols. The processor lacks AVX2, which may be a cause of the issue.

I was interested in the package when I saw it in testing and wanted to get an early look. The build goes fine, it's just the testing that fails.

Additional info:

  • package version(s): 1.2.0-2
  • config and/or log files: none
  • link to upstream bug report, if any: none

Steps to reproduce:

  1. Step 1 makepkg -s
  2. Step 2 wait a very long time for testing to complete
  3. ...

Testing Results:

Summary of Failures:

 40/393 leancrypto:regression / AEAD KMAC Crypt                                     FAIL              0.22s   killed by signal 8 SIGFPE
 41/393 leancrypto:performance / AEAD KMAC Crypt Accel large                        FAIL              3.34s   killed by signal 8 SIGFPE
 42/393 leancrypto:performance / AEAD KMAC Crypt C large                            FAIL              3.39s   killed by signal 8 SIGFPE
 43/393 leancrypto:regression / AEAD cSHAKE Crypt                                   FAIL              0.01s   exit status 2
 44/393 leancrypto:performance / AEAD cSHAKE Crypt Accel large                      FAIL              3.26s   killed by signal 8 SIGFPE
 45/393 leancrypto:performance / AEAD cSHAKE Crypt C large                          FAIL              3.33s   killed by signal 8 SIGFPE
129/393 leancrypto:regression / Kyber IES                                           FAIL              0.03s   (exit status 161 or signal 33 SIGinvalid)
147/393 leancrypto:regression / Kyber-X25519 IES                                    FAIL              0.02s   (exit status 161 or signal 33 SIGinvalid)
152/393 leancrypto:regression / Kyber 768 IES                                       FAIL              0.06s   (exit status 161 or signal 33 SIGinvalid)
168/393 leancrypto:regression / Kyber768-X25519 IES                                 FAIL              0.02s   (exit status 161 or signal 33 SIGinvalid)
173/393 leancrypto:regression / Kyber 512 IES                                       FAIL              0.07s   (exit status 161 or signal 33 SIGinvalid)
185/393 leancrypto:regression / Kyber512-X25519 IES                                 FAIL              0.02s   (exit status 161 or signal 33 SIGinvalid)
202/393 leancrypto:regression / Dilithium signature AVX2                            FAIL              0.02s   (exit status 231 or signal 103 SIGinvalid)
203/393 leancrypto:regression / Dilithium init update final AVX2                    FAIL              0.01s   (exit status 231 or signal 103 SIGinvalid)
223/393 leancrypto:regression / Dilithium 65 signature AVX2                         FAIL              0.02s   (exit status 231 or signal 103 SIGinvalid)
224/393 leancrypto:regression / Dilithium 65 init update final AVX2                 FAIL              0.01s   (exit status 231 or signal 103 SIGinvalid)

Ok:                 348
Expected Fail:      11
Fail:               16
Unexpected Pass:    0
Skipped:            18
Timeout:            0

Full log written to /home/david/arch/pkg/bld/leancrypto/src/build/meson-logs/testlog.txt

I thought I would pass this along in case this impacts the package. Let me know if you want the full testlog.txt and give me an e-mail to send to and I'm happy to pass it along.

If this is a known limitation of the package, then just nuke the report.

Edited by David C. Rankin