mutex and semaphore tests timeout or fail to build

[HeatCrab]

The mutex and semaphore functional tests fail on both GNU and LLVM toolchains with different failure modes. This issue was discovered in PR #32 through the newly added CI workflow (merged in #12). On GNU toolchain, both tests build successfully but timeout after 5 seconds, suggesting the tests hang indefinitely. On LLVM toolchain, both tests fail to build.

GNU toolchain output:

DEBUG] Functional output received (length: 891)
[DEBUG] Found 2 FUNCTIONAL_TEST lines
[DEBUG] Found 5 FUNCTIONAL_CRITERIA lines
[DEBUG] Last 50 lines of functional output:
[+] Linmo Functional Test Suite (Step 3)
[+] Toolchain: gnu
[+] Timeout: 5s per test

[+] Running all functional tests: mutex semaphore 

=== Functional Test: mutex ===
[+] Building...
[+] Running (timeout: 5s)...
[!] Timeout (test hung)

=== Functional Test: semaphore ===
[+] Building...
[+] Running (timeout: 5s)...
[!] Timeout (test hung)


=== STEP 3 FUNCTIONAL TEST RESULTS ===
Total tests: 2
[!] FAILED (2): mutex semaphore

[DEBUG] About to emit parseable output for 2 tests
=== PARSEABLE_OUTPUT ===
FUNCTIONAL_TEST:mutex=failed
FUNCTIONAL_CRITERIA:mutex:fairness=timeout
FUNCTIONAL_CRITERIA:mutex:mutual_exclusion=timeout
FUNCTIONAL_CRITERIA:mutex:data_consistency=timeout
FUNCTIONAL_CRITERIA:mutex:overall=timeout
FUNCTIONAL_TEST:semaphore=failed
FUNCTIONAL_CRITERIA:semaphore:all_tests_passed!=timeout
[DEBUG] Finished emitting parseable output

[!] Step 3 functional tests FAILED
Test data collected for gnu toolchain

LLVM toolchain output:

[DEBUG] Functional output received (length: 863)
[DEBUG] Found 2 FUNCTIONAL_TEST lines
[DEBUG] Found 5 FUNCTIONAL_CRITERIA lines
[DEBUG] Last 50 lines of functional output:
[+] Linmo Functional Test Suite (Step 3)
[+] Toolchain: llvm
[+] Timeout: 5s per test

[+] Running all functional tests: mutex semaphore 

=== Functional Test: mutex ===
[+] Building...
[!] Build failed

=== Functional Test: semaphore ===
[+] Building...
[!] Build failed


=== STEP 3 FUNCTIONAL TEST RESULTS ===
Total tests: 2
[!] BUILD FAILED (2): mutex semaphore

[DEBUG] About to emit parseable output for 2 tests
=== PARSEABLE_OUTPUT ===
FUNCTIONAL_TEST:mutex=build_failed
FUNCTIONAL_CRITERIA:mutex:fairness=build_failed
FUNCTIONAL_CRITERIA:mutex:mutual_exclusion=build_failed
FUNCTIONAL_CRITERIA:mutex:data_consistency=build_failed
FUNCTIONAL_CRITERIA:mutex:overall=build_failed
FUNCTIONAL_TEST:semaphore=build_failed
FUNCTIONAL_CRITERIA:semaphore:all_tests_passed!=build_failed
[DEBUG] Finished emitting parseable output

[!] Step 3 functional tests FAILED
Test data collected for llvm toolchain

Reproduction

This issue was discovered through the CI workflow. It can be reproduced on any PR that triggers the CI workflow.

Example CI run:

• GNU toolchain log
• LLVM toolchain log