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

Implement Subscribe in libtock_unittest::fake::Kernel. #329

Merged
merged 2 commits into from
Sep 13, 2021

Conversation

jrvanwhy
Copy link
Collaborator

@jrvanwhy jrvanwhy commented Sep 4, 2021

Like #326 , this does not have a full unit test suite because it was getting too large. Instead, I'll be adding the unit tests that need additional infrastructure (a fake::Driver) later, and have a TODO to remind myself.

I added some conversions between Register, ErrorCode, and ReturnVariant. I'm not sure what these conversions should look like (some of the code is kind of awkward), so I opened #328 to take another look in the future.

@jrvanwhy jrvanwhy added the significant Indicates a PR is significant as defined by the code review policy. label Sep 5, 2021
@jrvanwhy jrvanwhy mentioned this pull request Sep 5, 2021
18 tasks
bors bot added a commit that referenced this pull request Sep 11, 2021
330: `libtock_unittest`: make Yield invoke queued upcalls. r=jrvanwhy a=jrvanwhy

With this PR, calling the Yield system calls will correctly invoke queued upcalls. This PR and #329 implement the fake Subscribe implementation in `libtock_unittest`.

331: Implement a fake LowLevelDebug API. r=jrvanwhy a=jrvanwhy

This is the first proper `fake::Driver` implementation!

Co-authored-by: Johnathan Van Why <[email protected]>
@jrvanwhy
Copy link
Collaborator Author

bors r+

@bors
Copy link
Contributor

bors bot commented Sep 13, 2021

Build succeeded:

@bors bors bot merged commit f680396 into tock:master Sep 13, 2021
@jrvanwhy jrvanwhy deleted the unittest-subscribe branch February 5, 2022 01:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
significant Indicates a PR is significant as defined by the code review policy.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants