[asterisk-dev] [Code Review] 3965: testsuite: Test CDRs in a multi-party bridge
Matt Jordan
reviewboard at asterisk.org
Fri Sep 5 15:25:38 CDT 2014
> On Sept. 5, 2014, 12:44 p.m., Scott Griepentrog wrote:
> > On fresh trunk (on centos6 64bit) I'm getting a failure on cdr_bridge_multi while no other cdr tests are failing.
> >
> > --> Running test 'tests/cdr/cdr_bridge_multi' ...
> > Making sure Asterisk isn't running ...
> > Making sure SIPp isn't running...
> > Running ['./lib/python/asterisk/test_runner.py', 'tests/cdr/cdr_bridge_multi'] ...
> > [Sep 05 12:38:11] WARNING[59911]: asterisk:405 __send_kill: Sending KILL to Asterisk 127.0.0.1
> > [Sep 05 12:38:11] WARNING[59911]: astcsv:128 match: CSV MATCH FAILED, different number of records, self=18 and other=23
> > [Sep 05 12:38:11] ERROR[59911]: cdr:91 match_cdrs: Master.csv: actual did not match expected.
> > Test ['./lib/python/asterisk/test_runner.py', 'tests/cdr/cdr_bridge_multi', 'SVN-trunk-r422647'] failed
> >
>
> opticron wrote:
> Did you apply the patch from 3964?
What Kinsey said. It needs the patch from 3964 (I'm just happy it didn't crash, honestly)
- Matt
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/3965/#review13250
-----------------------------------------------------------
On Sept. 1, 2014, 12:19 p.m., Matt Jordan wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/3965/
> -----------------------------------------------------------
>
> (Updated Sept. 1, 2014, 12:19 p.m.)
>
>
> Review request for Asterisk Developers.
>
>
> Bugs: ASTERISK-24241
> https://issues.asterisk.org/jira/browse/ASTERISK-24241
>
>
> Repository: testsuite
>
>
> Description
> -------
>
> This patch tests CDRs for channels in a multi-party bridge. It reproduces the bug on ASTERISK-24241, and passes with the patch on r3964. The test:
> * Makes 5 Local channels, and adds them to a multi-party bridge via ARI.
> * It then takes channels 0 and 3 and removes from the bridge
> * It then re-adds channels 0 and 3
> * Upon having all 5 channels back in the multi-party bridge, it removes them all, hangs them up, and deletes the bridge.
>
> The test verifies that the expected CDRs are generated.
>
>
> Diffs
> -----
>
> /asterisk/trunk/tests/cdr/tests.yaml 5539
> /asterisk/trunk/tests/cdr/cdr_bridge_multi/test-config.yaml PRE-CREATION
> /asterisk/trunk/tests/cdr/cdr_bridge_multi/configs/ast1/extensions.conf PRE-CREATION
> /asterisk/trunk/tests/cdr/cdr_bridge_multi/cdr_bridge_multi.py PRE-CREATION
>
> Diff: https://reviewboard.asterisk.org/r/3965/diff/
>
>
> Testing
> -------
>
>
> Thanks,
>
> Matt Jordan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20140905/b54778b9/attachment.html>
More information about the asterisk-dev
mailing list