← Back to context Comment by throw-qqqqq 4 days ago I do this too, but valgrind is slow! In my experience, the runtime increases a factor of 10/20/30x .. 2 comments throw-qqqqq Reply rwmj 4 days ago Yes, it's definitely slow. That's why we have an option to run the same tests normally or with valgrind, and mainly use valgrind runs in our CI system after changes have been committed. thefaux 4 days ago I can't help but notice the subtle ways in which git has corrupted our understanding of the word commit.
rwmj 4 days ago Yes, it's definitely slow. That's why we have an option to run the same tests normally or with valgrind, and mainly use valgrind runs in our CI system after changes have been committed. thefaux 4 days ago I can't help but notice the subtle ways in which git has corrupted our understanding of the word commit.
thefaux 4 days ago I can't help but notice the subtle ways in which git has corrupted our understanding of the word commit.
Yes, it's definitely slow. That's why we have an option to run the same tests normally or with valgrind, and mainly use valgrind runs in our CI system after changes have been committed.
I can't help but notice the subtle ways in which git has corrupted our understanding of the word commit.