manifest: sdk-zephyr: [nrf noup] samples: bluetooth: hci_ipc: increase main stack size for Cracen driver on nRF54H20

[NordicBuilder]

Automatically created by action-manifest-pr GH action from PR: nrfconnect/sdk-zephyr#2564

[NordicBuilder]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
zephyr	nrfconnect/sdk-zephyr@7fe2732	nrfconnect/sdk-zephyr@b3d63c6 (main)	nrfconnect/[email protected]

✅ All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[NordicBuilder]

CI Information

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

Inputs:

Sources:

sdk-nrf: PR head: 27f53fe9c05a40656048edc01a54bd13039f6f7c
zephyr: PR head: b3d63c6f67c5aaedfdeb652496c4096e12e5526e

more details

sdk-nrf:

PR head: 27f53fe9c05a40656048edc01a54bd13039f6f7c
merge base: 2777cc083da13f2f6b8bb8d97fc37c3216006b5e
target head (main): 200fdcd9a9d7cd1c869e1fe2779a870b31f23a57
Diff

zephyr:

PR head: b3d63c6f67c5aaedfdeb652496c4096e12e5526e
merge base: 7fe2732d7bee0b6825fc30871e95c2a72e641475
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 (5)

west.yml
zephyr
│  ├── drivers
│  │  ├── clock_control
│  │  │  │ clock_control_nrf.c
│  ├── samples
│  │  ├── bluetooth
│  │  │  ├── hci_ipc
│  │  │  │  ├── boards
│  │  │  │  │  │ nrf54h20dk_nrf54h20_cpurad.conf
│  ├── tests
│  │  ├── bluetooth
│  │  │  ├── tester
│  │  │  │  ├── boards
│  │  │  │  │  │ nrf54l15dk_nrf54l15_cpuapp.conf
│  │  │  │  │ overlay-mesh.conf

Outputs:

Toolchain

Version: aedb4c0245
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:aedb4c0245_bece0367df

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

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister - Skipped: Skipping Build & Test as it succeeded in a previous run: 2
• ❌ Integration tests
  • ✅ test-sdk-audio - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test-fw-nrfconnect-ble_samples - Skipped: Job was skipped as it succeeded in a previous run
  • ❌ test-fw-nrfconnect-chip
  • ✅ test-sdk-sidewalk - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test-low-level - Skipped: Job was skipped as it succeeded in a previous run
  • ⚠️ test_ble_nrf_config

Disabled integration tests

• • desktop52_verification
  • doc-internal
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-boot
  • 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_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-proprietary_esb
  • 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-sdk-dfu
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-pmic-samples
  • test-sdk-wifi
  • test-secdom-samples-public

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

[github-actions]

You can find the documentation preview for this PR here.

[gordonklaus]

CI failures are code checks of unrelated code.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gordonklaus]

@nordicjm The latest CI failures are unrelated to this change -- flaky tests, perhaps? How does this work, I'm kinda new here. Can it just be merged, or does CI need to be run again?

[nordicjm]

@nordicjm The latest CI failures are unrelated to this change -- flaky tests, perhaps? How does this work, I'm kinda new here. Can it just be merged, or does CI need to be run again?

Yes, have restarted failed tests

[rlubos]

Manifest already points to the latest sdk-zephyr, this can be closed.