[test-results] [Bamboo] Asterisk - trunk - Linux - i686 build 62 has FAILED. Change made by dvossel

[Bamboo]

-------------- next part --------------
-----------------------------------------------------------
AST-TRUNK32-62 failed.
-----------------------------------------------------------
Code has been updated by dvossel.
No failed tests found, a possible compilation error.

http://bamboo.asterisk.org/browse/AST-TRUNK32-62/        


--------------
Code Changes
--------------
dvossel (292869):

>Merged revisions 292868 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.8
>
>................
>  r292868 | dvossel | 2010-10-25 14:07:50 -0500 (Mon, 25 Oct 2010) | 39 lines
>  
>  Merged revisions 292867 via svnmerge from 
>  https://origsvn.digium.com/svn/asterisk/branches/1.6.2
>  
>  ................
>    r292867 | dvossel | 2010-10-25 14:06:21 -0500 (Mon, 25 Oct 2010) | 32 lines
>    
>    Merged revisions 292866 via svnmerge from 
>    https://origsvn.digium.com/svn/asterisk/branches/1.4
>    
>    ........
>      r292866 | dvossel | 2010-10-25 14:05:07 -0500 (Mon, 25 Oct 2010) | 27 lines
>      
>      This patch turns chan_local pvts into astobj2 objects.
>      
>      chan_local does some dangerous things involving deadlock avoidance.
>      tech_pvt functions like hangup and queue_frame are provided with a
>      locked channel upon entry.  Those functions are completely safe as
>      long as you don't attempt to give up that channel lock, but that is
>      impossible to guarantee due to the required deadlock avoidance necessary
>      to lock both the tech_pvt and both channels involved.
>      
>      In the past, we have tried to account for this by doing things like
>      setting a "glare" flag that indicates what function should destroy the
>      pvt.  This was used in local_hangup and local_queue_frame to decided
>      who should destroy the pvt if they collided in separate threads.  I
>      have removed the need to do this by converting all chan_local tech_pvts
>      to astobj2.  This means we can ref a pvt before deadlock avoidance
>      and not have to worry about that pvt possibly getting destroyed under
>      us.  It also cleans up where we destroy the tech_pvt.  The only unlink
>      from the tech_pvt container occurs in local_hangup now, which is where
>      it should occur.
>      
>      Since there still may be thread collisions on some functions like
>      local_hangup after deadlock avoidance, I have added some checks to detect
>      those collisions and exit appropriately.  I think this patch is going to
>      solve quite a bit of weirdness we have had with local channels in the past.
>    ........
>  ................
>................
>


--------------
Error Summary
--------------
   Could not find ant Junit test results in the /srv/bamboo/xml-data/build-dir/AST-TRUNK32 directory.
   install: cannot remove `/usr/local/bin/bamboo/build-asterisk.sh': Operation not permitted
   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
   cc1: warnings being treated as errors
   sig_pri.c: In function ?sig_pri_transfer_rsp?:
   sig_pri.c:1946: error: implicit declaration of function ?pri_transfer_rsp?
   make[1]: *** [sig_pri.o] Error 1
   make: *** [channels] Error 2


--
This message is automatically generated by Atlassian Bamboo

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