Skip to content

(Auto-)Upmerge 20231010 #3785

(Auto-)Upmerge 20231010

(Auto-)Upmerge 20231010 #3785

Triggered via pull request January 9, 2024 16:39
Status Failure
Total duration 15m 33s
Artifacts 1

compliance.yml

on: pull_request
Run compliance checks on patch series (PR)
15m 19s
Run compliance checks on patch series (PR)
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 10 warnings
POINTER_LOCATION: drivers/ipm/ipm_imx.c#L333
drivers/ipm/ipm_imx.c:333 "foo * bar" should be "foo *bar"
E0611: scripts/tests/twister/test_handlers.py#L24
scripts/tests/twister/test_handlers.py:24 No name 'ZEPHYR_BASE' in module 'conftest' (no-name-in-module)
E0611: scripts/tests/twister_blackbox/test_hardwaremap.py#L15
scripts/tests/twister_blackbox/test_hardwaremap.py:15 No name 'ZEPHYR_BASE' in module 'conftest' (no-name-in-module)
E0611: scripts/tests/twister_blackbox/test_hardwaremap.py#L15
scripts/tests/twister_blackbox/test_hardwaremap.py:15 No name 'testsuite_filename_mock' in module 'conftest' (no-name-in-module)
E0611: scripts/tests/twister_blackbox/test_qemu.py#L17
scripts/tests/twister_blackbox/test_qemu.py:17 No name 'TEST_DATA' in module 'conftest' (no-name-in-module)
E0611: scripts/tests/twister_blackbox/test_qemu.py#L17
scripts/tests/twister_blackbox/test_qemu.py:17 No name 'ZEPHYR_BASE' in module 'conftest' (no-name-in-module)
E0611: scripts/tests/twister_blackbox/test_qemu.py#L17
scripts/tests/twister_blackbox/test_qemu.py:17 No name 'testsuite_filename_mock' in module 'conftest' (no-name-in-module)
Run compliance checks on patch series (PR)
Process completed with exit code 4.
Run compliance checks on patch series (PR): Pylint.txt#L1
See https://www.pylint.org/ for more details E0611:No name 'ZEPHYR_BASE' in module 'conftest' (no-name-in-module) File:scripts/tests/twister/test_handlers.py Line:24 Column:0 E0611:No name 'ZEPHYR_BASE' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_hardwaremap.py Line:15 Column:0 E0611:No name 'testsuite_filename_mock' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_hardwaremap.py Line:15 Column:0 E0611:No name 'TEST_DATA' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_qemu.py Line:17 Column:0 E0611:No name 'ZEPHYR_BASE' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_qemu.py Line:17 Column:0 E0611:No name 'testsuite_filename_mock' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_qemu.py Line:17 Column:0 I0021:Useless suppression of 'unused-import' (useless-suppression) File:scripts/west_commands/runners/uf2.py Line:13 Column:0
Run compliance checks on patch series (PR): Gitlint.txt#L1
See https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines for more details Commit 123bcd5af2: 1: UC5 Commit title exceeds max length (81>75): "[nrf fromtree] tests: logging: log_backend_uart: Disable backends other than UART" Commit 7e80b6ded3: 1: UC5 Commit title exceeds max length (82>75): "[nrf fromtree] samples: ipc: multi_endpoint: Fix synchronisation of data receiving" Commit b37336b7a0: 1: UC5 Commit title exceeds max length (85>75): "[nrf fromtree] tests: drivers: flash: Use fixtures for tests requiring external chips" Commit 63c41ca09a: 1: UC5 Commit title exceeds max length (79>75): "[nrf fromtree] tests: drivers: flash: Update nrf52840dk_mx25r_high_perf.overlay" Commit acd17aac06: 1: UC5 Commit title exceeds max length (77>75): "[nrf fromtree] samples/boards/nrf/nrf53_sync_rtc: Reduce sysbuild boilerplate" Commit aa5cd5c78d: 1: UC5 Commit title exceeds max length (78>75): "[nrf fromtree] samples/subsys/logging/multidomain: Reduce sysbuild boilerplate" Commit bbdd614b29: 1: UC5 Commit title exceeds max length (76>75): "[nrf fromtree] tests: bsim: Bluetooth: Enable nrf5340bsim CIS ACL group test" Commit 929e5dc689: 1: UC5 Commit title exceeds max length (85>75): "[nrf fromtree] samples/bluetooth: sysbuild: Add Kconfig setting for HCI IPC inclusion" Commit 63fa5e0907: 1: UC5 Commit title exceeds max length (84>75): "[nrf fromtree] soc: arm: nrf52: Configurable EGU instance for anomaly 109 workaround" Commit 51132518fb: 1: UC5 Commit title exceeds max length (84>75): "[nrf fromtree] sysbuild: introduce Kconfig setting for controlling HCI IPC inclusion" Commit 0359fa9fbf: 1: UC5 Commit title exceeds max length (76>75): "[nrf fromtree] drivers: nrf_qspi_nor: Fix and refactor driver initialization" Commit 6b966bf75a: 1: UC5 Commit title exceeds max length (86>75): "[nrf fromtree] drivers: nrf_qspi_nor: Refactor deactivation and locking access to QSPI" Commit 47ebb40751: 1: UC5 Commit title exceeds max length (80>75): "[nrf fromtree] drivers: nrf_qspi_nor: Prevent reading status before sending RDPD" Commit 112b53114b: 1: UC5 Commit title exceeds max length (77>75): "[nrf fromtree] tfm: Enforce initial attestation with required key provisioned" Commit eb8f598e0a: 1: UC5 Commit title exceeds max length (86>75): "[nrf fromlist] soc: nordic_nrf: Enable the TF-M NS storage partition for nordic boards" Commit 514949df76: 1: UC5 Commit title exceeds max length (87>75): "[nrf fromlist] manifest: hal_nordic: Update revision with fixed workaround in nrfx_qspi" Commit 91e3780914: 1: UC5 Commit title exceeds max length (81>75): "[nrf fromtree] scripts/pylib/twister/twisterlib: Support multiple `--pytest-args`" Commit af9a6edcb3: 1: UC5 Commit title exceeds max length (83>75): "[nrf fromlist] tfm: Remove limitation of enabling FP when build TF-M NS application"
Run compliance checks on patch series (PR): Nits.txt#L1
See https://docs.zephyrproject.org/latest/contribute/guidelines.html#coding-style for more details. Please remove blank lines at end of 'tests/lib/c_lib/common/README.txt'
Run compliance checks on patch series (PR): Checkpatch.txt#L1
See https://docs.zephyrproject.org/latest/contribute/guidelines.html#coding-style for more details. TYPO_SPELLING: 'maping' may be misspelled - perhaps 'mapping'? File:arch/arm/core/cortex_a_r/smp.c Line:80 TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'? File:boards/arm/apollo4p_blue_kxr_evb/doc/index.rst Line:15 LINE_SPACING: Missing a blank line after declarations File:drivers/adc/adc_max11102_17.c Line:324 TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'? File:drivers/can/can_tcan4x5x.c Line:375 TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'? File:drivers/can/can_tcan4x5x.c Line:378 TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'? File:drivers/can/can_tcan4x5x.c Line:378 TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'? File:drivers/can/can_tcan4x5x.c Line:378 TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'? File:drivers/can/can_tcan4x5x.c Line:379 TYPO_SPELLING: 'perfomance' may be misspelled - perhaps 'performance'? File:drivers/crypto/crypto_smartbond.c Line:386 TYPO_SPELLING: 'retrived' may be misspelled - perhaps 'retrieved'? File:drivers/dma/dma_smartbond.c Line:90 TYPO_SPELLING: 'perfomance' may be misspelled - perhaps 'performance'? File:drivers/dma/dma_smartbond.c Line:268 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:468 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:548 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:633 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:695 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:720 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:738 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:761 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:783 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:869 POINTER_LOCATION: "foo * bar" should be "foo *bar" File:drivers/ipm/ipm_imx.c Line:333 TYPO_SPELLING: 'Initilized' may be misspelled - perhaps 'Initialized'? File:drivers/rtc/rtc_am1805.c Line:491 TYPO_SPELLING: 'the the' may be misspelled - perhaps 'the'? File:drivers/serial/uart_intel_lw.c Line:71 TYPO_SPELLING: 'alredy' may be misspelled - perhaps 'already'? File:drivers/timer/cortex_m_systick.c Line:399 TYPO_SPELLING: 'INTERUPT' may be misspelled - perhaps 'INTERRUPT'? File:drivers/watchdog/wdt_xmc4xxx.c Line:37 TYPO_SPELLING: 'peripherial' may be misspelled - perhaps 'peripheral'? File:dts/bindings/dma/andestech,atcdmac300.yaml Line:32 TYPO_SPELLING: 'triggerd' may be misspelled - perhaps 'triggered'? File:dts/bindings/power-domain/power-domain-gpio-monitor.yaml Line:9 TYPO_SPELLING: 'minimim' may be misspelled - perhaps 'minimum'? File:dts/bindings/pwm/nxp,s32-emios-pwm.yaml Line:182 TYPO_SPELLING: 'configuation' may be misspelled - perhaps 'configuration'? File:include/zephyr/net/ieee802154_radio.h Line:1054 FUNCTION_ARGUMENTS: function definition argument 'int' should also have an identifier name File:lib/libc/common/include/threads.h Line:55 MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided File:modules/lvgl/input/lvgl_common_input.c Line:69 TYPO_SPELLING: 'the the' may be misspelled - perhaps 'the'? File:scripts/build/check_init_priorities.py Line:325 TYPO_SPELLING: 'tunning' may be misspelled - perhaps 'tuning'? File:soc/arm/ti_simplelink/cc13x2x7_cc26x2x7/Kconfig.soc Line:73 TYPO_SPELLING: 'wont' may be misspelled - perhaps 'won't'? File:subsys/bluetooth/audio/cap_initiator.c Line:855 TYPO_SPELLING: 'OVERFLW' may be misspelled - perhaps 'OVERFLOW'? File:subsys/canbus/isotp/isotp.c Line:296 TYPO_SPELLING: 'OVERFLW' may be misspelled - perhaps 'OVERFLOW'? File:subsys/canb
Run compliance checks on patch series (PR)
Process completed with exit code 1.
TYPO_SPELLING: arch/arm/core/cortex_a_r/smp.c#L80
arch/arm/core/cortex_a_r/smp.c:80 'maping' may be misspelled - perhaps 'mapping'?
TYPO_SPELLING: boards/arm/apollo4p_blue_kxr_evb/doc/index.rst#L15
boards/arm/apollo4p_blue_kxr_evb/doc/index.rst:15 'upto' may be misspelled - perhaps 'up to'?
LINE_SPACING: drivers/adc/adc_max11102_17.c#L324
drivers/adc/adc_max11102_17.c:324 Missing a blank line after declarations
TYPO_SPELLING: drivers/can/can_tcan4x5x.c#L375
drivers/can/can_tcan4x5x.c:375 'upto' may be misspelled - perhaps 'up to'?
TYPO_SPELLING: drivers/can/can_tcan4x5x.c#L378
drivers/can/can_tcan4x5x.c:378 'upto' may be misspelled - perhaps 'up to'?
TYPO_SPELLING: drivers/can/can_tcan4x5x.c#L378
drivers/can/can_tcan4x5x.c:378 'upto' may be misspelled - perhaps 'up to'?
TYPO_SPELLING: drivers/can/can_tcan4x5x.c#L378
drivers/can/can_tcan4x5x.c:378 'upto' may be misspelled - perhaps 'up to'?
TYPO_SPELLING: drivers/can/can_tcan4x5x.c#L379
drivers/can/can_tcan4x5x.c:379 'upto' may be misspelled - perhaps 'up to'?
TYPO_SPELLING: drivers/crypto/crypto_smartbond.c#L386
drivers/crypto/crypto_smartbond.c:386 'perfomance' may be misspelled - perhaps 'performance'?
TYPO_SPELLING: drivers/dma/dma_smartbond.c#L90
drivers/dma/dma_smartbond.c:90 'retrived' may be misspelled - perhaps 'retrieved'?

Artifacts

Produced during runtime
Name Size
compliance.xml Expired
23.5 KB