Topic: [SOLVED] wolfssl-4.5.0: make check failed for tests/unit.test
Getting an error with make check
Note: I am working on a Ubuntu-18.04.15 LTS machine which is present on the cloud, and have logged into it using VMware-horizon client.
Since I am working on the same machine on which I am trying to install wolfssl-4.5.0-commercial-fips, so this won't be an issue In my opinion.
I have executed the following commands in sequence.
./configure --enable-fips=v2 --enable-jni --enable-debug
make
make checkI have updated the hash
message = In Core Integrity check FIPS error
hash = 8D29242F610EAEA179605BB1A99974EBC72B0ECDB26B483B226A729F36FC82A2
In core integrity hash check failure, copy above hash
into verifyCore[] in fips_test.c and rebuildinside the fips_test.c and then executed make check again, getting the error as: -
make check
make -j5 check-am
make[1]: Entering directory '/home/user/Desktop/wolfssl/wolfssl-4.5.0-commercial-fips-linuxv2'
make -j5 testsuite/testsuite.test tests/unit.test scripts/resume.test scripts/crl-revoked.test scripts/psk.test scripts/pkcallbacks.test scripts/tls13.test scripts/external.test scripts/google.test scripts/openssl.test scripts/ocsp.test
make[2]: Entering directory '/home/user/Desktop/wolfssl/wolfssl-4.5.0-commercial-fips-linuxv2'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
make[2]: Nothing to be done for 'scripts/resume.test'.
make[2]: Nothing to be done for 'scripts/crl-revoked.test'.
make[2]: Nothing to be done for 'scripts/psk.test'.
make[2]: Nothing to be done for 'scripts/pkcallbacks.test'.
make[2]: Nothing to be done for 'scripts/tls13.test'.
make[2]: Nothing to be done for 'scripts/external.test'.
make[2]: Nothing to be done for 'scripts/google.test'.
make[2]: Nothing to be done for 'scripts/openssl.test'.
make[2]: Nothing to be done for 'scripts/ocsp.test'.
make[2]: 'tests/unit.test' is up to date.
make[2]: Leaving directory '/home/user/Desktop/wolfssl/wolfssl-4.5.0-commercial-fips-linuxv2'
make -j5 check-TESTS
make[2]: Entering directory '/home/user/Desktop/wolfssl/wolfssl-4.5.0-commercial-fips-linuxv2'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
make[3]: Entering directory '/home/user/Desktop/wolfssl/wolfssl-4.5.0-commercial-fips-linuxv2'
make[3]: warning: -jN forced in submake: disabling jobserver mode.
PASS: scripts/external.test
PASS: scripts/openssl.test
PASS: scripts/resume.test
PASS: scripts/psk.test
PASS: scripts/google.test
PASS: scripts/crl-revoked.test
PASS: scripts/pkcallbacks.test
PASS: scripts/ocsp.test
PASS: testsuite/testsuite.test
./build-aux/test-driver: line 107: 18917 Aborted (core dumped) "$@" > $log_file 2>&1
FAIL: tests/unit.test
PASS: scripts/tls13.test
============================================================================
Testsuite summary for wolfssl 4.5.0
============================================================================
# TOTAL: 11
# PASS: 10
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
Please report to https://github.com/wolfssl/wolfssl/issues
============================================================================
Makefile:5609: recipe for target 'test-suite.log' failed
make[3]: *** [test-suite.log] Error 1
make[3]: Leaving directory '/home/user/Desktop/wolfssl/wolfssl-4.5.0-commercial-fips-linuxv2'
Makefile:5715: recipe for target 'check-TESTS' failed
make[2]: *** [check-TESTS] Error 2
make[2]: Leaving directory '/home/user/Desktop/wolfssl/wolfssl-4.5.0-commercial-fips-linuxv2'
Makefile:5937: recipe for target 'check-am' failed
make[1]: *** [check-am] Error 2
make[1]: Leaving directory '/home/user/Desktop/wolfssl/wolfssl-4.5.0-commercial-fips-linuxv2'
Makefile:5940: recipe for target 'check' failed
make: *** [check] Error 2with the test-suite.log having the error as: -
wolfSSL Entering wolfSSL_ASN1_STRING_free
Freeing der CA
OK Freeing der CA
wolfSSL Leaving AddCA, return -151
Error in Cert in Chain
wolfSSL Leaving wolfSSL_CTX_load_verify_buffer_ex, return -151
FAIL tests/unit.test (exit status: 134)the full log is attached here as an attachment.
Can someone help me with this?