[test-results] [Bamboo] Asterisk - trunk - Mac OS 10.4 - PPC build 29 was SUCCESSFUL (with 3 tests). Change made by twilson

[Bamboo]

-------------- next part --------------
-----------------------------------------------------------
AST-MACOS104XPPCVTRUNK-29 was successful.
-----------------------------------------------------------
Code has been updated by twilson.
3 tests in total.

http://bamboo.asterisk.org/browse/AST-MACOS104XPPCVTRUNK-29/        


--------------
Code Changes
--------------
twilson (292310):

>Merged revisions 292309 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.8
>
>........
>  r292309 | twilson | 2010-10-19 12:27:32 -0700 (Tue, 19 Oct 2010) | 10 lines
>  
>  Add sip show peer info about crypto and remove dated comment
>  
>  This patch adds information about the encryption setting to 'sip show
>  peers' and removes an out-of-date comment from res_srtp.c and instead
>  directs users to the proper documentation.
>  
>  (closes issue #18140)
>  Reported by: chodorenko
>........
>


--------------
Error Summary
--------------
   ./configure: line 4714: Support/Asterisk/Modules: No such file or directory
   ./configure: line 4715: Support/Asterisk: No such file or directory
   ./configure: line 4717: Support/Asterisk/Run: No such file or directory
   Package gtk+-2.0 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gtk+-2.0.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gtk+-2.0' found
   Package gtk+-2.0 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gtk+-2.0.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gtk+-2.0' found
   No such process
   asterisk.c line 318 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 320 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 318 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 320 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 318 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 320 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 318 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 320 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 318 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 320 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 318 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 320 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 318 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 320 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 318 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 320 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 318 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 320 (ast_register_file_version): Error releasing rwlock: Invalid argument
   Workaround Bonjour: Unknown error: 0
   loader.c line 179 (ast_module_unregister): Error obtaining mutex: Invalid argument
   loader.c line 187 (ast_module_unregister): mutex '&(&module_list)->lock' freed more times than we've locked!
   loader.c line 187 (ast_module_unregister): Error releasing mutex: Invalid argument


--
This message is automatically generated by Atlassian Bamboo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/test-results/attachments/20101019/2d23c409/attachment.htm