Check valgrind log files #1173
Merged
Check valgrind log files #1173
Conversation
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
Check valgrind log files. Do not print an error message like: ls: cannot access './examples/umf_example_*.log': No such file or directory when only the tests log files are present for example. Signed-off-by: Lukasz Dorau <[email protected]>
ldorau
force-pushed
the
Check_valgrind_log_files
branch
from
f7d4063 to
6483c54
Compare
lukaszstolarczuk
approved these changes
Mar 10, 2025
KFilipek
approved these changes
Mar 10, 2025
Contributor
KFilipek
left a comment
KFilipek
left a comment
There was a problem hiding this comment.
I hate bash files, approve.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Check valgrind log files. Do not print an error message like:
when only the tests log files are present for example.
Checklist