[test-results] [Bamboo] No agents to build plan Asterisk Testing - Asterisk 10 Branch - Asterisk CentOS 6 32-Bit

Bamboo bamboo at asterisk.org
Mon Sep 17 09:24:11 CDT 2012


-------------------------------------------------------------------------------
TESTING-ASTERISK10BRANCH-AST18CENTOS32-388 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------

http://bamboo.asterisk.org/browse/TESTING-ASTERISK10BRANCH-AST18CENTOS32/log

--------------
Code Changes
--------------
dlee (373025):

>Fix timeouts for ast_waitfordigit[_full].
>
>ast_waitfordigit_full would simply pass its timeout to ast_waitfor_nandfds,
>expecting it to decrement the timeout by however many milliseconds were
>waited. This is a problem if it consistently waits less than 1ms. The timeout
>will never be decremented, and we wait... FOREVER!
>
>This patch makes ast_waitfordigit_full manage the timeout itself. It maintains
>the previously undocumented behavior that negative timeouts wait forever.
>
>(closes issue ASTERISK-20375)
>Reported by: Mark Michelson
>Tested by: Mark Michelson
>Review: https://reviewboard.asterisk.org/r/2109/
>........
>
>Merged revisions 373024 from http://svn.asterisk.org/svn/asterisk/branches/1.8
>

mjordan (373059):

>Constify __ao2_ref_debug in astobj2
>
>When REF_DEBUG is enabled in certain files - most notably ccss.c - the 'tag'
>parameter passed to __ao2_ref_debug will be a const char *.  The function
>currently expects that parameter to not be const.  This causes a warning
>when compiling, as the const qualifier is being discarded.  With dev-mode
>enabled, this prevents compiling Asterisk.
>
>This patch makes __ao2_ref_debug's tag and file parameters const.
>
>(closes issue ASTERISK-20408)
>Reported by: mjordan
>........
>
>Merged revisions 372959 from http://svn.asterisk.org/svn/asterisk/branches/1.8
>

mjordan (373062):

>Resolve memory leaks in TLS initialization and TLS client connections
>
>This patch resolves two sources of memory leaks when using TLS in Asterisk:
>1) It removes improper initialization (and multiple re-initializations) of
>   portions of the SSL library.  Asterisk calls SSL_library_init and
>   SSL_load_error_strings during SSL initialization; collectively this
>   obviates the need for calling any of the following during initialization
>   or client connection handling:
>   * ERR_load_crypto_strings (handled by SSL_load_error_strings)
>   * OpenSSL_add_all_algorithms (synonym for SSL_library_init)
>   * SSLeay_add_ssl_algorithms (synonym for SSL_library_init)
>2) Failure to completely clean up all memory allocated by Asterisk and by
>   the SSL library for TLS clients.  This included not freeing the SSL_CTX
>   object in the SIP channel driver, as well as not clearing the error
>   stack when the TLS client exited.
>
>Note that these memory leaks were found by Thomas Arimont, and this patch
>was essentially written by him with some minor tweaks.
>
>(closes issue AST-889)
>Reported by: Thomas Arimont
>Tested by: Thomas Arimont
>patches:
>  (bugAST-889.patch) by Thomas Arimont (license 5525)
>
>Review: https://reviewboard.asterisk.org/r/2105
>........
>
>Merged revisions 373061 from http://svn.asterisk.org/svn/asterisk/branches/1.8
>


--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20120917/03db76e3/attachment-0001.htm>


More information about the Test-results mailing list