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

Adding Valgrind Issues reporting #1909

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

panicking
Copy link
Contributor

@panicking panicking commented Dec 15, 2024

Allow to use valgrindParser to report memory issues

The analytic-model already has the valgrind model. Just extend the plugin to use it.

recordIssues sourceCodeRetention: 'LAST_BUILD',
tool: Valgrind(pattern: "out/test/memcheck.xml"),
qualityGates: [[threshold: 1, type: 'TOTAL', criticality: 'FAILURE']]

Testing done

Deploy locally on latest jenkins instance version 2.489

@panicking
Copy link
Contributor Author

Screenshot from 2024-12-15 18-38-51
Screenshot from 2024-12-15 18-38-36

@uhafner uhafner added the enhancement Enhancement of existing functionality label Dec 21, 2024
}

/** Descriptor for this static analysis tool. */
@Symbol("valgrindParser")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is valgrind already used somewhere else?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@uhafner I don't think is used at all. I add it because we are using in memory detection leak in iot devices.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I wasn't clear about this: wouldn't it be simpler to use the ID valgrind rather than valgrindParser?

Copy link
Contributor Author

@panicking panicking Dec 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@uhafner I will repost with all your suggestions. Clean up and make a better commit. Including how use it and use cases

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@uhafner Done

@panicking panicking force-pushed the feature/add-valgrind-parser branch 3 times, most recently from 1c1e67e to c919254 Compare December 25, 2024 17:50
Allow to use valgrindParser to report memory issues
The analytic-model already has the valgrind model. Just extend the plugin to use it.

recordIssues sourceCodeRetention: 'LAST_BUILD',
tool: valgrind(pattern: "out/test/memcheck.xml"),
qualityGates: [[threshold: 1, type: 'TOTAL', criticality: 'FAILURE']]

Add Fix copy paste error in JavaDoc from Ullrich Hafner

Reviewed-by: Ullrich Hafner <[email protected]>
Signed-off-by: Michael Trimarchi <[email protected]>
@panicking panicking force-pushed the feature/add-valgrind-parser branch from 6d3e5c1 to 23a8658 Compare December 27, 2024 17:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement of existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants