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

[Bamboo]

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

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

--------------
Code Changes
--------------
wdoekes (342871):

>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
>........
>
>Merged revisions 342869 from http://svn.asterisk.org/svn/asterisk/branches/1.8
>........
>
>Merged revisions 342870 from http://svn.asterisk.org/svn/asterisk/branches/10
>

wdoekes (342930):

>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
>........
>
>Merged revisions 342927 from http://svn.asterisk.org/svn/asterisk/branches/1.8
>........
>
>Merged revisions 342929 from http://svn.asterisk.org/svn/asterisk/branches/10
>


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