You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Closure of bug #14500 via pull request #15005 remove the majority of coverage error. (Thank you for the effort. I appreciate it a lot)
I am trying not to look a gift horse in the mouth, but here are the remaining errors after merging #15005.
===================================================================
starting test - test_mpool_alloc_timeout
***** USAGE FAULT *****
Illegal use of the EPSR
***** Hardware exception *****
Current thread ID = 0x200148a0
Faulting instruction address = 0x2001c11c
Fatal fault in essential thread! Spinning...
starting test - Test kernel Mutex API
===================================================================
***** MPU FAULT *****
Stacking error (context area might be not valid)
Data Access Violation
MMFAR Address: 0x2001cdc0
***** Stack Check Fail! *****
Current thread ID = 0x20010214
Faulting instruction address = 0x0
Fatal fault in thread 0x20010214! Aborting.
Assertion failed at /home/cinlyooi/tests/zephyrproject/zephyr/tests/kernel/mutex/sys_mutex/src/main.c:284: test_mutex: tc_rc not equal to TC_PASS
[100%] [QEMU] CPU: qemu32,+nx,+pae
QEMU 3.1.0 monitor - type 'help' for more information
(qemu) make[4]: *** [zephyr/CMakeFiles/run.dir/build.make:58: zephyr/CMakeFiles/run] Error 1
[100%] [QEMU] CPU: qemu32,+nx,+pae
QEMU 3.1.0 monitor - type 'help' for more information
(qemu) make[4]: *** [zephyr/CMakeFiles/run.dir/build.make:58: zephyr/CMakeFiles/run] Error 1
[100%] [QEMU] CPU: qemu32,+nx,+pae
QEMU 3.1.0 monitor - type 'help' for more information
(qemu) make[4]: *** [zephyr/CMakeFiles/run.dir/build.make:58: zephyr/CMakeFiles/run] Error 1
eaBIOS (version rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org)
Booting from ROM..***** Booting Zephyr OS v1.14.0-rc3-113-g0c59471436e2 *****
Running test suite thread_init
===================================================================
starting test - test_kdefine_preempt_thread
PASS - test_kdefine_preempt_thread
===================================================================
starting test - test_kdefine_coop_thread
The text was updated successfully, but these errors were encountered:
cinlyooi-intel
changed the title
sanitycheck --coverage: stack overflows on qemu_x86 and mps2_an385
sanitycheck --coverage: stack overflows on qemu_x86, mps2_an385 and qemu_x86_nommu
Apr 5, 2019
for SDK 0.10.0, it consumes more stack size when coverage
enabled, so adjust stack size to fix stack overflow issue.
Fixes: zephyrproject-rtos#15206.
Signed-off-by: Wentong Wu <[email protected]>
wentongwu
added a commit
to wentongwu/zephyr
that referenced
this issue
Apr 9, 2019
for SDK 0.10.0, it consumes more stack size when coverage
enabled, so adjust stack size to fix stack overflow issue.
Fixes: zephyrproject-rtos#15206.
Signed-off-by: Wentong Wu <[email protected]>
for SDK 0.10.0, it consumes more stack size when coverage
enabled, so adjust stack size to fix stack overflow issue.
Fixes: #15206.
Signed-off-by: Wentong Wu <[email protected]>
for SDK 0.10.0, it consumes more stack size when coverage
enabled, so adjust stack size to fix stack overflow issue.
Fixes: #15206.
Signed-off-by: Wentong Wu <[email protected]>
Describe the bug
Closure of bug #14500 via pull request #15005 remove the majority of coverage error. (Thank you for the effort. I appreciate it a lot)
I am trying not to look a gift horse in the mouth, but here are the remaining errors after merging #15005.
To Reproduce
It is confirmed that, if I am not running code coverage, i.e.
all the test that failed in coverage tests, passed here.
Environment (please complete the following information):
** Failures **
For:
see: sanity-out/mps2_an385/tests/kernel/fatal/kernel.common.stack_sentinel/run.log
see: sanity-out/mps2_an385/tests/kernel/mem_protect/mem_protect/kernel.memory_protection/run.log
see: sanity-out/mps2_an385/tests/kernel/arm_irq_vector_table/arch.interrupt/handler.log
see: sanity-out/mps2_an385/tests/kernel/mem_protect/mem_protect/kernel.memory_protection/run.log
see: sanity-out/mps2_an385/tests/kernel/lifo/lifo_usage/kernel.lifo.usage/handler.log
see: sanity-out/mps2_an385/tests/kernel/mem_pool/mem_pool_api/kernel.memory_pool/handler.log
see: sanity-out/mps2_an385/tests/kernel/mem_protect/stackprot/kernel.memory_protection/handler.log
see: sanity-out/mps2_an385/tests/kernel/mem_protect/userspace/kernel.memory_protection.userspace/handler.log
No output in handler.log
see: sanity-out/mps2_an385/tests/kernel/mutex/sys_mutex/kernel.mutex/handler.log
This one has GCOV data.
see: sanity-out/mps2_an385/tests/kernel/pipe/pipe/kernel.pipe/handler.log
This one has GCOV data
see: sanity-out/mps2_an385/tests/kernel/profiling/profiling_api/kernel.profiling/handler.log
see: sanity-out/mps2_an385/tests/kernel/timer/timer_api/kernel.timer/handler.log
This one has GCOV data
see: sanity-out/mps2_an385/tests/kernel/threads/thread_apis/kernel.threads/handler.log
68/214 mps2_an385 tests/subsys/logging/log_core/logging.log_core PASSED
see: sanity-out/qemu_x86/tests/kernel/mem_pool/mem_pool_api/kernel.memory_pool/run.log
see: sanity-out/qemu_x86/tests/kernel/mem_protect/stackprot/kernel.memory_protection/run.log
see: sanity-out/qemu_x86/tests/kernel/pipe/pipe/kernel.pipe/handler.log
see: sanity-out/qemu_x86_nommu/tests/kernel/mem_protect/stackprot/kernel.memory_protection/run.log
179/214 qemu_x86_nommu tests/kernel/mutex/sys_mutex/kernel.mutex FAILED: failed
see: sanity-out/qemu_x86_nommu/tests/kernel/mutex/sys_mutex/kernel.mutex/handler.log
214/214 qemu_x86_nommu tests/kernel/threads/thread_init/kernel.threads FAILED: timeout
see: sanity-out/qemu_x86_nommu/tests/kernel/threads/thread_init/kernel.threads/handler.log
The text was updated successfully, but these errors were encountered: