mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-16 11:15:55 +00:00
62077917b6
This adds unit test for microkernel private tasks. The code piggybacks to the public task test (by including the same source file), so any updates to the test will be applied to both. Note that the prj.mdef are different for both tests, since the private tasks test move the tasks inside source code. So, both mdef files will need to be updated at the same time. Change-Id: I2890f70be460c0e45208ce03d6e7897d2662f6f0 Signed-off-by: Daniel Leung <daniel.leung@intel.com> |
||
|---|---|---|
| .. | ||
| arches | ||
| .gitignore | ||
| bt_regression_chk | ||
| bt_regression_chk.data | ||
| common.defs | ||
| footprint_chk | ||
| footprint_chk.data | ||
| out-of-tree_chk | ||
| out-of-tree_chk.data | ||
| README.txt | ||
| regression_chk | ||
| regression_chk.data | ||
| sanity_chk | ||
| sanity_last_release.csv | ||
Sanity Check Data Files ======================= The sanity check data files contain project metadata that is parsed by the relevant sanity check script to both build and run the listed projects. Project metadata consists of: - project directory (relative to PRJ_PATH - defined in the script) - build arguments (optional) - project flags, enclosed in angle brackets "<>" - 'u' => microkernel; 'n' => nanokernel (required; must be first flag) - 'q' => run as part of quick sanity check (optional) - list of platform names that can be used with the project It is important that each set of project metadata be specified on a single line. The sanity check scripts will select first listed platform name if the user does not specify a platform name (i.e. is the "default" platform). A given project can appear more than once, allowing the project to be sanitized multiple times. This can be useful if the project has multiple configurations, or if the project should be characterized on more than one platform during a default platform sanity check. Comment lines are permitted (denoted by '#').