zephyr/samples/synchronization/sample.yaml

sample:
  description: A simple application that demonstrates
    basic sanity of the kernel.
  name: Synchronization Sample
tests:
  sample.kernel.synchronization:
    tags: synchronization
    build_on_all: true
    harness: console
    harness_config:
      type: multi_line
      regex:
        - "thread_a: Hello World from (.*)!"
        - "thread_b: Hello World from (.*)!"
tests: samples: convert testcase files to yaml This will prepare test cases and samples with metadata and information that will be consumed by the sanitycheck script which will be changed to parse YAML files instead of ini. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-04-05 05:11:22 +02:00			`sample:`
tests: samples: fix yaml syntax Fix indentation and syntax and make it pass yamllint tool. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-10-14 18:08:08 +02:00			`description: A simple application that demonstrates`
			`basic sanity of the kernel.`
			`name: Synchronization Sample`
tests: samples: convert testcase files to yaml This will prepare test cases and samples with metadata and information that will be consumed by the sanitycheck script which will be changed to parse YAML files instead of ini. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-04-05 05:11:22 +02:00			`tests:`
tests: fix test identifiers 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> 2019-12-01 18:29:43 +01:00			`sample.kernel.synchronization:`
tests: remove kernel tag from key tests/samples Thos tests/samples are used to build any PR onl all available boards to verify basic sanity. Having the kernel tag means they can get excluded for random non-kernel changes causing regressions. so remove kernel tag to keep them in all CI runs. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2021-07-08 14:49:04 +02:00			`tags: synchronization`
samples: synchronization: build this sample on all platforms Try to catch issues related to platforms and HAL changes using this basic sample. We have the same flag for a kernel test, but this is skipped if no kernel changes are present in the PR, so we were missing some coverage of platform related changes. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2023-09-20 15:26:34 +02:00			`build_on_all: true`
samples: remove build_only from various samples Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-11 02:05:44 +01:00			`harness: console`
sample: synchronization: support console harness Evaluate console output of sample. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-24 16:11:39 +01:00			`harness_config:`
			`type: multi_line`
			`regex:`
samples: synchronization: show cpu Show which CPU were are running on systems with SMP enabled. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2020-08-04 22:42:28 +02:00			`- "thread_a: Hello World from (.*)!"`
			`- "thread_b: Hello World from (.*)!"`