[test-results] [Bamboo] No agents to build plan Asterisk - 1.8 - CentOS 5.5 - i386

Bamboo bamboo at asterisk.org
Fri Jan 14 12:02:53 CST 2011


-------------------------------------------------------------------------------
AST18-CENTOS55-I386-103 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------

http://bamboo.asterisk.org/browse/AST18-CENTOS55-I386/log

--------------
Code Changes
--------------
lmadsen (301731):

>Merged revisions 301730 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.6.2
>
>........
>  r301730 | lmadsen | 2011-01-13 11:01:11 -0600 (Thu, 13 Jan 2011) | 7 lines
>  
>  Add static entry for split Polycom 332 firmware.
>  
>  (closes issue #18607)
>  Reported by: cjacobsen
>  Patches: 
>        polycom_331.diff uploaded by cjacobsen (license 1029)
>  Tested by: lathama
>........
>

jpeeler (301790):

>Resolve deadlock involving REFER.
>
>Two fixes:
>1) One must always have the private unlocked before calling
>pbx_builtin_setvar_helper to not invalidate locking order since it locks the
>channel.
>2) Unlock the channel before calling pbx_find_extension, which starts and stops
>autoservice during the lookup. The problem scenario as illustrated by the
>reporter:
>
>Thread: do_monitor
>-----------------------
>handle_request_do
> handle_incoming
>  handle_request_refer
>   ast_parking_ext_valid
>    pbx_find_extension
>     ast_autoservice_stop
>      while (chan_list_state == as_chan_list_state) { usleep(1000); }
>
>Thread: autoservice_run
>-----------------------
>autoservice_run
> chan = ast_waitfor_n
>  ast_waitfor_nandfds
>   ast_waitfor_nandfds_classic / simple / complex (depending on your system)
>    ast_channel_lock(c[x]);
>
>handle_request_do and schedule_process_request_queue locks the owner
>if it exists. The autoservice thread is waiting for the channel lock, which
>wasn't ever released since the do_monitor thread was waiting for autoservice
>operations to complete. Solved by unlocking the channel but keeping a reference
>to guarantee safety.
>
>(closes issue #18403)
>Reported by: jthurman
>Patches: 
>      20110103-blind_deadlock.diff uploaded by jthurman (license 614)
>      issue18403.patch uploaded by jpeeler (license 325)
>Tested by: jthurman
>
>


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


More information about the Test-results mailing list