Skip to content

nrf_security: added benchmarking bypass config #26

nrf_security: added benchmarking bypass config

nrf_security: added benchmarking bypass config #26

Triggered via pull request June 2, 2026 13:38
Status Failure
Total duration 2m 21s
Artifacts 1

compliance.yml

on: pull_request
Run compliance checks on patch series (PR)
2m 18s
Run compliance checks on patch series (PR)
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
Run compliance checks on patch series (PR)
Process completed with exit code 1.
Run compliance checks on patch series (PR): KconfigBasic.txt#L0
See https://docs.zephyrproject.org/latest/build/kconfig/tips.html for more details. Undefined Kconfig symbols: warning: undefined symbol PSA_CRYPO_FORCE_OBERON: - Referenced at /home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf/modules/../subsys/nrf_security/src/drivers/Kconfig:9: config PSA_CRYPTO_DRIVER_OBERON bool "Oberon PSA driver" if !(TFM_PARTITION_PROTECTED_STORAGE || TFM_CRYPTO_BUILTIN_KEYS) default y if !HAS_HW_NRF_CRACEN || PSA_CRYPO_FORCE_OBERON depends on PSA_CRYPTO && NRF_SECURITY help This configuration enables the usage of the Oberon PSA driver.
Run compliance checks on patch series (PR): Kconfig.txt#L0
See https://docs.zephyrproject.org/latest/build/kconfig/tips.html for more details. Undefined Kconfig symbols: warning: undefined symbol PSA_CRYPO_FORCE_OBERON: - Referenced at /home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf/modules/../subsys/nrf_security/src/drivers/Kconfig:9: config PSA_CRYPTO_DRIVER_OBERON bool "Oberon PSA driver" if !(TFM_PARTITION_PROTECTED_STORAGE || TFM_CRYPTO_BUILTIN_KEYS) default y if !HAS_HW_NRF_CRACEN || PSA_CRYPO_FORCE_OBERON depends on PSA_CRYPTO && NRF_SECURITY help This configuration enables the usage of the Oberon PSA driver.
Run compliance checks on patch series (PR)
Process completed with exit code 2.
Run compliance checks on patch series (PR)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@d4323d4df104b026a6aa633fdb11d772146be0bf, actions/checkout@v4, actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
compliance.xml
1002 Bytes
sha256:91c7339b155b4c1a19327fbe6a17da165fe7ade35ad3250fc3cb1b62bca26200