Investigate and fix 5 failing Linux NoCUDA tests

[kumaakh]

Issue Summary

5 tests are currently failing on Linux NoCUDA builds and have been temporarily disabled to get green builds. These tests need to be investigated and fixed.

Failing Tests

mp4readersource_tests (2 tests)

1. mp4v_to_jpg_frames_metadata - base/test/mp4readersource_tests.cpp:130
2. mp4v_to_h264_frames_metadata - base/test/mp4readersource_tests.cpp:166

audioToTextXform_test (3 tests)

3. test_asr - base/test/audioToTextXform_tests.cpp:95
4. changeprop_asr - base/test/audioToTextXform_tests.cpp:135
5. change_unsupported_prop_asr - base/test/audioToTextXform_tests.cpp:192

Context

These tests started failing after fixing the Linux NoCUDA build issues related to OpenAL-Soft/fmt dependency (see build 19801337916).

The tests have been temporarily disabled using *boost::unit_test::disabled() to allow the CI pipeline to pass while investigation proceeds.

Test Characteristics

mp4readersource_tests failures:

• Duration: 6-7 seconds each before failure
• Likely file I/O or timing related issues

audioToTextXform_test failures:

• Duration: 0 seconds (immediate failure)
• Likely missing dependencies, initialization failures, or environment issues

Next Steps

1. Run these tests locally in a Linux environment to reproduce the failures
2. Analyze error logs and stack traces
3. Fix the root cause
4. Re-enable the tests by removing *boost::unit_test::disabled()
5. Verify fixes with CI builds

Related

• Build where failures were observed: https://github.com/Apra-Labs/ApraPipes/actions/runs/19801337916
• Branch: fix/ci-windows-ak

[kumaakh]

🔍 Critical Analysis - Stale Issue

Age: Created Dec 2025 - over 1 month old

Issue: 5 tests disabled on Linux NoCUDA:

• mp4v_to_jpg_frames_metadata
• mp4v_to_h264_frames_metadata
• test_asr, changeprop_asr, change_unsupported_prop_asr

Current State Check:

grep -r 'disabled()' base/test/mp4readersource_tests.cpp base/test/audioToTextXform_tests.cpp

Critical Questions:

1. Are these tests still disabled?
2. Has anyone investigated the root cause?
3. Are these tests blocking any functionality?

Recommendation:

• If tests are still disabled with no investigation, this is technical debt accumulating
• The audio tests failing immediately (0 seconds) suggests missing initialization or dependencies
• Consider: Are these tests even valuable? If the underlying features work in production, maybe the tests are flawed

Priority: Medium - disabled tests reduce confidence in CI

[kumaakh]

🔍 Deep Analysis Update - PR Exists

Associated PR: #491 Enable 8 previously disabled tests
PR Status: Open since Dec 2025
PR Branch: improve-disabled-tests

Update: Found PR #491 which addresses this issue (plus 3 additional tests).

PR #491 enables:

• The 5 tests mentioned in this issue
• 3 additional tests

Decision Required:

1. Review and merge PR Enable 8 previously disabled tests #491 to resolve this issue
2. Request changes if tests are still failing
3. Close both if tests are not worth fixing

@kumaakh - Please review PR #491