[ 
https://issues.apache.org/jira/browse/YETUS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102433#comment-15102433
 ] 

Colin Patrick McCabe commented on YETUS-286:
--------------------------------------------

We now we have some C++ code in the tree whose build time is drastically 
reduced by using a higher concurrency level.  Typical maven builds don't peg 
the CPU because maven spends a lot of its time downloading things from the 
internet, writing files, running unit tests, and so on.  gcc processes also 
don't use a lot of memory when compared to maven (most of the time).  So I'm 
skeptical that running make -j 16 will be that harmful in practice.  We could 
certainly look into tuning this, but I don't see why it would be the root cause 
of "failed to map segment from shared object" failures.

> The native build randomly fails with "failed to map segment from shared 
> object"
> -------------------------------------------------------------------------------
>
>                 Key: YETUS-286
>                 URL: https://issues.apache.org/jira/browse/YETUS-286
>             Project: Yetus
>          Issue Type: Bug
>          Components: Test Patch
>    Affects Versions: 0.2.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Sean Busbey
>            Priority: Critical
>
> On Jenkins, the native build seems to intermittently fail with "failed to map 
> segment from shared object."  For example:
> {code}
> [WARNING] /usr/bin/cmake: error while loading shared libraries: libxml2.so.2: 
> failed to map segment from shared object: Permission denied
> {code}
> We have also seen this happen with {{librtmp.so.0}}, {{libcurl.so.4}}, and 
> other native libraries which are dependencies of the thing being built.  
> Basically, there is some random chance any particular native dependency will 
> get "failed to map segment."  When this happens, the native build fails and 
> returns a -1 even if there was no actual problem.  This requires us to re-run 
> Jenkins to get a correct result.  The problem does not seem to reproduce 
> locally.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to