[test-results] [Bamboo] Asterisk - Trunk > Mac OS X Snow Leopard (10.6) > #321 has FAILED. Change made by 8 authors.

[Bamboo]

-----------------------------------------------------------------------
Asterisk - Trunk > Mac OS X Snow Leopard (10.6) > #321 failed.
-----------------------------------------------------------------------
This build occurred because it is a dependant of ASTTRUNK-LUCID-841.
No failed tests found, a possible compilation error.

http://bamboo.asterisk.org/browse/ASTTRUNK-SNOWLEOPARD-321/


--------------
Failing Jobs
--------------
  - x86_64 (Default Stage): No tests found.


--------------
Code Changes
--------------
dvossel (331869):

>Merged revisions 331868 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/10
>
>................
>  r331868 | dvossel | 2011-08-15 10:14:13 -0500 (Mon, 15 Aug 2011) | 12 lines
>  
>  Merged revisions 331867 via svnmerge from 
>  https://origsvn.digium.com/svn/asterisk/branches/1.8
>  
>  ........
>    r331867 | dvossel | 2011-08-15 10:12:16 -0500 (Mon, 15 Aug 2011) | 6 lines
>    
>    Fixes locking inversion issues present in the handling of the sip REFER method.
>    
>    (closes issue ASTERISK-18082)
>    Reported by: James Van Vleet
>  ........
>................
>

rmudgett (331716):

>Merged revisions 331715 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/10
>
>................
>  r331715 | rmudgett | 2011-08-12 12:54:47 -0500 (Fri, 12 Aug 2011) | 29 lines
>  
>  Merged revisions 331714 via svnmerge from 
>  https://origsvn.digium.com/svn/asterisk/branches/1.8
>  
>  ........
>    r331714 | rmudgett | 2011-08-12 12:47:57 -0500 (Fri, 12 Aug 2011) | 22 lines
>    
>    AMI actions DAHDIHangup and DAHDITransfer have no effect.
>    
>    The AMI actions DAHDIHangup and DAHDITransfer have no effect on a DAHDI
>    channel.  These two AMI actions are highly specialized to analog channels
>    and appear to make the channel behave like a jack port for headsets.
>    
>    * Made the faked DAHDI event get processed before a normal media stream
>    read in dahdi_read() instead of trying to trigger an exception read by
>    setting the AST_FLAG_EXCEPTION flag.  Apparently a change was made long
>    ago that changed how AST_FLAG_EXCEPTION is processed in the core.
>    Unfortunately, the faked DAHDI events no longer worked when that happened.
>    
>    * Updated the DAHDI AMI action documentation for the following actions:
>    DAHDITransfer, DAHDIHangup, DAHDIDialOffhook, DAHDIDNDon, DAHDIDNDoff,
>    DAHDIShowChannels, and DAHDIRestart.
>    
>    * Made use sscanf() instead of atoi() for better error checking of the
>    DAHDIChannel header string.
>    
>    JIRA AST-620
>    JIRA SWP-3616
>  ........
>................
>

rmudgett (331957):

>Merged revisions 331956 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/10
>
>................
>  r331956 | rmudgett | 2011-08-15 12:35:03 -0500 (Mon, 15 Aug 2011) | 20 lines
>  
>  Merged revisions 331955 via svnmerge from 
>  https://origsvn.digium.com/svn/asterisk/branches/1.8
>  
>  ........
>    r331955 | rmudgett | 2011-08-15 12:24:08 -0500 (Mon, 15 Aug 2011) | 13 lines
>    
>    Fix some minor chan_dahdi config load issues.
>    
>    * Address chan_dahdi.conf dahdichan option todo item about needing line
>    number.
>    
>    * Make ignore_failed_channels option also apply to dahdichan option.
>    
>    * Don't attempt to create a default pseudo channel if the chan_dahdi.conf
>    channel/channels option is not allowed.
>    
>    * Add a similar check for dahdichan in normal chan_dahdi.conf sections as
>    is done in users.conf.
>  ........
>................
>


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