[test-results] [Bamboo] Asterisk Testing > AST1.8-digiumphones > #5 has FAILED. Change made by Mark Michelson.

[Bamboo]

-----------------------------------------------------------------------
Asterisk Testing > AST1.8-digiumphones > #5 failed.
-----------------------------------------------------------------------
Code has been updated by Mark Michelson.
2/2 jobs failed, with 0 failing tests.

http://bamboo.asterisk.org/browse/TESTING-AST18DIGIUMPHONES-5/


--------------
Failing Jobs
--------------
  - Asterisk 1.8 CentOS 6 32-Bit (CentOS 6): 68 tests passed.
  - Asterisk 1.8 CentOS 6 64-Bit (CentOS 6): 69 tests passed.


--------------
Code Changes
--------------
Mark Michelson (360031):

>Get rid of an annoying "Possible programming error" message.
>
>If an extension's 'app' field is NULL, then a "(null)" string
>would be written into an ast_str due to the way that snprintf
>works. When this is passed to ast_strlen_zero(), it fires up
>a big warning indicating something is probably wrong.
>
>There indeed was a problem, but luckily it wasn't a very big
>problem. After the failed ast_strlen_zero() check and big
>warning message, the very next if statement, checking to
>see if the "(null)" matched a presence provider, would fail,
>so no harm was done.
>
>


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