You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2016/01/27 23:56:39 UTC

[jira] [Resolved] (YETUS-286) The native build randomly fails with "failed to map segment from shared object"

     [ https://issues.apache.org/jira/browse/YETUS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved YETUS-286.
------------------------------------
    Resolution: Duplicate

> 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)