Open
Conversation
|
Can one of the admins verify this patch? |
d34d5a1 to
18b2bb3
Compare
Contributor
|
Okay to test. We are in contact with contributor. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
MemBrowse memory footprint tracking in CI (Following a discussion with wolfSSL team)
I've configured four targets in membrowse-targets.json, all on Cortex-M4 with minimal test code linked so it doesn't affect the memory tracking:
It includes:
To get started:
The workflows will handle the rest.
Full docs are available at docs.membrowse.com.
Happy to help if any questions come up during integration.