calling make check after building fails
Closed, ResolvedPublic

Description

Test fails and output appended, not sure what this exactly means, but test are
there for a reason I guess
make check &> log_file.txt was called after building.

Details

MisterXYZ set Version to 2.1.19.
MisterXYZ renamed this task from calling make check after building to calling make check after building fails.
wk added a subscriber: wk.Apr 3 2017, 9:50 AM

Can you please run

cd tests/openpgp
make check XTESTS=4gb-packet.scm verbose=4

user@group: make check XTESTS=4gb-packet.scm verbose=4 &> 4gb-packet.scm_execution.log
and content of 4gb-packet.scm.log appended for completeness{F66019}

justus claimed this task.Apr 6 2017, 12:30 PM
justus added a subscriber: justus.

The 4gb-packet test reads an OpenPGP message compressed with BZIP2. If that test fails, it most certainly means that you compiled GnuPG without support for BZIP2. You can check this with:

$ gpg --with-colons --list-config compressname
cfg:compressname:Uncompressed;ZIP;ZLIB;BZIP2

I'll make the test more robust.

$ gpg2 --with-colons --list-config compressname
cfg:compressname:nicht komprimiert;ZIP;ZLIB

You are correct justus, thanks.
https://www.rootusers.com/gzip-vs-bzip2-vs-xz-performance-comparison/
for informal knowledge here a benchmark of different compression algorithms.
bzip2 --version work thus it is installed, but I guess it is not per default used

Sadly test still fails
FAIL: import-all-certs

justus added a comment.Apr 6 2017, 2:06 PM

You need the development package installed (e.g. libbz2-dev on Debian-like systems). Then, rerun configure and rebuild.

Sadly test still fails
FAIL: import-all-certs

But this is a different test. It is from the 'tests/pkits' suite, which hasn't been maintained for ages, and usually we don't run it. Did you explicitly enable it or was it run automatically?

Steps to (hopefully) reproduce
Cloned the developtment branch and reverified the commit hash described in
https://www.gnupg.org/download/git.html
[Removing https://git.gnupg.org/gnupg.git would be great, since cloning that did not work]
$ ./autogen.sh
$ ./configure --sysconfdir=/etc --enable-maintainer-mode && make
$ make check &> check.log
make does not exist also, though cpu seems to not work on

Did I do anything wrong?

It was run automatically. Installing libbz2-dev did not help.
Output stays the same.

SKIP: Environment variable 'XTEST_GPGME_SRCDIR' not set. Please point it to a recent GPGME source tree to run the GPGME test suite.
also looks abit strange, it does not look up for the path GPGME is installed on the system?

Any advice besides changing the distro? :D

justus added a comment.Apr 6 2017, 2:27 PM

Please just keep discussing *one* issue per task.

It was run automatically.

For the tests/pkits issue I have created T3067.

Installing libbz2-dev did not help. Output stays the same.

Am I right in assuming that the 4gb-packet.scm test now passes? If so, let's close this task.

SKIP: Environment variable 'XTEST_GPGME_SRCDIR' not set. Please point it to a recent GPGME source tree to run the GPGME test suite.
also looks abit strange, it does not look up for the path GPGME is installed on the system?

No it does not. This is not an error. If you happen to be a GnuPG developer, then you may setup your environment to point to the GPGME sources and build tree, and then we run GPGME's tests as part of the GnuPG test suite.