-
Notifications
You must be signed in to change notification settings - Fork 1
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
Memory report ci #32
Memory report ci #32
Conversation
🤖 Pull request artifactsempty string
|
Memory usage reportHere is an overview of how your pull request impacts the memory usage compared to the main branch:
|
Thanks for addressing this. Will be a very useful feature! However, now the artefacts are committed directly to the main branch of the repo. |
Add used data
Test add static data
I think it's ready for review now! See the description on the PR for why the CI job is failing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! I think this is going to be very useful! In the future I want to do the report based on compilation targeting our embedded platforms.
This PR adds a workflow that comments a PR with the change in memory usage for all the C tests. An example of how it will look can be seen here: #56. From the results of the memory report, it is clear the .bss memory region has been massively increased.
It compares the memory usage of the target branch with the head branch to calculate an increase percentage. In doing so it checks out the target branch and runs an action there. Because of this, the CI fails for this PR because the main branch does have the memory-report action yet. But because it works on #56 I expect it will work if we merge this to main as well.