BIND 10 #614: Run unit tests with Valgrind

[BIND 10 Development]

#614: Run unit tests with Valgrind
-------------------------------------+-------------------------------------
                 Reporter:  stephen  |                Owner:  jinmei
                     Type:  task     |               Status:  reviewing
                 Priority:  major    |            Milestone:  A-Team-
                Component:           |  Sprint-20110309
  Unclassified                       |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jinmei
 * status:  assigned => reviewing


Comment:

 Hello

 Replying to [comment:5 jinmei]:
 > - just FYI: valgrind on bind10.isc.org doesn't recognize the
 >   --read-var-info option, so we'll have to specify FLAGS

 I removed that one. I was reading trough the manpage and hoped it will
 give me better output, but it seems it doesn't matter in our case anyway.

 > As for using perl, again, I have no problem with it at least at the
 > moment, also with the understanding that perl is pretty ubiquitously
 > available.  But I'd like to avoid creating a precedent of a chaos
 > where everyone is introducing tool scripts using their favorite
 > language saying "I like ruby/java/haskel/xxx and it just seemed to me
 > using XXX was the best way to do this job".  So, I'd suggest adding
 > a note about the choice of perl, and, unless it's your intent, it's
 > not for opening the possibility of the chaos (or, better than that,
 > we'll eventually rewrite it in our primary script language, python, if
 > it's a plan).

 I added a note. I didn't think of including it in time of writing. Just
 when I did use it, it crossed my mind it would be nice to preserve it, so
 I just put it there (I had the choice of including it or not, rewriting it
 at the time seemed like no gain).

 So, should I merge it now?

 > > May I create tickets for each of these tasks (except the
 AddressSelection)? I would the output as attachment for each of them.
 >
 > I think it's a good idea.

 OK, I'll put them into the relevant backlogs for now and we can promote
 them if they seem important enough.

 Thanks

-- 
Ticket URL: <https://bind10.isc.org/ticket/614#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development