Skip to content
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

tests: drivers: timer: Test drivers.timer.nrf_rtc_timer.stress fails on nrf52 platforms #31822

Closed
PerMac opened this issue Feb 1, 2021 · 3 comments
Assignees
Labels
area: Tests Issues related to a particular existing or missing test bug The issue is a bug, or the PR is fixing a bug platform: nRF Nordic nRFx priority: medium Medium impact/importance bug

Comments

@PerMac
Copy link
Member

PerMac commented Feb 1, 2021

Describe the bug
The test drivers.timer.nrf_rtc_timer.stress from /tests/drivers/timer/nrf_rtc_timer/ fails on nrf52dk_nrf52832 and nrf52840dk_nrf52840.

To Reproduce
Steps to reproduce the behavior:

  1. have nrf52 platform connected
  2. go to zephyr dir
  3. run ./scripts/twister -p nrf52dk_nrf52832 --device-testing --device-serial /dev/ttyACM0 -v -v --inline-logs -T tests/drivers/timer/nrf_rtc_timer
  4. See error

Expected behavior
The test passes
Impact
Not clear

Logs and console output
The script enters test_stress test case then hangs and is terminated by a timeout.

Environment (please complete the following information):

  • OS: Ubuntu 18.04
  • Toolchain ZEphyr SDK
  • Commit SHA or Version used: v2.5.0-rc1-173-g3f1d1f5773
@PerMac PerMac added bug The issue is a bug, or the PR is fixing a bug platform: nRF Nordic nRFx area: Tests Issues related to a particular existing or missing test labels Feb 1, 2021
@ioannisg ioannisg added the priority: medium Medium impact/importance bug label Feb 1, 2021
@pabigot
Copy link
Collaborator

pabigot commented Feb 8, 2021

With my nrf52dk and nrf52840dk I can't reproduce the failures on a recent mainline: three runs on each board all passed. Is this very intermittent?

Also look at #32072 (comment) and try running the clock skew program it references. If LFCLK is slower than HFCLK on the test boards (negative skew) the test may be failing because of that.

@pabigot
Copy link
Collaborator

pabigot commented Feb 8, 2021

I have now reproduced it at the reported commit 3f1d1f5, but have not on current mainline a281d10 after 10 runs on the same board that failed at the reported commit.

Interestingly it's the non-ZLI test variant that failed for me:

tests/drivers/timer/nrf_rtc_timer/drivers.timer.nrf_rtc_timer FAILED Timeout

@PerMac
Copy link
Member Author

PerMac commented Feb 9, 2021

It seems the issue was fixed in the meantime. I saw no fails in recent versions in any of my setups. Closing the issue.

@PerMac PerMac closed this as completed Feb 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Tests Issues related to a particular existing or missing test bug The issue is a bug, or the PR is fixing a bug platform: nRF Nordic nRFx priority: medium Medium impact/importance bug
Projects
None yet
Development

No branches or pull requests

4 participants