# cmocka 1.1.7+git (SRCREV a01cc69ee9536f90e57c61a198f2d1944d3d4313) -- the
# NATIVE x86_64 control run, and the oracle 77-cmocka.test scores the target
# against.
#
# Built from the identical source with the recipe's own configuration:
#   cmake -DCMAKE_BUILD_TYPE=Debug -DUNIT_TESTING=ON \
#         -DBUILD_SHARED_LIBS=OFF -DWITH_EXAMPLES=OFF
# then each tests/test_* executed directly and its exit status recorded.
#
# WHY THE EXIT STATUS IS A TRUE ORACLE AND NOT A CONVENIENCE. cmocka's status is
# its COUNT OF FAILED TESTS, and every count here is fixed by the suite's own
# control flow: test_ordering_fail asserts that seven specific mis-ordered mock
# calls are each caught, so it exits 7 when cmocka works and something other
# than 7 when it does not. None of these numbers carries a pointer width, a
# sizeof, an address or a timing, so nothing in them is ALLOWED to differ
# between x86_64 and wasm32 -- a single disagreement is a defect on this arm
# rather than a platform difference to reason about.
#
# SEVEN OF THE 23 FAIL ON PURPOSE. They are cmocka's tests OF ITS OWN FAILURE
# REPORTING, and upstream marks them WILL_FAIL / PASS_REGULAR_EXPRESSION in
# tests/CMakeLists.txt. run-ptest transcribes those properties, so an expected
# failure must also fail for the expected REASON.
#
# Columns: <binary> <exit status> <PASSED counts, comma-separated per group>
#          ("0" passed is correct for a suite whose every test is a by-design
#           failure, and for test_skip, whose one test skips.)

test_alloc 0 3
test_assert_macros 0 1
test_assert_macros_fail 1 0
test_basics 0 2
test_cmockery 0 1
test_double_macros 0 1
test_exception_handler 3 0
test_fixtures 0 8
test_float_macros 0 1
test_group_fixtures 0 3
test_group_setup_assert 1 0
test_group_setup_fail 1 0
test_groups 0 1,1
test_ordering 0 7
test_ordering_fail 7 0
test_returns 0 3
test_returns_fail 3 0
test_setup_fail 1 1
test_skip 0 0
test_skip_filter 0 1
test_string 0 2
test_strmatch 0 4
test_wildcard 0 2