[test-results] [Bamboo] No agents to build plan Asterisk - 1.8 - FreeBSD 8.1 - i386

[Bamboo]

-------------------------------------------------------------------------------
AST18-FREEBSD81-I386-319 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------

http://bamboo.asterisk.org/browse/AST18-FREEBSD81-I386/log

--------------
Code Changes
--------------
mjordan (342769):

>Fixed invalid memory access when adding extension to pattern match tree
>
>When an extension is removed from a context, its entry in the pattern match
>tree is not deleted.  Instead, the extension is marked as deleted.  When an
>extension is removed and re-added, if that extension is also a prefix of
>another extension, several log messages would report an error and did not
>check whether or not the extension was deleted before accessing the memory.
>Additionally, if the extension was already in the tree but previously
>deleted, and the pattern was at the end of a match, the findonly flag was
>not honored and the extension would be erroneously undeleted.  
>
>Additionaly, it was discovered that an IAX2 peer could be unregistered
>via the CLI, while at the same time it could be scheduled for unregistration
>by Asterisk.  The unregistration method now checks to see if the peer
>was already unregistered before continuing with an unregistration.
>
>(closes issue ASTERISK-18135)
>Reported by: Jaco Kroon, Henry Fernandes, Kristijan Vrban
>Tested by: Matt Jordan
>
>Review: https://reviewboard.asterisk.org/r/1526
>
>
>

wdoekes (342869):

>Cleanup references to sipusers and sipfriends dynamic realtime families
>
>Somewhere between 1.4 and 1.8 the sipusers family has become completely
>unused. Before that, the sipfriends family had been obsoleted in favor
>of separate sipusers and sippeers families. Apparently, they have been
>merged back again into a single family which is now called "sippeers".
>
>Reviewed by: irroot, oej, pabelanger
>
>Review: https://reviewboard.asterisk.org/r/1523
>

wdoekes (342927):

>Several fixes to the chan_sip dynamic realtime peer/user lookup
>
>There were several problems with the dynamic realtime peer/user lookup
>code. The lookup logic had become rather hard to read due to lots of
>incremental changes to the realtime_peer function. And, during the
>addition of the sipregs functionality, several possibilities for memory
>leaks had been introduced. The insecure=port matching has always been
>broken for anyone using the sipregs family. And, related, the broken
>implementation forced those using sipregs to *still* have an ipaddr
>column on their sippeers table.
>
>Thanks Terry Wilson for comprehensive testing and finding and fixing
>unexpected behaviour from the multientry realtime call which caused
>the realtime_peer to have a completely unused code path.
>
>This changeset fixes the leaks, the lookup inconsistenties and that
>you won't need an ipaddr column on your sippeers table anymore (when
>you're using sipregs). Beware that when you're using sipregs, peers
>with insecure=port will now start matching!
>
>(closes issue ASTERISK-17792)
>(closes issue ASTERISK-18356)
>Reported by: marcelloceschia, Walter Doekes
>Reviewed by: Terry Wilson
>
>Review: https://reviewboard.asterisk.org/r/1395
>


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