[test-results] [Bamboo] No agents to build plan Asterisk Testing - Asterisk 1.8 Branch - Asterisk 1.8 CentOS 6 64-Bit

[Bamboo]

-------------------------------------------------------------------------------
TESTING-ASTERISK18BRANCH-AST18CENTOS64-430 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------

http://bamboo.asterisk.org/browse/TESTING-ASTERISK18BRANCH-AST18CENTOS64/log

--------------
Code Changes
--------------
mjordan (374843):

>Fix incorrect billing duration reported when batch mode is enabled
>
>Similar to r369351, the billing duration can be skewed when batch mode is
>enabled.  This happened much more rarely than the duration, as it only
>occured when the call was answered (thereby indicating an actual answer
>time) and immediately hung up on (indicating a billsec of 0).  Since
>a billing time of '0' can either mean that the call immediately ended
>or that the CDR was improperly answered, we have to use additional information
>to know whether or not we can trust the CDR billsec value.  Prior to this
>patch, we looked to see if we had a valid answer time.  If we did, and
>billsec was zero, we used the current time to calculate what billsec value
>we could from the CDR being written.  If batch mode is enabled, this will
>incorrectly report a billsec value being much greater than the actual
>duration of the call.
>
>Instead of relying on the presence of an answer time to know whether or not
>we can re-calculate the billsec for the CDR, we now also use the presence
>of the CDR's end time to know if we need to re-calculate or whether we can
>trust the billsec value that we have.  This prevents erroneous jumps in the
>billsec value, while still making sure that in the worst case, some billing
>time will be calculated.
>
>(closes issue AST-1016)
>Reported by: Thomas Arimont
>Tested by: Thomas Arimont
>
>


--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20121011/ccc27139/attachment-0001.htm>