Topic: testsuite

I'm following the instructions in section 2.2 of the wolfSSL User Manual / August 2019 / Version 4.1.0 (latest?) to build and test wolfSSL. Here are the commands I execute:

./configure
make
./testsuite/testsuite.test

There are two failures in the test log (see attached). The first is:

can't open ./certs/client-key.der, Please run from wolfSSL home dir error = -40

I am following the instructions and am running the test suite as noted in the documentation: from the wolfSSL home directory.

System: MINGW64_NT-10.0-19042 -- this is a very recent build of msys2.
Compiler: gcc.exe (Rev5, Built by MSYS2 project) 10.3.0

Any idea why this is happening?

Share

Re: testsuite

Hi a7v7

Are you in the root wolfssl directory when trying to execute the test script? Could you try "make check" and report the results?

The latest version of wolfSSL is v4.8.1 and is available from https://github.com/wolfSSL/wolfssl

Thanks,
Eric @ wolfSSL Support

3 (edited by a7v7 2021-08-24 14:51:29)

Re: testsuite

Eric,

I started with a clean version of wolfssl-4.8.1.
Here are the commands I ran:

.configure
make check > make_check.log 2>&1

The attached zip file contains make_check.log and test-suite.log.

ACV

Post's attachments

log_files.zip 3.08 kb, 2 downloads since 2021-08-24 

You don't have the permssions to download the attachments of this post.

Share

Re: testsuite

I don't see the attachment. Is it the same error?

Re: testsuite

Akk. Forgot the most important thing.

I have attached it to the previous post.

The error appears to be the same.

Share

Re: testsuite

Thanks for that. By chance do you have any folder names with spaces in the path to the the wolfssl install? MSYS can be finicky with absolute paths.

Re: testsuite

I can reproduce the issue on my MSYS2 install. I'll let you know what I find out.

Thanks,
Eric

Re: testsuite

No spaces in the path. And the path is very short too. It's c:\dev\wolfss-4.8.1.

Share

Re: testsuite

Okay, there is some issue with filesystem access from the wolfSSL test scripts in MSYS. I can get around it with

#define USE_CERT_BUFFERS_256
#define USE_CERT_BUFFERS_4096
#define NO_WRITE_TEMP_FILES

...added to options.h (or added as CFLAGS during configure).

That allows testsuite.test.exe to pass, but there is a similar issue with unit.test

Re: testsuite

Eric,

Thanks for letting me know.

ACV

Share