3.9.12 build test failures
The build tests are failing on Ubuntu 23.10.
Is there also a way to make running these build tests more verbose?
Build log excerpt
../tests/unit-test
Running suite(s): dmap_av_connection
../../src/check_msg.c:80: Unable to report test progress or a failure; was an ck_assert or ck_abort function called while not running tests?
../../src/check_msg.c:80: Unable to report test progress or a failure; was an ck_assert or ck_abort function called while not running tests?
../../src/check_msg.c:80: Unable to report test progress or a failure; was an ck_assert or ck_abort function called while not running tests?
../../src/check_msg.c:80: Unable to report test progress or a failure; was an ck_assert or ck_abort function called while not running tests?
../../src/check_msg.c:80: Unable to report test progress or a failure; was an ck_assert or ck_abort function called while not running tests?
0%: Checks: 5, Failures: 0, Errors: 5
dmap-av-connection.c:205:E:_get_protocol_version_cc_test:_get_protocol_version_cc_test:0: (after this point) Early exit with return value 2
dmap-av-connection.c:214:E:_get_query_metadata_test:_get_query_metadata_test:0: (after this point) Early exit with return value 2
dmap-av-connection.c:229:E:_new_test:_new_test:0: (after this point) Early exit with return value 2
dmap-av-connection.c:270:E:_handle_mlcl_test:_handle_mlcl_test:0: (after this point) Early exit with return value 2
dmap-av-connection.c:370:E:_handle_mlcl_bad_code_test:_handle_mlcl_bad_code_test:0: (after this point) Early exit with return value 2
Full build log
https://launchpad.net/ubuntu/+source/libdmapsharing/3.9.12-1/+latestbuild/amd64