samples/basic/threads/sample.yaml

sample:
  description: A basic demo to showcase multi-threading using K_THREAD_DEFINE
  name: Basic Thread Demo
tests:
  sample.basic.threads:
    tags:
      - kernel
      - threads
      - gpio
    filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds") and
            dt_enabled_alias_with_parent_compat("led1", "gpio-leds")
    integration_platforms:
      - nrf52833dk_nrf52820
    depends_on: gpio
    harness: console
    harness_config:
      type: multi_line
      ordered: false
      regex:
        - "Toggled led0; counter=(.*)"
        - "Toggled led1; counter=(.*)"
samples: Basic Thread Demo A basic demo to showcase multi-threading using K_THREAD_DEFINE Signed-off-by: Sahaj Sarup <sahaj.sarup@linaro.org> 2017-10-26 23:35:38 +05:30			`sample:`
samples, tests: convert string-based twister lists to YAML lists Twister now supports using YAML lists for all fields that were written as space-separated lists. Used twister_to_list.py script. Some artifacts on string length are due to how ruamel dumps content. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> 2023-05-08 13:37:42 +02:00			`description: A basic demo to showcase multi-threading using K_THREAD_DEFINE`
samples: Basic Thread Demo A basic demo to showcase multi-threading using K_THREAD_DEFINE Signed-off-by: Sahaj Sarup <sahaj.sarup@linaro.org> 2017-10-26 23:35:38 +05:30			`name: Basic Thread Demo`
			`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 12:29:43 -05:00			`sample.basic.threads:`
samples, tests: convert string-based twister lists to YAML lists Twister now supports using YAML lists for all fields that were written as space-separated lists. Used twister_to_list.py script. Some artifacts on string length are due to how ruamel dumps content. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> 2023-05-08 13:37:42 +02:00			`tags:`
			`- kernel`
			`- threads`
			`- gpio`
twister: replace dt_compat_enabled_with_alias filter Originally added in 7733b942246cfbfa354328d28a8a469e1c135f37. This filter is not well-formed. It's meant to match nodes like /leds/led_0 in this DTS: / { aliases { led0 = &led0; }; leds { compatible = "gpio-leds"; led0: led_0 { gpios = <...>; label = "LED 0"; }; }; }; Uses look like this: filter: dt_compat_enabled_with_alias("gpio-leds", "led0") But notice how the led_0 node doesn't have compatible "gpio-leds"; it's actually the parent node that has that compatible. Replace this with a new filter, dt_enabled_alias_with_parent_compat(), which is used like this: filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds") This has a name and argument order that makes the meaning of the filter clearer. Replace in-tree users with the new filter. Deprecate the old filter and warn about its use using the standard logging module. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2021-02-26 07:50:27 -08:00			`filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds") and`
			`dt_enabled_alias_with_parent_compat("led1", "gpio-leds")`
tests: cleanup metadata and filtering - Add integration_platforms to avoid excessive filtering - Make sure integration platforms are actually part of the filter - Fix some tags and test meta data Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2023-06-09 12:30:46 +00:00			`integration_platforms:`
			`- nrf52833dk_nrf52820`
samples: threads: Fix ASSERTION FAIL without gpio driver Some boards' configuration does not enable GPIO by default, like nrf52_pca10056, it causes ASSERTION FAIL when running this application. This fix is to enable GPIO by default for the basic threads sample, like basic blinky sample does. Signed-off-by: Aaron Tsui <aaron.tsui@outlook.com> 2019-02-22 14:24:59 +08:00			`depends_on: gpio`
samples: define harness for samples Most of the basic tests trigger LEDs or expect button press and would hang in device testing because we can't parse success or failure from the console. Define harness for this with the intent to skip those in sanitycheck device testing and until we have a better way to test those. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-03-03 10:07:25 -05:00			`harness: console`
			`harness_config:`
			`type: multi_line`
			`ordered: false`
			`regex:`
samples: threads: cleanups Align the docs and source code with other changes done to the basic samples. Use numbers 0 and 1 to refer to the LEDs consistently. This matches the generic devicetree aliases used by Zephyr, instead of using USR1 and USR2, which are specific to 96b_carbon. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2020-05-04 13:25:36 -07:00			`- "Toggled led0; counter=(.*)"`
			`- "Toggled led1; counter=(.*)"`