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>
45 lines
1.2 KiB
YAML
45 lines
1.2 KiB
YAML
common:
|
|
platform_type:
|
|
- qemu
|
|
tags: log_api logging
|
|
skip: true
|
|
integration_platforms:
|
|
- qemu_x86
|
|
tests:
|
|
logging.log_stack_deferred:
|
|
extra_configs:
|
|
- CONFIG_LOG_MODE_DEFERRED=y
|
|
logging.log_stack_deferred_no_opt:
|
|
filter: not CONFIG_MIPS
|
|
extra_configs:
|
|
- CONFIG_LOG_MODE_DEFERRED=y
|
|
- CONFIG_NO_OPTIMIZATIONS=y
|
|
logging.log_stack_immediate:
|
|
extra_configs:
|
|
- CONFIG_LOG_MODE_IMMEDIATE=y
|
|
logging.log_stack_immediate_no_opt:
|
|
filter: not CONFIG_MIPS
|
|
extra_configs:
|
|
- CONFIG_LOG_MODE_IMMEDIATE=y
|
|
- CONFIG_NO_OPTIMIZATIONS=y
|
|
logging.log_stack_deferred_cpp:
|
|
extra_configs:
|
|
- CONFIG_LOG_MODE_DEFERRED=y
|
|
- CONFIG_CPLUSPLUS=y
|
|
logging.log_stack_deferred_cpp_no_opt:
|
|
filter: not CONFIG_MIPS
|
|
extra_configs:
|
|
- CONFIG_LOG_MODE_DEFERRED=y
|
|
- CONFIG_NO_OPTIMIZATIONS=y
|
|
- CONFIG_CPLUSPLUS=y
|
|
logging.log_stack_immediate_cpp:
|
|
extra_configs:
|
|
- CONFIG_LOG_MODE_IMMEDIATE=y
|
|
- CONFIG_CPLUSPLUS=y
|
|
logging.log_stack_immediate_cpp_no_opt:
|
|
filter: not CONFIG_MIPS
|
|
extra_configs:
|
|
- CONFIG_LOG_MODE_IMMEDIATE=y
|
|
- CONFIG_NO_OPTIMIZATIONS=y
|
|
- CONFIG_CPLUSPLUS=y
|