If python bindings are enables with --enable-python, make check will fail on the unit tests for the python bindings.

make  check-TESTS
make[5]: Entering directory `/kobaltnet/janssege/Development/Builds/gnucash-f19-trunk/src/optional/python-bindings/tests'
make[6]: Entering directory `/kobaltnet/janssege/Development/Builds/gnucash-f19-trunk/src/optional/python-bindings/tests'
rm -f runTests.py.tmp
sed < /kobaltnet/janssege/Development/EclipseGnuCash/GnuCash-git/src/optional/python-bindings/tests/runTests.py.in > runTests.py.tmp \
    -e 's#@-PYTHON-@#/usr/bin/python#'
mv runTests.py.tmp runTests.py
chmod u+x runTests.py
/kobaltnet/janssege/Development/EclipseGnuCash/GnuCash-git/test-driver: line 95: 31911 Trace/breakpoint trap   (core dumped) "$@" > $log_file 2>&1
FAIL: runTests.py

This is the content of the test's log file:
* 15:51:49  CRIT <GLib> g_str_has_prefix: assertion `prefix != NULL' failed
* 15:51:49 OTHER <GLib-GIO> Settings schema '' is not installed

The log file suggests that the test aborted because gsettings is not finding it's schemas. GSettings is known to abort the runnig program in such situation.

The difficulty in fixing this is that gsettings schemas are only available after a successful "make install" run. That's how the gsettings make rules work.

We may circumvent this problem if the tests never reach a code path in which gsettings is used. That will have to be investigated.