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

Jie Yu commented on MESOS-3410:
-------------------------------

OK, i know the reason. OpenSUSE put libpcre.so.1 under /usr/lib64 (not /lib64). 
We don't copy /usr/lib64 when preparing the test rootfs (see 
src/tests/containerizer/rootfs.hpp).

> MesosContainerizerLaunchTest.ROOT_ChangeRootfs is broken/flaky
> --------------------------------------------------------------
>
>                 Key: MESOS-3410
>                 URL: https://issues.apache.org/jira/browse/MESOS-3410
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization, test
>            Reporter: Kapil Arya
>
> `sudo make check` failed with the following error on my OpenSUSE Tumbleweed 
> box (Linux 4.1, gcc 5.1):
> {code}
> [----------] 1 test from MesosContainerizerLaunchTest
> [ RUN      ] MesosContainerizerLaunchTest.ROOT_ChangeRootfs
> Changing root to 
> /tmp/MesosContainerizerLaunchTest_ROOT_ChangeRootfs_4hGV7G/rootfs
> /usr/bin/stat: error while loading shared libraries: libpcre.so.1: cannot 
> open shared object file: No such file or directory
> ../../src/tests/containerizer/launch_tests.cpp:143: Failure
> Value of: ((((*(int *) &(status))) & 0xff00) >> 8)
>   Actual: 127
> Expected: 0
> [  FAILED  ] MesosContainerizerLaunchTest.ROOT_ChangeRootfs (1171 ms)
> {code}
> Here is the output of ldd:
> {code}
> $> ldd /usr/bin/stat
>         linux-vdso.so.1 (0x00007fffd83fc000)
>         libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f80748b3000)
>         libc.so.6 => /lib64/libc.so.6 (0x00007f807450e000)
>         libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f807429f000)
>         libdl.so.2 => /lib64/libdl.so.2 (0x00007f807409b000)
>         /lib64/ld-linux-x86-64.so.2 (0x00005602eb941000)
>         libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f8073e7d000)
> {code}



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

Reply via email to