#1580

Tests: report unconfigured retail runtime tests as skipped

OpenZebrainewants to merge intofrom

Claimed in the coordination issue as: retail runtime test skips in #1548.

What and why

bink_decode, bink_audio, fsr_dispatch, and bvh_builder print a skip message when their required retail input configuration is absent, then exit 0. Both CTest and the Wine runner count those cases as passes, although the tests did not reach the retail routines.

Return the project's existing skip code 77 in these missing-configuration branches and register SKIP_RETURN_CODE 77 for each CTest entry. The existing Wine runner reads that property. Input validation still reports configured but invalid paths as failures.

Tested

CachyOS x86_64, Wine 11.22, clang-cl 23.1.5, xwin 0.10.0 and Windows SDK 10.0.26100. The host GPU was an AMD RX 7700 XT (RADV Mesa 26.3.1); these checks exited before GPU initialization. No game files were used.

Built all four Windows test targets and ran each with both CTest through Wine and scripts/run_wine_tests.py under the same Wine prefix. The Wine runner used the generated CTest entries with paths mapped to the Windows checkout layout used by CI.

Input configurationCTest through WineWine runner
LEONIDA_GAME_DIR, LEONIDA_MOVIE and LEONIDA_MOVIE_AUDIO unset4 skipped, 0 failed; CTest exit 04 skipped, 0 passed, 0 failed; process exit 77 for all four
All three set to nonexistent paths under a temporary directory4 failed, 0 skipped; CTest exit 84 failed, 0 skipped; process exit 1 for all four, runner exit 1 with all four marked required

For the direct CTest run, configure the xwin build as in docs/testing.md and build bink_decode_test bink_audio_test fsr_dispatch_test bvh_builder_test. Run ctest --test-dir <xwin-build> -R '^(bink_decode|bink_audio|fsr_dispatch|bvh_builder)$' --no-tests=error -V once with the variables unset and again with nonempty Windows paths that do not exist.

AI-assisted (Codex).

Checklist

  • No game data, keys or decryption (CONTRIBUTING.md), including in logs or reports quoted here.
  • A new translator rule is in the contract table of docs/design.md, with how it was confirmed. (N/A, test status change.)