manifest: Update sdk-zephyr and nrfx revision to have extracted cb fo…

[adamkondraciuk]

…r TWI

[NordicBuilder]

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

Name	Old Revision	New Revision	Diff
nrfx	nrfconnect/nrfx@master	https://github.com/nrfconnect/nrfx/pull/1040	nrfconnect/nrfx#1040/files
zephyr	nrfconnect/sdk-zephyr@collab-nrfx	nrfconnect/sdk-zephyr#3505	nrfconnect/sdk-zephyr#3505/files

⛔ DNM label due to: 2 projects with PR revision

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

[NordicBuilder]

CI Information

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

Inputs:

Sources:

sdk-nrf: PR head: 3c49cb183ccce10175a4ca50fbf78dba92772cd5
zephyr: PR head: 6cd16a71b935b206fbe661fe18c53aa44d5e1503

more details

sdk-nrf:

PR head: 3c49cb183ccce10175a4ca50fbf78dba92772cd5
merge base: 04de0eccae40eb93c9c70d285ac92868ca84d84f
target head (collab-nrfx): 04de0eccae40eb93c9c70d285ac92868ca84d84f
Diff

zephyr:

PR head: 6cd16a71b935b206fbe661fe18c53aa44d5e1503
merge base: dd66b34752b0e6015d1ecfdc2ebdd718707bb7eb
target head (collab-nrfx): dd66b34752b0e6015d1ecfdc2ebdd718707bb7eb
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 (11)

west.yml
zephyr
│  ├── drivers
│  │  ├── i2c
│  │  │  ├── Kconfig.nrfx
│  │  │  ├── i2c_nrfx_twi.c
│  │  │  ├── i2c_nrfx_twi_common.c
│  │  │  ├── i2c_nrfx_twi_common.h
│  │  │  │ i2c_nrfx_twi_rtio.c
│  │  ├── spi
│  │  │  ├── Kconfig.nrfx
│  │  │  │ spi_nrfx_spi.c
│  ├── modules
│  │  ├── hal_nordic
│  │  │  ├── nrfx
│  │  │  │  ├── Kconfig
│  │  │  │  │ nrfx_kconfig.h
│  ├── soc
│  │  ├── nordic
│  │  │  ├── common
│  │  │  │  │ Kconfig.peripherals

Outputs:

Toolchain

Version: c3b3fc2dba
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:c3b3fc2dba_5ea73affbf

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: 4
• ✅ Integration tests
  • ✅ test-sdk-audio - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test_ble_nrf_config - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test-fw-nrfconnect-chip - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test-fw-nrfconnect-nfc - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test-fw-nrfconnect-nrf-iot_cloud - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test-fw-nrfconnect-rs - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test-fw-nrfconnect-fem - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test-fw-nrfconnect-thread-main - Skipped: Job was skipped as it succeeded in a previous run
  • ✅ test-sdk-find-my - 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-sdk-dfu - Skipped: Job was skipped as it succeeded in a previous run

Disabled integration tests

• • test-fw-nrfconnect-nrf_lrcs_mosh
  • desktop52_verification
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-ps-main
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-tfm
  • test-sdk-mcuboot
  • test-sdk-wifi
  • test-secdom-samples-public

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

[github-actions]

This pull request has been marked as stale because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 7 days. Note, that you can always re-open a closed pull request at any time.