zephyr/tests/legacy/kernel/test_obj_tracing/microkernel/README.txt
Allan Stephens 7dabe23485 kernel/test: Use custom code in object tracing tests
Microkernel and nanokernel versions of the test now use distinct
sets of source files. This eliminates the dependency on the
MICROKERNEL and NANOKERNEL configuration options, which the
unified kernel doesn't set correctly in all cases.

Change-Id: I59e1d4a73265a433f526d030d2fd04d4b8de1973
Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
2016-11-02 21:56:25 +00:00

18 lines
678 B
Plaintext

Test Description
----------------
The object tracing test is a sanity test to verify that the
object tracing API remains healthy.
It uses the philsophers as an application that implements
multiple taks that are synchronized with mutexes.
The application initializes their objects and starts the philosophers'
task interaction. A specific task, called object monitor, accesses
the object tracing API and reports the number of expected objects.
The sanity test script expects each test to finish its execution
and then it considers the test completed. For that reason the
philosophers' threads execute a finite number of iterations. After
that the application execution ends.