[test-results] [Bamboo] Asterisk - 1.8 - Mac OS 10.6 build 155 has FAILED. Change made by 8 authors
Bamboo
bamboo at asterisk.org
Thu Sep 9 20:54:23 CDT 2010
-------------- next part --------------
-----------------------------------------------------------
AST-MACOS106V18-155 failed.
-----------------------------------------------------------
Code has been updated by twilson, qwell, Russell Bryant, rmudgett, bbryant, dvossel, Bc. Jan Kalab, Tilghman Lesher.
No failed tests found, a possible compilation error.
http://bamboo.asterisk.org/browse/AST-MACOS106V18-155/
--------------
Code Changes
--------------
dvossel (285568):
>Merged revisions 285567 via svnmerge from
>https://origsvn.digium.com/svn/asterisk/branches/1.6.2
>
>................
> r285567 | dvossel | 2010-09-08 17:11:28 -0500 (Wed, 08 Sep 2010) | 9 lines
>
> Merged revisions 285566 via svnmerge from
> https://origsvn.digium.com/svn/asterisk/branches/1.4
>
> ........
> r285566 | dvossel | 2010-09-08 17:07:31 -0500 (Wed, 08 Sep 2010) | 2 lines
>
> In retrans_pkt, do not unlock pvt until the end of the function on a transmit failure.
> ........
>................
>
bbryant (285533):
>Merged revisions 285532 via svnmerge from
>https://origsvn.digium.com/svn/asterisk/branches/1.6.2
>
>........
> r285532 | bbryant | 2010-09-08 16:56:12 -0400 (Wed, 08 Sep 2010) | 8 lines
>
> Fixes a bug with MeetMe where after announcing the amount of time left in a conference, if music on hold was playing, it doesn't restart.
>
> (closes issue #17408)
> Reported by: sysreq
> Patches:
> asterisk-issue-17408_fixed.patch uploaded by sysreq (license 1009)
> Tested by: sysreq
>........
>
dvossel (285564):
>Merged revisions 285563 via svnmerge from
>https://origsvn.digium.com/svn/asterisk/branches/1.6.2
>
>........
> r285563 | dvossel | 2010-09-08 16:47:29 -0500 (Wed, 08 Sep 2010) | 54 lines
>
> Fixes interoperability problems with session timer behavior in Asterisk.
>
> CHANGES:
> 1. Never put "timer" in "Require" header. This is not to our benefit
> and RFC 4028 section 7.1 even warns against it. It is possible for one
> endpoint to perform session-timer refreshes while the other endpoint does
> not support them. If in this case the end point performing the refreshing
> puts "timer" in the Require field during a refresh, the dialog will
> likely get terminated by the other end.
>
> 2. Change the behavior of 'session-timer=accept' in sip.conf (which is
> the default behavior of Asterisk with no session timer configuration
> specified) to only run session-timers as result of an incoming INVITE
> request if the INVITE contains an "Session-Expires" header... Asterisk is
> currently treating having the "timer" option in the "Supported" header as
> a request for session timers by the UAC. I do not agree with this. Session
> timers should only be negotiated in "accept" mode when the incoming INVITE
> supplies a "Session-Expires" header, otherwise RFC 4028 says we should
> treat a request containing no "Session-Expires" header as a session with
> no expiration.
>
> Below I have outlined some situations and what Asterisk's behavior is.
> The table reflects the behavior changes implemented by this patch.
>
> SITUATIONS:
> -Asterisk as UAS
> 1. Incoming INVITE: NO "Session-Expires"
> 2. Incoming INVITE: HAS "Session-Expires"
>
> -Asterisk as UAC
> 3. Outgoing INVITE: NO "Session-Expires". 200 Ok Response HAS "Session-Expires" header
> 4. Outgoing INVITE: NO "Session-Expires". 200 Ok Response NO "Session-Expires" header
> 5. Outgoing INVITE: HAS "Session-Expires".
>
> Active - Asterisk will have an active refresh timer regardless if the other endpoint does.
> Inactive - Asterisk does not have an active refresh timer regardless if the other endpoint does.
> XXXXXXX - Not possible for mode.
> ______________________________________
> |SITUATIONS | 'session-timer' MODES |
> |___________|________________________|
> | | originate | accept |
> |-----------|------------|-----------|
> |1. | Active | Inactive |
> |2. | Active | Active |
> |3. | XXXXXXXX | Active |
> |4. | XXXXXXXX | Inactive |
> |5. | Active | XXXXXXXX |
> --------------------------------------
>
>
> (closes issue #17005)
> Reported by: alexrecarey
>........
>
--------------
Error Summary
--------------
Could not find ant Junit test results in the /srv/bamboo/xml-data/build-dir/AST-MACOS106V18 directory.
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
svn: This client is too old to work with working copy '.'; please get a newer Subversion client
cc1: warnings being treated as errors
In file included from /srv/bamboo/xml-data/build-dir/AST-MACOS106V18/include/asterisk/select.h:29,
from /srv/bamboo/xml-data/build-dir/AST-MACOS106V18/include/asterisk/poll-compat.h:83,
from /srv/bamboo/xml-data/build-dir/AST-MACOS106V18/include/asterisk/compat.h:74,
from /srv/bamboo/xml-data/build-dir/AST-MACOS106V18/include/asterisk.h:28,
from ael_lex.c:20:
/srv/bamboo/xml-data/build-dir/AST-MACOS106V18/include/asterisk/utils.h: In function ‘_ast_strndup’:
/srv/bamboo/xml-data/build-dir/AST-MACOS106V18/include/asterisk/utils.h:559: warning: implicit declaration of function ‘strndup’
/srv/bamboo/xml-data/build-dir/AST-MACOS106V18/include/asterisk/utils.h:559: warning: incompatible implicit declaration of built-in function ‘strndup’
make[1]: *** [aelparse.o] Error 1
make: *** [utils] Error 2
--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/test-results/attachments/20100909/c7b9815e/attachment-0001.htm
More information about the Test-results
mailing list