applications: machine_learning: Update sample.yaml file

[maje-emb]

Added entry for the board nrf54l15dk/nrf54l15/cpuapp in the sample.yaml file.

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 2

Inputs:

Sources:

sdk-nrf: PR head: 3236eced05e75dd61dd03182bb13f53ba3a6612c

more details

sdk-nrf:

PR head: 3236eced05e75dd61dd03182bb13f53ba3a6612c
merge base: d126a9cb195cfad737b9f8bc5d4f9e0f8c3218e7
target head (main): b4851abf9b0a48c77b133768b1b7012ab15c09dd
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (1)

applications
│  ├── machine_learning
│  │  │ sample.yaml

Outputs:

Toolchain

Version: b77d8c1312
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:b77d8c1312_912848a074

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
  • sdk-nrf test count: 57
• ✅ Integration tests
  • ✅ test-fw-nrfconnect-apps

Disabled integration tests

• • desktop52_verification
  • doc-internal
  • test_ble_nrf_config
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-boot
  • test-fw-nrfconnect-chip
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_mosh
  • test-fw-nrfconnect-nrf-iot_nrf_provisioning
  • test-fw-nrfconnect-nrf-iot_positioning
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-ps
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-thread
  • test-fw-nrfconnect-zigbee
  • test-low-level
  • test-sdk-audio
  • test-sdk-dfu
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-pmic-samples
  • test-sdk-sidewalk
  • test-sdk-wifi
  • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[NordicBuilder]

You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds.

Note: This comment is automatically posted by the Documentation Publish GitHub Action.

[grochu]

The change looks good. Just wanted to clarify: is it correct, that building for nrf54l15dk/nrf54l15/cpuapp will result in single-core configuration with simulated sensor? Then maybe nRF54L15 build should be mentioned in https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/applications/machine_learning/app_desc.html#nrf_machine_learning_build_types to make the table complete?

[maje-emb]

The change looks good. Just wanted to clarify: is it correct, that building for nrf54l15dk/nrf54l15/cpuapp will result in single-core configuration with simulated sensor? Then maybe nRF54L15 build should be mentioned in https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/applications/machine_learning/app_desc.html#nrf_machine_learning_build_types to make the table complete?

Yes, that's right, building for nrf54l15dk/nrf54l15/cpuapp will result in a single core configuration with a simulated sensor.
But this does not require additional configuration of prj_singlecore.conf. This is the default configuration from prj.conf.
So it seems to me that we don't need to update this table.

[shanthanordic]

approved for scope