Searched refs:fail (Results 176 – 191 of 191) sorted by relevance
12345678
429 older versions of west will fail with an error message that explains the441 # fail with an error message saying that west v0.10.0 or2103 from :file:`baz/west.yml`, which "should" cause ``west update P`` to fail with an
215 in a new workspace for the first time; this used to fail (just for the first
249 Adding ``required: true`` to a property definition will fail the build if a
672 faill||fail
124 fail the build if the device does not exist.
1470 * :github:`26038` - build zephyr with llvm fail1796 * :github:`18629` - Some tests fail to reach test_main() on cc1352r1_launchxl1812 * :github:`16387` - STM32wb55 bluetooth samples fail
214 than the system workqueue caused the GATT Mesh Proxy Service registration to fail.2239 address in the size which caused serial recovery to fail on some platforms.
1257 …attempting to mount the disk in a global function caused FAT FS to fail due to not being registere…
1319 application would fail to boot properly.
152 include the ``csf`` member, otherwise the build would fail.
649 that retrieving the bitrate limits can no longer fail. Deprecated the existing
610 This means a construct like this will fail:
1107 user applications won't immediately fail to compile.
727 # Without this code, CMake will fail with the following error:
603 will automatically fail the bonding. See "RL limitation" below.
1801 # zephyr_blobs_verify(MODULE my_module REQUIRED) # verify all blobs in my_module and fail on error2749 # Let's check if anyone uses relative path as scoped variable, and fail
