[test-results] [Bamboo] Asterisk - Team Branches > roibos-cng-support-1.8 > #9 has FAILED. Change made by oej and root.
Bamboo
bamboo at asterisk.org
Tue Dec 4 18:31:31 CST 2012
-----------------------------------------------------------------------
Asterisk - Team Branches > roibos-cng-support-1.8 > #9 failed.
-----------------------------------------------------------------------
Code has been updated by oej, root.
2/2 jobs failed, no tests found.
http://bamboo.asterisk.org/browse/ASTTEAM-ROIBUSCNGSUPPORT18-9/
--------------
Failing Jobs
--------------
- Asterisk 1.8 CentOS 6 32-Bit (CentOS 6): No tests found.
- Asterisk 1.8 CentOS 6 64-Bit (CentOS 6): No tests found.
--------------
Code Changes
--------------
root (376943):
>Merged revisions 376919 via svnmerge from
>file:///srv/subversion/repos/asterisk/branches/1.8
>
>........
> r376919 | seanbright | 2012-11-30 11:04:34 -0600 (Fri, 30 Nov 2012) | 2 lines
>
> Minor spelling fix to the VOLUME documentation.
>........
>
root (376977):
>Merged revisions 376950 via svnmerge from
>file:///srv/subversion/repos/asterisk/branches/1.8
>
>................
> r376950 | rmudgett | 2012-11-30 15:30:48 -0600 (Fri, 30 Nov 2012) | 15 lines
>
> chan_misdn: Fix sending RELEASE_COMPLETE in response to SETUP.
>
> Fix sending a RELEASE_COMPLETE in response to a SETUP if chan_misdn does
> not have a B channel available to assign to the call.
>
> (closes issue ABE-2869)
> Reported by: Guenther Kelleter
> Patches:
> setup-reject_2.diff (license #6372) patch uploaded by Guenther Kelleter
> Modified
>
> ........
>
> Merged revision 376949 from https://origsvn.digium.com/svn/asterisk/be/branches/C.3-bier
>................
>
root (376915):
>Merged revisions 376901 via svnmerge from
>file:///srv/subversion/repos/asterisk/branches/1.8
>
>........
> r376901 | mmichelson | 2012-11-30 10:12:07 -0600 (Fri, 30 Nov 2012) | 21 lines
>
> Fix potential crashes during SIP attended transfers.
>
> The principal behind this patch is simple. During a transfer,
> we manipulate channels that are owned by a separate thread than
> the one we currently are running in, so it makes sense that we
> need to grab a reference to the channels so that they cannot
> disappear out from under us.
>
> In the wild, crashes were sometimes seen when the transferring
> party would hang up the call before the transfer target answered
> the call. The most common place to see the crash occur was when
> attempting to send a connected line update to the transferer
> channel.
>
> (closes issue ASTERISK-20226)
> Reported by Jared Smith
> Patches:
> ASTERISK-20226.patch uploaded by Mark Michelson (License #5049)
> Tested by: Jared Smith
>........
>
--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20121204/a99505b9/attachment.htm>
More information about the Test-results
mailing list