ci: change docker pointer

[karhama]

Currently WIP

[NordicBuilder]

CI Information

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

Inputs:

Sources:

sdk-nrf: PR head: 955c6d59864141c64481f968395ab4f051547a8a

more details

sdk-nrf:

PR head: 955c6d59864141c64481f968395ab4f051547a8a
merge base: b5fe0387bad80d787a633419e2dc109e647668f9
target head (main): 338290ef6f8a0ce5e35047a0fa1b5bed6359c804
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)

scripts
│  │ ncs-docker-version.txt

Outputs:

Toolchain

Version: 53ac68dd62
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:53ac68dd62_454710fe16

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

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
• ❌ Integration tests
  • ❌ test-sdk-audio
  • ✅ desktop52_verification
  • ✅ test-fw-nrfconnect-apps
  • ✅ test_ble_nrf_config
  • ✅ test-fw-nrfconnect-ble_mesh
  • ✅ test-fw-nrfconnect-ble_samples
  • ✅ test-fw-nrfconnect-chip
  • ✅ test-fw-nrfconnect-nfc
  • ✅ test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • ✅ test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • ✅ test-fw-nrfconnect-nrf-iot_samples
  • ✅ test-fw-nrfconnect-nrf-iot_lwm2m
  • ✅ test-fw-nrfconnect-nrf-iot_thingy91
  • ❌ test-fw-nrfconnect-nrf_crypto
  • ✅ test-fw-nrfconnect-rpc
  • ✅ test-fw-nrfconnect-rs
  • ✅ test-fw-nrfconnect-fem
  • ✅ test-fw-nrfconnect-tfm
  • ✅ test-fw-nrfconnect-thread-main
  • ✅ test-sdk-find-my
  • ✅ test-fw-nrfconnect-nrf_lrcs_mosh
  • ✅ test-fw-nrfconnect-nrf_lrcs_positioning
  • ❌ test-sdk-wifi
  • ✅ test-low-level
  • ✅ test-sdk-mcuboot
  • ✅ test-sdk-dfu
  • ✅ test-fw-nrfconnect-ps-main
  • ❌ test-secdom-samples-public

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

[NordicBuilder]

Memory footprint analysis revealed the following potential issues

applications.hpf.gpio.mbox[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 7234[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.mbox[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 3994[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 13010[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 9750[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 9386[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 6134[B] - link (cc: @nrfconnect/ncs-ll-ursus)

Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-28322/6)