[
https://issues.apache.org/jira/browse/YETUS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102418#comment-15102418
]
Colin Patrick McCabe commented on YETUS-286:
--------------------------------------------
I did some Googling and most of the people complaining about "failed to map
segment from shared object: Permission denied" are complaining about selinux.
Is selinux enabled in any of our Docker images? Of course, that begs the
question of why the build failure would be intermittent, rather than repeatable.
Another random theory I had is that some process is updating {{libxml2.so.2}},
etc. etc. while the build is in progress, potentially deleting or renaming the
old version and causing this failure. However, I thought this had been
addressed during Dockerization.
Examples of this failure:
https://builds.apache.org/job/PreCommit-HADOOP-Build/8414/artifact/patchprocess/patch-compile-root-jdk1.8.0_66.txt
https://builds.apache.org/job/PreCommit-HADOOP-Build/8414/artifact/patchprocess/patch-compile-root-jdk1.7.0_91.txt
Obviously this is really frustrating and until we can fix this, we're going to
burn a lot of jenkins time re-running native patches... :(
> 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 randomly 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. 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)
