I'm working with a CODESYS 3.5 unit test framework on an embedded Linux PLC and running into an issue where a phantom test slot appears in the results that never completes, preventing the full test suite from ever finishing.
The symptom:
A blank-named test entry appears in the results table with an ever-increasing action count. It stays as "Testing" or "Failing" indefinitely. Because it never closes, bAllFinished never goes TRUE and the final report is never generated.
Question:
Has anyone seen this kind of phantom slot issue in a CODESYS unit testing setup?
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
I'm working with a CODESYS 3.5 unit test framework on an embedded Linux PLC and running into an issue where a phantom test slot appears in the results that never completes, preventing the full test suite from ever finishing.
The symptom:
A blank-named test entry appears in the results table with an ever-increasing action count. It stays as "Testing" or "Failing" indefinitely. Because it never closes, bAllFinished never goes TRUE and the final report is never generated.
Question:
Has anyone seen this kind of phantom slot issue in a CODESYS unit testing setup?
Thanks