When running the test suite in parallel, the two tests testsuite.test and jsontestsuite.test may be executed before their dependencies test-suite-data and json-test-suite-data are finished, as the download / cloning of the git repository takes a considerable amount of time. In this case, those two tests fail due to missing test data.
You may be able to reproduce this issue by running make check with the -j flag, e.g. env TESTS="jsontestsuite.test" make -e -j16 check. If the test is executed too fast / before the git clone(s) of test-suite-data and json-test-suite-data are finished, the test log file will include errors like:
[ERR]: failed to open json-test-suite-data/test_parsing/n_*.json
[ERR]: failed to open json-test-suite-data/test_parsing/i_*.json
It may be a solution to clone the two repos during initial build in e.g. bootstrap.sh - or, if it's desired to only download those files when tests are actually executed, inside the actual tests.
When running the test suite in parallel, the two tests
testsuite.test
andjsontestsuite.test
may be executed before their dependenciestest-suite-data
andjson-test-suite-data
are finished, as the download / cloning of the git repository takes a considerable amount of time. In this case, those two tests fail due to missing test data.You may be able to reproduce this issue by running make check with the -j flag, e.g.
env TESTS="jsontestsuite.test" make -e -j16 check
. If the test is executed too fast / before the git clone(s) oftest-suite-data
andjson-test-suite-data
are finished, the test log file will include errors like:It may be a solution to clone the two repos during initial build in e.g. bootstrap.sh - or, if it's desired to only download those files when tests are actually executed, inside the actual tests.