On Fri, 2016-02-26 at 13:15 -0500, Andrew Stitcher wrote: > > I say we add suppressions for these issues as tightly as we can and > just wash our hands! > > The travis failures are becoming a drag.
I see no way to write reasonable suppressions, the sasl and crypto libs have no debug info so we'd have to supress everything under sasl_server_new and sasl_server_step, which is effectively no valgrind for server-side use of SASL. Can we just turn valgrind off in travis.yml? That will give us useful result from travis on compilability etc. and we can do un-supressed valgrind checking on our own builds. Cheers, Alan. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
