[test-results] [Bamboo] Asterisk - Team Branches > Bridge Construction > #433 has FAILED (1 tests failed, no failures were new). Change made by root.

[Bamboo]

-----------------------------------------------------------------------
Asterisk - Team Branches > Bridge Construction > #433 failed.
-----------------------------------------------------------------------
Code has been updated by root.
1/2 jobs failed, with 1 failing test, no failures were new.

http://bamboo.asterisk.org/browse/ASTTEAM-BRIDGECONSTRUCTION-433/


--------------
Failing Jobs
--------------
  - Asterisk 1.8 CentOS 6 32-Bit (CentOS 6): 1 of 323 tests failed.



--------------
Code Changes
--------------
root (392009):

>Multiple revisions 392004-392005
>
>........
>  r392004 | mjordan | 2013-06-17 09:31:51 -0500 (Mon, 17 Jun 2013) | 5 lines
>  
>  Restore bad merge on CHANGES
>  
>  The patch for CDRs moved around a lot of content in CHANGES to try and
>  organize the areas that were affected. This missed some changes that went
>  in with a merge and removed some updates - this patch adds them back in.
>........
>  r392005 | mjordan | 2013-06-17 09:40:23 -0500 (Mon, 17 Jun 2013) | 20 lines
>  
>  Prevent sending a NewExten event after a Hangup during a stack restore
>  
>  When a channel is originated, its application is typically set to AppDial2,
>  indicating that it was a dialed channel through the Dial API. Asterisk during
>  an originate will perform a stack execute to direct the outgoing channel to
>  a particular place in the dialplan or application. When the stack returns, the
>  previous application (AppDial2) is restored.
>  
>  Unfortunately, in the case of an originated channel, the stack restore happens
>  after hangup. A stasis message is sent notifying everyone that the application
>  was restored, and this causes a NewExten event to go out after the Hangup event,
>  violating the basic contract consumers have of the channel lifetime. While we
>  could preclude the message from going out, restoring the channel's state before
>  it executed the next higher frame in the stack has to occur, and other places
>  in the code depend on this behavior.
>  
>  Since we know that channel hung up (it's a ZOMBIE!), this patch simply checks
>  to see if the channel has been zombified before sending a NewExten event.
>  
>  Note that this will fix a number of bouncing tests in the Test Suite. Go tests.
>........
>
>Merged revisions 392004-392005 from file:///srv/subversion/repos/asterisk/trunk
>



--------------
Tests
--------------
Existing Test Failures (1)
   - AsteriskUnitTests: /main/pbx/test substitution

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