-
Notifications
You must be signed in to change notification settings - Fork 7.3k
tests: drivers: gpio: gpio_basic_api: drivers.gpio.2pin fails on [email protected]/nrf54h20/cpuapp and cpuard #88293
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
Comments
Guessing that happens after bea0a06 |
Fails the same at nrf54l15dk/nrf54l15/cpuapp |
Additionally, similar failure at nrf52840dk/nrf52840 for:
and
|
Issues occurs on
what is status of this issue? |
2 more instances blocking #89370: https://github.com/zephyrproject-rtos/zephyr/actions/runs/14856947600/job/41712752094?pr=89370
https://github.com/zephyrproject-rtos/zephyr/actions/runs/14856947600/job/41712751562?pr=89370
Could the priority of the issue be increased to high? |
Disable `tests/drivers/gpio/gpio_hogs -T drivers.gpio.hogs` for nrf bsim board to unblock PR. The test can be enabled as part of fix for issue zephyrproject-rtos#88293. Signed-off-by: Sudan Landge <[email protected]>
I will work on it now :) |
tests/drivers/gpio/gpio_hogs failure bisected to bea0a06 |
Hi @bjarki-andreasen , thank you for looking into this. I tried #89595 and still see the gpio hogs issue with bsim. Could you please confirm if the commands mentioned here #88293 (comment) ran successfully for you? |
At least to me the whole |
Must be something wrong with my workspace then, thanks for confirming though. |
Describe the bug
Tests
Observed for
[email protected]/nrf54h20/cpuapp
and[email protected]/nrf54h20/cpurad
.To Reproduce
Steps to reproduce the behavior:
./scripts/twister -T tests/drivers/gpio/gpio_basic_api -p [email protected]/nrf54h20/cpuapp --device-testing --device-serial /dev/ttyACM0 -v --inline-logs --west-flash="--erase"
Expected behavior
Valid console output
Impact
Not clear
Logs and console output
Environment (please complete the following information):
v4.1.0-2034-g8f2f97ce320a
The text was updated successfully, but these errors were encountered: