[test-results] [Bamboo] No agents to build plan Asterisk - Trunk - Ubuntu Lucid (10.04) - amd64

[Bamboo]

-------------------------------------------------------------------------------
ASTTRUNK-LUCID-AMD64-579 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------

http://bamboo.asterisk.org/browse/ASTTRUNK-LUCID-AMD64/log

--------------
Code Changes
--------------
mnicholson (320181):

>Merged revisions 320180 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.8
>
>........
>  r320180 | mnicholson | 2011-05-20 13:48:46 -0500 (Fri, 20 May 2011) | 16 lines
>  
>  This commit modifies the way polling is done on TLS sockets.
>  
>  Because of the buffering the TLS layer does, polling is unreliable. If poll is
>  called while there is data waiting to be read in the TLS layer but not at the
>  network layer, the messaging processing engine will not proceed until something
>  else writes data to the socket, which may not occur. This change modifies the
>  logic around TLS sockets to only poll after a failed read on a non-blocking
>  socket. This way we know that there is no data waiting to be read from the
>  buffering layer.
>  
>  (closes issue #19182)
>  Reported by: st
>  Patches:
>        ssl-poll-fix3.diff uploaded by mnicholson (license 96)
>  Tested by: mnicholson
>........
>

rmudgett (320238):

>Merged revisions 320237 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.8
>
>................
>  r320237 | rmudgett | 2011-05-20 15:49:03 -0500 (Fri, 20 May 2011) | 27 lines
>  
>  Merged revisions 320236 via svnmerge from 
>  https://origsvn.digium.com/svn/asterisk/branches/1.6.2
>  
>  ................
>    r320236 | rmudgett | 2011-05-20 15:44:54 -0500 (Fri, 20 May 2011) | 20 lines
>    
>    Merged revisions 320235 via svnmerge from 
>    https://origsvn.digium.com/svn/asterisk/branches/1.4
>    
>    ........
>      r320235 | rmudgett | 2011-05-20 15:38:22 -0500 (Fri, 20 May 2011) | 13 lines
>      
>      The meetme CLI command completion leaves conferences mutex locked.
>      
>      When issuing a meetme kick CLI command and an invalid (non-existent)
>      conference number is specified, pressing Tab leaves the conferences mutex
>      locked and, therefore, all conferences deadlock.
>      
>      Add missing unlock.
>      
>      (closes issue #19336)
>      Reported by: zvision
>      Patches:
>            app_meetme.diff uploaded by zvision (license 798)
>    ........
>  ................
>................
>


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