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

twister: Add memory footprint info to json report #34272

Closed
PerMac opened this issue Apr 14, 2021 · 1 comment · Fixed by #34287
Closed

twister: Add memory footprint info to json report #34272

PerMac opened this issue Apr 14, 2021 · 1 comment · Fixed by #34287
Assignees
Labels
Enhancement Changes/Updates/Additions to existing features

Comments

@PerMac
Copy link
Member

PerMac commented Apr 14, 2021

Is your enhancement proposal related to a problem? Please describe.
Our customers decide which platform to use for their needs based on (among other criteria) the table where each available sample is marked if it will fit or not on each board based on the sample's ram/rom usage. Maintaining such table will be easier if this information could be easily posessed with a single run of twister

Describe the solution you'd like
The information about ram/rom usage for each test/sample will be added to the json report from twister call. I think this can be a default option, without the need of extra args (besides --json-report).

Describe alternatives you've considered
There is a west option to show this stats but it requires calling west individually for each sample/test which is inconvenient. Parsing build logs also seems like not the cleanest solution.

Additional context
Such information can also be used for tracing and visualizing the trends of tests/samples sizes for different zephyr's versions

@PerMac PerMac added the Enhancement Changes/Updates/Additions to existing features label Apr 14, 2021
@PerMac
Copy link
Member Author

PerMac commented Apr 14, 2021

It looks like such feature is already implemented (json report can have rom and ram fields) but I cannot make it to work yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants