-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Closed
Labels
area: CANbugThe issue is a bug, or the PR is fixing a bugThe issue is a bug, or the PR is fixing a bugpriority: mediumMedium impact/importance bugMedium impact/importance bug
Milestone
Description
Trying to run the can tests:
./scripts/sanitycheck -T tests/drivers/can/ -l
We get:
4 tests selected, 314 tests discarded due to filters
total complete: 0/ 4 0% failed: 0
stm32f072b_disco tests/drivers/can/api/peripheral.can FAILED: build_error
see: sanity-out/stm32f072b_disco/tests/drivers/can/api/peripheral.can/build.log
total complete: 1/ 4 25% failed: 1
stm32f072b_disco tests/drivers/can/stm32/peripheral.can FAILED: build_error
see: sanity-out/stm32f072b_disco/tests/drivers/can/stm32/peripheral.can/build.log
total complete: 2/ 4 50% failed: 2
nucleo_l432kc tests/drivers/can/api/peripheral.can FAILED: build_error
see: sanity-out/nucleo_l432kc/tests/drivers/can/api/peripheral.can/build.log
total complete: 3/ 4 75% failed: 3
nucleo_l432kc tests/drivers/can/stm32/peripheral.can FAILED: build_error
see: sanity-out/nucleo_l432kc/tests/drivers/can/stm32/peripheral.can/build.log
total complete: 4/ 4 100% failed: 4
0 of 4 tests passed with 0 warnings in 3 seconds
There are 2 different issues here, one is the tests didn't get updated with change in PR #13374. Second is enabling of the STM32 CAN driver.
The second issue is addressed by PR #13715
Metadata
Metadata
Assignees
Labels
area: CANbugThe issue is a bug, or the PR is fixing a bugThe issue is a bug, or the PR is fixing a bugpriority: mediumMedium impact/importance bugMedium impact/importance bug