[test-results] [Bamboo] Asterisk > Asterisk Unit Tests > #826 has FAILED (4 tests failed, no failures were new). Change made by Matt Jordan and Richard Mudgett.

Bamboo noreply at bamboo.asterisk.org
Mon Nov 24 23:35:12 CST 2014


-----------------------------------------------------------------------
Asterisk > Asterisk Unit Tests > #826 failed.
-----------------------------------------------------------------------
This build occurred because it is a dependant of AST-ATRUNKFULLBUILD-855.
2/2 jobs failed, with 4 failing tests, no failures were new.

https://bamboo.asterisk.org/bamboo/browse/AST-ATRUNKUNIT-826/

---------------------
Currently Responsible
---------------------

Corey Farrell (Automatically assigned)
John Bigelow (Automatically assigned)
Richard Mudgett (Automatically assigned)



--------------
Failing Jobs
--------------
  - CentOS 6 32-Bit Unit Testing (Unit Testing): 2 of 458 tests failed.
  - CentOS 6 64-Bit Unit Testing (Unit Testing): 2 of 458 tests failed.



--------------
Code Changes
--------------
Richard Mudgett (428603):

>DTMF hooks: Leaving channels need to push any collected digits into the bridge.
>
>Any partially collected DTMF digits for a DTMF hook need to be pushed into
>the bridge when a channel leaves the bridging system as if there were a
>timeout.
>
>Review: https://reviewboard.asterisk.org/r/4199/
>........
>
>Merged revisions 428601 from http://svn.asterisk.org/svn/asterisk/branches/12
>........
>
>Merged revisions 428602 from http://svn.asterisk.org/svn/asterisk/branches/13
>

Matt Jordan (5993):

>asterisk: Fix timeout issues introduced by r5942
>
>When the valgrind patch was merged for r5942, it unilaterally increased the
>timeouts for the callback sequence during an Asterisk shutdown. When we
>shutdown Asterisk, we:
>* Call stop gracefully
>* Wait a bit, then call stop now
>* Wait a bit, then kill Asterisk
>
>The wait times for killing Asterisk was increased from 5 seconds to 200
>seconds. For tests that currently KILL Asterisk, this made them run
>inordinately long. It also increased unilaterally the 'core wait fullybooted'
>timeout.
>
>This patch restores the regular timeouts when VALGRIND_ENABLED is not detected.
>

Matt Jordan (5994):

>bridge/atxfer_retries: Unilaterally kill all channels on scenario end
>
>When the atxfer_retries test ends, it does properly hangup the 'test' channels
>that it controls. However, because it dials several other channels in the test,
>and those channels are transferred to different extensions, there are several
>channels still active and not controlled by the AppTest framework active. When
>Asterisk is shut down gracefully, the graceful shutdown fails and we end up
>having to kill Asterisk.
>
>This patch updates the test to send a 'Hangup all the channels' AMI action
>just prior to scenario end. That causes all of the transferred channels to be
>hung up as well.
>



--------------
Tests
--------------
Existing Test Failures (4)
   - AsteriskUnitTests: /main/cel/test cel attended transfer bridges swap
   - AsteriskUnitTests: /channels/features/test features channel dtmf
   - AsteriskUnitTests: /channels/features/test features channel dtmf
   - AsteriskUnitTests: /main/cel/test cel attended transfer bridges link
Fixed Tests (1)
   - AsteriskUnitTests: /main/cel/test cel attended transfer bridges link

--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20141125/70caf5c6/attachment.html>


More information about the Test-results mailing list