-
Notifications
You must be signed in to change notification settings - Fork 2k
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
misc issues with tests/trickle #9052
Comments
Thank for investigating this, I also had problem on |
Having `prev_now` initialized to 0 breaks tests on `arduino-zero` and `arduino-mega2560` as `xtimer_now_usec` is way bigger (72k on `arduino-zero`). Issue found in: * RIOT-OS#9052 and proposed fix by ZetaR60 * RIOT-OS/Release-Specs#62 (comment)
Having `prev_now` initialized to 0 breaks tests on `arduino-zero` and `arduino-mega2560` as `xtimer_now_usec` is way bigger (72k on `arduino-zero`). Issue found in: * RIOT-OS#9052 and proposed fix by ZetaR60 * RIOT-OS/Release-Specs#62 (comment)
I implemented your However I misread and thought it also fixed your problem, I can amend my commit message depending on your feedback. |
@cladmi I found that |
Having `prev_now` initialized to 0 breaks tests on `arduino-zero` and `arduino-mega2560` as `xtimer_now_usec` is way bigger (72k on `arduino-zero`). Issue found in: * RIOT-OS#9052 and proposed fix by ZetaR60 * RIOT-OS/Release-Specs#62 (comment)
@ZetaR60 I am not seeing any hang on |
@cladmi Below is what I get on mega-xplained. Could you post the output you are getting as well?
|
I am running from my branch to run on IoT-LAB:
Toolchain
|
The test correctly runs if I increase |
Not that those have anything to do with each other -_- |
Having `prev_now` initialized to 0 breaks tests on `arduino-zero` and `arduino-mega2560` as `xtimer_now_usec` is way bigger (72k on `arduino-zero`). Issue found in: * RIOT-OS#9052 and proposed fix by ZetaR60 * RIOT-OS/Release-Specs#62 (comment)
Note from the release tests, it is also broken on
|
Description
While running tests/trickle for #8904 on mega-xplained, I have run into a number of different issues. One issue is that prev_now is not being initialized properly in main (it assumes xtimer_now_usec is zero when main starts, which is not the case). This is easily fixed by adding
prev_now = xtimer_now_usec();
to the beginning of main. There are also a number of problems where it hangs at various points.Steps to reproduce the issue
Run tests/trickle with the following variations:
prev_now = xtimer_now_usec();
prev_now = xtimer_now_usec();
Expected results
tests/trickle runs, printing 5 messages after
[START]
, and then 7 messages after[TRICKLE_RESET]
, and then prints[SUCCESS]
.Actual results
[TRICKLE_RESET]
[TRICKLE_RESET]
Versions
Board: mega-xplained
The text was updated successfully, but these errors were encountered: