6eef2f1485
The mbedtls test is hitting a compiler bug where two subtests will soft fail on qemu_xtensa when assertions are enabled. This is despite the fact that: + The failure is entirely internal to the mbedtls suite. + The mbedtls code does not use zephyr asserts + The mbedtls code does not call into zephyr code that might assert. + The behavior persists even when an irq_lock() is held across the entire test, ruling out any asserts in interrupt/exception context. + And EVEN WHEN the mbedtls library blobs are bytewise identical between assert and non-assert cases. The bug seems to be a layout thing where the mbedtls code behavior differently based on code address and/or link-time optimizations (xtensa has a few). Unfortunately sanitycheck enables assertions by setting CFLAGS directly and not via kconfig, so we can't fix this by turning the feature off in an app right now. This patch adds a simple "override" flag that can be set by apps like this that hit bugs. Again, note that zephyr assertions are not used nor needed by this one test. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
---|---|---|
.. | ||
src | ||
CMakeLists.txt | ||
prj.conf | ||
testcase.yaml |