Twister is more useful in a CI context because we can easily test
multiple combinations of the firmware using a single command.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
These actions are triggering warnings about usage of deprecated features
(e.g. NodeJS 12). Use latest version of the actions.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Schedule a daily build, so that we can quickly spot regressions in the
application due to changes in Zephyr.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
This is not necessary since it's running in the zephyr docker image,
that already contains them.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Enhance the example-application repository with a configurable,
trivial library example and associated test cases.
.
This implementation appears to make no assumptions.
.
This implementation was verified by running the following commands
in an example-application workspace and verifying all tests passed.
1. `west build -b native_posix -p always example-application/tests/lib/custom_lib/`
2. `./build/zephyr/zephyr.exe`
3. `west build -b native_posix -p always example-application/tests/lib/custom_lib/ -- -DCONFIG_CUSTOM_LIB_GET_VALUE_DEFAULT=6`
4. `./build/zephyr/zephyr.exe`
5. `zephyr/scripts/twister -T example-application/tests/ \
-p qemu_cortex_m0`
6. `cd zephyr/doc && make clean && make` built cleanly.
.
Note that `twister` does not follow the `zephyr/module.yml:tests`
setting to discover tests in modules, so the testcase-root must be
explicitly provided.
Fixes#35177
Signed-off-by: Gregory Shue <gregory.shue@legrand.us>
-s/--source is a legacy option. There's a proposal to actually use it
for something else in Zephyr now:
https://github.com/zephyrproject-rtos/zephyr/pull/40669
Let's update README.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
Fixes: #39270
The latest zephyrprojectrtos/ci no longer sets ZEPHYR_SDK_INSTALL_DIR
in the environment and doesn't register the Zephyr-SDK as a CMake
package in the CMake package registry.
To ensure the the Zephyr SDK can be correctly discovered by
find_package(Zephyr-sdk) we add `/opt/toolchains` to the
CMAKE_PREFIX_PATH environment variable which is a list containing
additional search prefixes for the `find_package()` function.
Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>