The sample did not specify any tests in its sample.yaml file, causing CI failures. Additionally, the sample requires to generate secure key before building the sample, otherwise the build fails. For the CI needs, specify a dummy test key, which is only included if the build was triggered by Twister. For this, specify a USE_DUMMY_KEY variable in the sample.yaml file. Finally, fix some minor build issues in the sample itself - remove unused variable, and remove deleted (and also unneeded) mbed TLS header inclusion. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
13 lines
299 B
YAML
13 lines
299 B
YAML
sample:
|
|
description: MQTT sample app to Google IoT cloud
|
|
name: google_iot_mqtt
|
|
common:
|
|
tags: net mqtt cloud
|
|
harness: net
|
|
filter: TOOLCHAIN_HAS_NEWLIB == 1
|
|
extra_args: USE_DUMMY_KEY=1
|
|
tests:
|
|
sample.net.cloud.google_iot_mqtt:
|
|
depends_on: netif
|
|
platform_allow: frdm_k64f qemu_x86
|