zephyr

History

Anas Nashif 9a183fa912 tests: sys_mutex: do not use TC_START for debugging TC_START is used to evaluate output of tests and is used internally by ztest when a test starts, no need to call this manually here. Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2023-04-05 10:27:28 +02:00
..
src	tests: sys_mutex: do not use TC_START for debugging	2023-04-05 10:27:28 +02:00
CMakeLists.txt
prj.conf	tests: kernel: syst_mutex: move to new ztest API	2022-08-03 18:43:42 +02:00
README.txt
testcase.yaml

README.txt

Title: Mutex APIs

Description:

This test verifies that the kernel mutex APIs operate as expected.

--------------------------------------------------------------------------------

Building and Running Project:

This project outputs to the console.  It can be built and executed
on QEMU as follows:

    make run

--------------------------------------------------------------------------------

Troubleshooting:

Problems caused by out-dated project information can be addressed by
issuing one of the following commands then rebuilding the project:

    make clean          # discard results of previous builds
                        # but keep existing configuration info
or
    make pristine       # discard results of previous builds
                        # and restore pre-defined configuration info

--------------------------------------------------------------------------------

Sample Output:

***** BOOTING ZEPHYR OS vxxxx - BUILD: xxxxx *****
tc_start() - Test kernel Mutex API
===================================================================
Done LOCKING!  Current priority = 5
Testing recursive locking
Recursive locking tests successful
===================================================================
PASS - RegressionTask.
===================================================================
PROJECT EXECUTION SUCCESSFUL