BIND 10 #1175: find another solution to synchronize between threads used in unittests for stats

BIND 10 Development do-not-reply at isc.org
Fri Sep 16 05:43:09 UTC 2011


#1175: find another solution to synchronize between threads used in unittests for
stats
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  naokikambe                         |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20110927
                   Priority:  major  |            Resolution:
                  Component:         |             Sensitive:  0
  statistics                         |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  5
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by naokikambe):

 * owner:  jreed => UnAssigned
 * status:  assigned => reviewing


Comment:

 Replying to [comment:2:trac:1243 jinmei]:
 > Works for me, but I'm afraid that may mean the branch for #1175 is too
 > big to review (as was often the case for statistics-related tasks).
 > If that is possibly the case, please consider separating it into two
 > sub tasks.

 The trac1175 branch mainly consists of changes of two parts. First one was
 added on #930. Its reviewing is already done and was merged with the
 master once, but after that its test failed on the buildbot. So it was
 reverted from the master. (This reversion is git
 5de7909a21a077238567b64e489ed5345824b2a0.)
 Second one was added on #1175. Coding is done but reviewing is not done
 yet. However its test succeeds on the buidbot (That was tested on #1192).
 I think it is now ready for reviewing.
 So should we split the second one into two sub tasks? And do we need to
 edit again the committed changes of the second part? If it is yes, I try
 to create new tickets for it.

 Best

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


More information about the bind10-tickets mailing list