gmentci: add PR stack usage report via puncover#689
Closed
simensrostad wants to merge 0 commit into
Closed
Conversation
Contributor
|
App size did not change. See CI run |
Contributor
|
Stack margin report failed. See CI run for logs. |
dd1b3f5 to
bb475a0
Compare
bb475a0 to
9c97c89
Compare
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.
Add scripts and a CI workflow step that compare static stack usage between a PR and its merge base. On each PR, the workflow rebuilds with
CONFIG_STACK_USAGE=y, runs puncover viastack_threads.py, and posts a sticky comment with a per-thread table showing configured size, max static depth, delta vs base, and remaining margin.Thread entry points are discovered from
K_THREAD_DEFINEin app sources; Zephyr/NCS subsystem stacks are resolved viargin the west tree with a small fallback map. Work queues list configured size only since puncover can't attribute depth per queue.