Comment 1 for bug 1185221

It may be that we *also* want to run a broader set of tests with valgrind (since running everything that way on the RQ would make it take hours). In that case, we should IMHO do this nightly or weekly, rather than at the end of the release cycle, and any reports brought up by such testing should be fixed with highest priority. However, for this to be useful, we also would need some kind of baseline valgrind report that we deem acceptable, and only report regressions.