Skip to content

Fix beetle and lpc176x set ticker event in the past #4633

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

Closed
wants to merge 2 commits into from

Conversation

0xc0170
Copy link
Contributor

@0xc0170 0xc0170 commented Jun 26, 2017

Similar to #4632, for more platforms.

As we now have tests for this use case, these 2 are failing. If an event has a timestamp in the past, it either does not produce any callback or just crashes. This PR fixes it.

Will need a rebase once #4628 is being merged (it is included here) to be able to run the test. This was tested on Ach pro, before this patch ,the test would fail, with this patch, passes. Will run CI to get beetle passing.

this is the commit with fixes: f530acf

cc @mmorenobarm @toyowata @c1728p9

0xc0170 and others added 2 commits June 26, 2017 12:56
…past

If the event is in the past, set pending interrupt instead of directly using
timestamp.
Add a test to make sure timer events scheduled for the past fire
immediately, and add a test to ensure many events occurring at
once do not cause a stack overflow.
@0xc0170
Copy link
Contributor Author

0xc0170 commented Jun 27, 2017

This should be replaced by #4644 , I'll reopen if that is not a case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants