full.config is meant to be a snippet that enables as much as possible to increase coverage beyond what's in the defconfig, e.g. to enable selftests for a wider range of functionality. We have no configs enabling CONFIG_JWT, so this is currently not tested. Enable it in full.config to increase test coverage. Next step would be enabling this for CI. This will have to wait until a bthread related failure for x86 is fixed, which will be tackled separately. Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> --- common/boards/configs/full.config | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/common/boards/configs/full.config b/common/boards/configs/full.config index 547100bacc39..8c42b431f970 100644 --- a/common/boards/configs/full.config +++ b/common/boards/configs/full.config @@ -1,3 +1,9 @@ +CONFIG_COMPILE_TEST=y CONFIG_BTHREAD=y CONFIG_CMD_BTHREAD=y CONFIG_PROGRESS_NOTIFIER=y +CONFIG_JWT=y +CONFIG_DIGEST=y +CONFIG_DIGEST_SHA256_GENERIC=y +CONFIG_DIGEST_SHA384_GENERIC=y +CONFIG_DIGEST_SHA512_GENERIC=y -- 2.39.5
