zephyr/tests/kernel/fatal/exception
Andy Ross eb3734168a tests/kernel/fatal/exception: Remove ticked kernel from stack sentinel test
The "sentinel" variant of this test runs the same code, but enables
the stack sentinel feature.  Inexplicably, it's also disabling
TICKLESS_KERNEL, forcing a timer interrupt at every tick boundary.

That doesn't seem to be required for any test functionality I can see.

And worse, by changing that setting without adjusting the tick rate,
it runs afoul of more modern platforms which were designed with
tickless operation in mind.  Specifically, the intel_adsp platforms
have a default tick rate of 50 kHz, which is just too fast for
reasonable operation.  It leaves almost no time available for
application code and something falls behind and fails.

Just remove it.

Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2021-01-04 20:40:55 -05:00
..
src tests: exception: workaround agressive optimization 2020-10-06 11:41:23 -04:00
CMakeLists.txt test: fatal exception: Modify test case file location 2020-09-17 21:37:39 -04:00
prj_arm_fpu_sharing.conf tests: kernel: exception: use cbprintf_nano for arm fpu 2020-12-08 09:25:36 -05:00
prj_armv8m_mpu_stack_guard.conf test: fatal exception: Modify test case file location 2020-09-17 21:37:39 -04:00
prj.conf test: fatal exception: Modify test case file location 2020-09-17 21:37:39 -04:00
protection_no_userspace.conf test: fatal exception: Modify test case file location 2020-09-17 21:37:39 -04:00
README test: fatal exception: Modify test case file location 2020-09-17 21:37:39 -04:00
sentinel.conf tests/kernel/fatal/exception: Remove ticked kernel from stack sentinel test 2021-01-04 20:40:55 -05:00
testcase.yaml test: fatal exception: Modify test case file location 2020-09-17 21:37:39 -04: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.