re-enabled valgrind in CI#4516
Merged
danmar merged 2 commits intocppcheck-opensource:mainfrom Sep 29, 2022
Merged
Conversation
firewave
changed the title
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
2 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.
The valgrind workflow no longer experiences the package installation issues.
ASAN should have never been disabled. It being killed actually indicates excessive memory/CPU usage (this is what we experience as
-9crashes in daca).Edit: Turns out ASAN is way too slow to be enabled. It actually got much slower. It was once at around 20 minutes and the last time I checked it was 40 minutes but now we broke the one hour barrier. (I think we introduced another 10% Ir regression recently).