BIND 10 #2036: Integrate valgrind into our test suite

[BIND 10 Development]

#2036: Integrate valgrind into our test suite
-------------------------------------+-------------------------------------
                   Reporter:  muks   |                 Owner:  muks
                       Type:         |                Status:  new
  enhancement                        |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |            Resolution:
                  Component:  build  |             Sensitive:  0
  system                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Description changed by muks:

Old description:

> This is a bug to integrate Valgrind into a test suite. Basic objectives
> are:
>
> * Supply `--enable-valgrind` to `configure` to run tests (`make check`)
> under valgrind
> * Use two classes of suppressions files:
>  * `src/valgrind-suppressions` for permanent suppressions that we never
> want to re-consider again
>  * `src/valgrind-suppressions.revisit` for temporary suppressions (such
> as issues in testcases) that are not a priority to fix, but we'd like to
> fix them sometime
>
> We then get a single builder to configure with `--enable-valgrind` and
> mail us in case there are unsuppressed reports.
>
> I am assigning it to myself as I have an implementation ready to go on a
> branch.

New description:

 This is a bug to integrate Valgrind into our test suite. Basic objectives
 are:

 * Supply `--enable-valgrind` to `configure` to run tests (`make check`)
 under valgrind
 * Use two classes of suppressions files:
  * `src/valgrind-suppressions` for permanent suppressions that we never
 want to re-consider again
  * `src/valgrind-suppressions.revisit` for temporary suppressions (such as
 issues in testcases) that are not a priority to fix, but we'd like to fix
 them sometime

 We then get a single builder to configure with `--enable-valgrind` and
 mail us in case there are unsuppressed reports.

 I am assigning it to myself as I have an implementation ready to go on a
 branch.

--

-- 
Ticket URL: <http://bind10.isc.org/ticket/2036#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development