On Wed, Oct 25, 2017 at 12:50 PM, James E. King, III via Boost <boost@lists.boost.org> wrote:
If however the original author sets up a robust CI environment with code coverage metrics, the CMT would be able to understand what expectations for quality submissions are at a minimum. This can be further improved with ... -fsanitize type builds and valgrind-type builds.
Beast has code coverage: <https://codecov.io/gh/boostorg/beast/branch/master> And per-commit sanitizer builds on CI: <https://travis-ci.org/vinniefalco/beast/jobs/292759959#L2812> And per-commit valgrind builds on CI: <https://travis-ci.org/vinniefalco/beast/jobs/292759958#L1399> On Travis the tests are run with gdb so in the event of a failure a stacktrace is generated. Thanks