zephyr/tests/kernel/fatal/exception
Fabio Baltieri 5c32300861 yamllint: fix all yamllint truthy errors
Fix all thruthy errors detected by yamllint:

yamllint -f parsable -c .yamllint $( find -regex '.*\.y[a]*ml' ) | \
  grep '(truthy)'

This only accepts true/false for boolean properties. Seems like python
takes all sort of formats:

https://github.com/yaml/pyyaml/blob/master/lib/yaml/constructor.py#L224-L235

But the current specs only mention "true" or "false"

https://yaml.org/spec/1.2.2/#10212-boolean

Which is the standard yamllint config.

Excluding codeconv and workflow files, as some are using yes/no instead
in the respective documentation.

Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-01-04 01:16:45 +09:00
..
src includes: prefer <zephyr/kernel.h> over <zephyr/zephyr.h> 2022-09-05 16:31:47 +02:00
CMakeLists.txt
prj_arm_fpu_sharing.conf tests: kernel: exception: move to new ztest API 2022-07-06 21:09:55 -04:00
prj_armv8m_mpu_stack_guard.conf tests: kernel: exception: move to new ztest API 2022-07-06 21:09:55 -04:00
prj.conf tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
protection_no_userspace.conf tests: kernel: exception: move to new ztest API 2022-07-06 21:09:55 -04:00
README
sentinel.conf tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
testcase.yaml yamllint: fix all yamllint truthy errors 2023-01-04 01:16:45 +09:00

This test case verifies that kernel fatal error handling works correctly.

If a thread causes a CPU exception, and it is not in an ISR or "essential"
thread, the thread gets aborted and the rest of the system executes normally.