70758c4374
The seasonal overhaul of test identifiers aligning the terms being used and creating a structure. This is hopefully the last time we do this, plan is to document the identifiers and enforce syntax. The end-goal is to be able to generate a testsuite description from the existing tests and sync it frequently with the testsuite in Testrail. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
24 lines
684 B
YAML
24 lines
684 B
YAML
tests:
|
|
benchmark.kernel.timing.default:
|
|
arch_exclude: posix
|
|
tags: benchmark
|
|
harness: console
|
|
harness_config:
|
|
type: one_line
|
|
record:
|
|
regex: "(?P<metric>.*):(?P<cycles>.*) cycles ,(?P<nanoseconds>.*) ns"
|
|
regex:
|
|
- "PROJECT EXECUTION SUCCESSFUL"
|
|
benchmark.kernel.timing.userspace:
|
|
filter: CONFIG_ARCH_HAS_USERSPACE
|
|
extra_args: CONF_FILE=prj_userspace.conf
|
|
arch_whitelist: x86 arm arc
|
|
tags: benchmark userspace
|
|
harness: console
|
|
harness_config:
|
|
type: one_line
|
|
record:
|
|
regex: "(?P<metric>.*):(?P<cycles>.*) cycles ,(?P<nanoseconds>.*) ns"
|
|
regex:
|
|
- "PROJECT EXECUTION SUCCESSFUL"
|