zephyr/tests/subsys/logging
Anas Nashif d0be1de99e tests: logging: disable logging stack test
This test keeps breaking whenever something in kernel or
architecture code changes. If we are to track footprint and stack, it
should be done in some other way.
The value of the test deminished if we have to change the boundaries
every second day.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2022-07-12 22:46:05 -04:00
..
log_api tests: logging/log_api: add bits to test backend events 2022-07-11 11:09:31 +02:00
log_backend_fs tests: migrate includes to <zephyr/...> 2022-05-06 20:02:14 +02:00
log_backend_init logging: Removing v2 suffix from logging names 2022-06-23 15:46:37 -04:00
log_benchmark logging: Removing v2 suffix from logging names 2022-06-23 15:46:37 -04:00
log_core_additional logging: Removing v2 suffix from logging names 2022-06-23 15:46:37 -04:00
log_immediate tests: log_immediate: Increase tests timeout 2022-06-16 16:01:41 -04:00
log_msg logging: Removing v2 suffix from logging names 2022-06-23 15:46:37 -04:00
log_output logging: Allow for compilation without log_output 2022-07-04 16:43:32 +02:00
log_stack tests: logging: disable logging stack test 2022-07-12 22:46:05 -04:00
log_stress tests: log: stress: Adapt to logging API changes 2022-07-04 17:59:34 +02:00
log_switch_format tests: log_switch_format: Add mock backend and remove harness console 2022-07-08 20:10:42 +00:00
log_syst logging: Allow for compilation without log_output 2022-07-04 16:43:32 +02:00