25 Oct
2017
25 Oct
'17
9:02 p.m.
AMDG On 10/25/2017 02:42 PM, James E. King, III via Boost wrote:
On Wed, Oct 25, 2017 at 4:36 PM, Vinnie Falco via Boost < boost@lists.boost.org> wrote:
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.
Nice! It would be neat to have valgrind as a standard bjam build option, as a test wrapper.
There's a generic option for this: b2 testing.launcher=valgrind
I haven't used codecov.io yet, but I would like to. I tried to use coveralls but it didn't generate any coverage for header-only libraries?
In Christ, Steven Watanabe