-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Timing tests are unstable on NRF51_DK #4612
Comments
It might be linked to #4108 but I cannot reproduce the issue locally. |
I got NRF51 DK working, and can reproduce the problem. Every second time (first run is OK) I run the rtos basic test , I get this
I've been testing this with #4599 that should improve timer testing. Update: Seems it is random anyway, got 2x OK, then Error with stack underflow |
I looked at a similar problem with @studavekar and we found the cause to be a stack overflow because the 768 byte stack in the basic rtos test was too small. It intermittently failed in development builds because the stack would only overflow if an interrupt pushed more registers onto the thread stack at the right time. Rebuilding as debug caused the overflow to occur always since it used more stack space. @studavekar is updating the stack size in #4599 so this should fix the underflow in tests-mbedmicro-rtos-mbed-basic. Also of note, the above stack overflow was not nrf51 specific, and has been occurring on other platforms. |
@xc0170, @c1728p9 Is this issue is still valid? |
I believe this was resolved earlier with updating ticker tests at the host side plus above the stack overflow. |
Description
Bug
Target
NRF51_DK
Toolchain:
any
meed-os sha:
latest master
The test that is failing tests-mbedmicro-rtos-mbed-basic , it fails randomly, so might be harder to reproduce.
This is one #4601 (comment) and another one #4599 (comment)
different compilers, same issue. The result from the log
Test timeouts. There are some reports for nrf51 dk and its timers, are they relevant?
cc @nvlsianpu @anangl @pan- @c1728p9
The text was updated successfully, but these errors were encountered: