feat(ci): valgrind check for memory leaks (DONT UPDATE OR REBASE) #538
Conversation
This file contains 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
This adds a new ci check that runs valgrind on the main geometries, and fails out if non-suppressed errors are found. It also prints out the additions to the suppressions file that would be required if it turns out that the error is a false positive.
github-actions
bot
added
the
topic: infrastructure
wdconinc
changed the title
|
@wdconinc Is this going in for February? |
This is a CI feature. Irrelevant for production and won't go in soon due to not completed. |
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.
Briefly, what does this PR introduce?
This adds a new ci check that runs valgrind on the main geometries, and fails out if non-suppressed errors are found. It also prints out the additions to the suppressions file that would be required if it turns out that the error is a false positive.
This branch is intentionally on a non-updated main so it should be able to fail due to a known memory leak that was since fixed.
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No.
Does this PR change default behavior?
No.