-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CI test on Upmerge22073 #22148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
CI test on Upmerge22073 #22148
Conversation
Run migrate_posix_kconfigs.py to rename deprecated POSIX API Kconfig options. GETOPT was replaced by POSIX_C_LIB_EXT which default to n. Remove the obsolete default value change and use the replacement POSIX_C_LIB_EXT. Signed-off-by: Tomasz Moń <[email protected]> Signed-off-by: Johann Fischer <[email protected]>
Update version to upmerged sdk-zephyr and sdk-mcuboot. Signed-off-by: Johann Fischer <[email protected]>
Update Matter SDK revision. Signed-off-by: Adrian Gielniewski <[email protected]>
The combination of AF_PACKET and IPPROTO_RAW is not correct as packet sockets should only be used with IEEE 802.3 protocol numbers. As the support for this combination will likely be soon removed from Zephyr, switch to use DGRAM packet socket instead. Using ETH_P_ALL is fine in this case, as OpenThread interface only provides IPv6 packets anyway. Signed-off-by: Robert Lubos <[email protected]>
The combination of AF_PACKET and IPPROTO_RAW is not correct as packet sockets should only be used with IEEE 802.3 protocol numbers. As the support for this combination will likely be soon removed from Zephyr, switch to use DGRAM packet socket instead. As PPP L2 only supports IP/IPv6 packets, specify the L2 protocol type field accordingly so that the L2 can interpret the packet data correctly. Signed-off-by: Robert Lubos <[email protected]>
The combination of AF_PACKET and IPPROTO_RAW is not correct as packet sockets should only be used with IEEE 802.3 protocol numbers. As the support for this combination will likely be soon removed from Zephyr, switch to use DGRAM packet socket instead. As PPP L2 only supports IP/IPv6 packets, specify the L2 protocol type field accordingly so that the L2 can interpret the packet data correctly. Signed-off-by: Robert Lubos <[email protected]>
Totally unexpected, the exact same Kconfig options and C designators are introduced in the upstream Zephyr repository. Prefix the Kconfig options of the NCS implementation with NRF to resolve the conflicts. Signed-off-by: Johann Fischer <[email protected]>
Refer to commit zephyrproject-rtos/zephyr@d382fca Signed-off-by: Vinayak Kariappa Chettimada <[email protected]>
last_erased_page_start_offset has been removed by zephyrproject-rtos/zephyr#82326. Need to change accordingly to not break the build. Signed-off-by: Maximilian Deubel <[email protected]>
This has been renamed upstream. Signed-off-by: Timothy Keys <[email protected]>
BT_ISO_CHAN_TYPE_CONNECTED has been refactored into BT_ISO_CHAN_TYPE_CENTRAL and BT_ISO_CHAN_TYPE_PERIPHERAL. Signed-off-by: Timothy Keys <[email protected]>
Signature was changed to have const bt_conn upstream. Signed-off-by: Timothy Keys <[email protected]>
This is needed after changes in upstream zephyr. Signed-off-by: Timothy Keys <[email protected]>
Adjust for new net_linkaddr definition. Signed-off-by: Maximilian Deubel <[email protected]>
Moved OpenThread-related Kconfigs from L2 layer to modules/openthread. All of those configs were not strictly related to the L2 layer, so they fits better to OpenThread module. This operation allows using OpenThread Kconfigs even if L2 layer is disabled. Enabling NET_L2_OPENTHREAD also configures those configs by selecting the OPENTHREAD kconfig, so there is no change regarding backwards compatibility. The only change is that the Kconfigs related to Thread were moved to the modules space, so their location in the menuconfig also changed. Once it is done, a choice for setting different L2 implementations seems to be redundant. Signed-off-by: Arkadiusz Balys <[email protected]> Signed-off-by: Adrian Gielniewski <[email protected]>
Due to a change in the crypto library, the expected JWT signatures have changed. Signed-off-by: Maximilian Deubel <[email protected]>
The signature of bt_conn_get_remote_info changed upstream to use const conn *, but in this usecase conn * should not be const. Signed-off-by: Timothy Keys <[email protected]>
BT_GATT_CCC_INITIALIZER was renamed upstream. It is now called BT_GATT_CCC_MANAGED_USER_DATA_INIT. Signed-off-by: Timothy Keys <[email protected]>
Upstream refactor means it is no longer needed by default. Signed-off-by: Timothy Keys <[email protected]>
CURL and IPERF3 depend on POSIX_THREADS not being selected but POSIX_API selects POSIX_BASE_DEFINITIONS and subsequently POSIX_THREADS, resulting in a dependency conflict. There is no justification provided by the responsible team as to what the exact problem was with PTHREAD_IPC (now POSIX_THREADS) and whatever it still is or is not. Signed-off-by: Johann Fischer <[email protected]>
naming adjustment Signed-off-by: Mateusz Michalek <[email protected]>
The following west manifest projects have changed revision in this Pull Request:
⛔ DNM label due to: 3 projects with PR revision Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:hal_nordic: PR head: 119ff5b5ec7a413ca2f64ae1928c79eee1e7b7b2 more detailshal_nordic:
nrf_hw_models:
sdk-nrf:
mcuboot:
mbedtls:
matter:
hostap:
zephyr:
Github labels
List of changed files detected by CI (12945)
Outputs:ToolchainVersion: 1d2c5d0ab5 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
This option selects the :kconfig:option:`CONFIG_NRF_CPU_LOAD` option. | ||
The :kconfig:option:`CONFIG_NRF_CPU_LOAD` option enables the :ref:`cpu_load` library that is used to perform the measurements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This option selects the :kconfig:option:`CONFIG_NRF_CPU_LOAD` option. | |
The :kconfig:option:`CONFIG_NRF_CPU_LOAD` option enables the :ref:`cpu_load` library that is used to perform the measurements. | |
This option selects the :kconfig:option:`CONFIG_NRF_CPU_LOAD` option that enables the :ref:`cpu_load` library used for performing the measurements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks but that's just a CI test. No need for reviews here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
@@ -107,5 +107,6 @@ CONFIG_BT_BUF_EVT_RX_COUNT=2 | |||
CONFIG_BT_CONN_TX_MAX=3 | |||
CONFIG_BT_L2CAP_TX_BUF_COUNT=2 | |||
CONFIG_BT_ATT_TX_COUNT=2 | |||
CONFIG_BT_BUF_EVT_RX_COUNT=4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where this nr comes from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks but that's just a CI test. No need for reviews here.
@@ -403,7 +403,7 @@ int bt_conn_get_remote_info(struct bt_conn *conn, | |||
|
|||
bt_rpc_encode_bt_conn(&ctx, conn); | |||
|
|||
result.conn = conn; | |||
result.conn = (struct bt_conn *)conn; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
struct bt_conn_get_remote_info_rpc_res
needs to be updated instead
This option selects the :kconfig:option:`CONFIG_NRF_CPU_LOAD` option. | ||
The :kconfig:option:`CONFIG_NRF_CPU_LOAD` option enables the :ref:`cpu_load` library that is used to perform the measurements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
No description provided.