60b18711f3
Many test configs are the same, remove complexity and duplication by using just one kernel config where applicable. This removes the usage of ARCH which is a remnant from the days where we had to specify the architecture of the board, the architecture is now part of Kconfig and determined basded on the board configuration. This will also make it easy adding new architectures to test cases without having to add an architecture specific config file when it is actually not needed, for example now that we will enable micro-kernel support on ARC. Jira: ZEP-238 Change-Id: I143fa3c4629c58329cfeb0c761c7a896fc1ef63a Signed-off-by: Anas Nashif <anas.nashif@intel.com> |
||
|---|---|---|
| .. | ||
| src | ||
| Makefile | ||
| prj.conf | ||
| prj.mdef | ||
| README.txt | ||
| testcase.ini | ||
Test Description ---------------- The object tracing test is a sanity test to verify that the object tracing API remains healthy on both the nanokernel and microkernel. It uses the philsophers as a common 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.