diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2016-05-09 13:59:36 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2016-05-09 14:09:56 -0700 |
| commit | 3cc643bea2cb5f42244b158e5f268a38b7153f11 (patch) | |
| tree | 2bef31c4df241d95cbc851a9657bdd086a74357b /036refcount.cc | |
| parent | 2a94896bb9ebc5042afb739fe94ffcc05705a137 (diff) | |
| download | mu-3cc643bea2cb5f42244b158e5f268a38b7153f11.tar.gz | |
2949 - disable Valgrind on app layer tests
I kept suspecting Valgrind and kept finding that Valgrind wasn't actually slowing down Travis CI, but I'd been running it like this: valgrind ./mu test edit Which wasn't actually running the underlying ./mu_bin binary atop Valgrind. Ok, so Mu is just super slow running any non-trivial apps atop Valgrind. That's ok, we've rarely needed an app to flush out memory leaks in Mu.
Diffstat (limited to '036refcount.cc')
0 files changed, 0 insertions, 0 deletions