[test-results] [Bamboo] No agents to build plan Asterisk - Trunk - FreeBSD 8.1 - i386

[Bamboo]

-------------------------------------------------------------------------------
ASTTRUNK-FREEBSD81-I386-210 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------

http://bamboo.asterisk.org/browse/ASTTRUNK-FREEBSD81-I386/log

--------------
Code Changes
--------------
dvossel (314078):

>Merged revisions 314067 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.8
>
>........
>  r314067 | dvossel | 2011-04-18 10:23:45 -0500 (Mon, 18 Apr 2011) | 22 lines
>  
>  Remove the need for deadlock avoidance in chan_sip do_monitor.
>  
>  Deadlock avoidance between the sip pvt and the pvt->owner is
>  very difficult.  Now that channel's are ao2 objects, this complication
>  is no longer necessary.  It turns out the pvt's msg queue only
>  exists because of deadlock avoidance (when deadlock avoidance fails
>  msgs were added to a queue to be processed later), so this goes away as well.
>  
>  The technique used in the new sip_lock_pvt_full() function should
>  be used as a template for replacing all locations where deadlock
>  avoidance occurs between a channel tech_pvt and the pvt's owner.
>  My hope is that this will begin a reversal of the invalid channel
>  driver locking architecture we have been using for so long. 
>  
>  This patch also resolves an issue where the pvt->owner gets
>  unlocked during processing the msg queue.
>  
>  (closes issue #18690)
>  Reported by: dvossel
>  
>  Review: https://reviewboard.asterisk.org/r/1182/
>........
>

rmudgett (314079):

>Merged revisions 314068 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.8
>
>........
>  r314068 | rmudgett | 2011-04-18 11:02:12 -0500 (Mon, 18 Apr 2011) | 7 lines
>  
>  Unclear code in app_dial.c.
>  
>  Make code formatting clear.
>  
>  (closes issue #19134)
>  Reported by: oej
>........
>

rmudgett (314080):

>Merged revisions 314069 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.8
>
>........
>  r314069 | rmudgett | 2011-04-18 11:10:10 -0500 (Mon, 18 Apr 2011) | 22 lines
>  
>  The AsyncAGI command loop is lax in the value it returns for the return status.
>  
>  * Return correct status: SUCCESS/FAILED/HANGUP.  Previously, abnormal
>  exits from the command loop such as hangup would return SUCCESS.
>  
>  * The "asyncagi break" command now returns SUCCESS and is now the only way
>  to break the command loop with that status.  Previously, it returned
>  FAILED.
>  
>  * The AMI event AsyncAGI End is no longer sent if the AsyncAGI Start event
>  is not sent.  Previously, this happened because of an error setting up the
>  AGI pipes.
>  
>  * All executed AGI commands now get an AsyncAGI Exec result event.
>  Previously, if the command returned failure (because of hangup), the
>  command loop just exited with FAILURE and did not send the AsyncAGI Exec
>  result event.
>  
>  * Makes sure that the channel frame queue is empty on hangup.
>  
>  Review: https://reviewboard.asterisk.org/r/1183/
>........
>


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